Servers, databases, and installation scenarios
To help you choose an installation scenario, the following table describes the uses of servers and databases that you can install with PolicyCenter.
|
Install element |
Type |
Good to know |
More information |
|---|---|---|---|
|
QuickStart application server |
Bundled |
You can immediately use the QuickStart server without configuring it. It does not build a WAR or EAR file, which it is necessary to do before deployment with other servers. Use the QuickStart application server for demonstration or
development ( It is not possible to run PolicyCenter in production
( |
|
|
JBoss application server |
Optional |
Suitable for production environments. |
|
|
Tomcat application server |
Optional |
Suitable for production environments. |
|
|
WebSphere application server |
Optional |
Suitable for production environments. |
|
|
WebLogic application server |
Optional |
Suitable for production environments. |
|
|
QuickStart database |
Bundled |
You can immediately use the QuickStart database in file mode. PolicyCenter creates and stores the database files within the tmp directory of the local drive. You can customize this location. You can use the QuickStart database for demonstration or development environments. Guidewire does not support QuickStart for a production environment. Guidewire does not support upgrades to the QuickStart database. Configuring your application sometimes requires extending the data model, which might require dropping the database. With QuickStart, it is not possible to have more than one database connection at a time. |
|
|
Oracle database |
Optional |
It is possible to use the Oracle database for both development and production. |
|
|
SQL Server database |
Optional |
It is possible to use the Microsoft SQL Server database for both development and production. |