Core application tasks

Command                        

Action

gwb gwTasks

Displays all Guidewire gwb command options.

gwb clean

Deletes the build directories.

gwb cleanIdea

Deletes the PolicyCenter Studio project files (files with .iml and .idea extensions).

gwb codegen

Generates metadata classes, page configuration classes, permission classes, localization classes, xml classes, and entity role constraints classes.

gwb compile

Compiles and copies resources for the QuickStart application server. Run this command before you start the QuickStart server. See the runServer command for more information.
gwb dropDB -Denv=env

Prepares a new database for use by the Guidewire application. It will act upon the database configured in database-config.xml, or as optionally specified by the -Denv=env parameter.

Use caution whenever using this command. If the database has any objects before the command is run, the objects are all dropped and not available for recovery except from a database backup.

You can pass additional parameters to this command by adding the parameters to the <reset-tools-params> subelement in database-config.xml as shown in the following code example:

<database>
  <dbcp-connection-pool>
    <reset-tool-params system-username="user" system-password="pass"/>
  </dbcp-connection-pool>
</database>

SQL Server

The command drops and creates a new database. It creates any filegroups named within the <database> element. The database files will be physically located where the server would put them by default. If specified, the collate attribute specifies the database collation. Otherwise, the default collation of the database server will be used. The command SET READ_COMMITTED_SNAPSHOT ON WITH ROLLBACK IMMEDIATE is issued on the new database. Since a CREATE DATABASE command is used, attributes of the model system database of the server are inherited.

The dropDB command will create any file groups listed in the upgrade element of the database configuration. This does not happen on Oracle. However, the dropDB command will not drop a database with file groups. If you have file groups configured, first drop the database using the Management Studio. Then you can run dropDB to create the database with file groups.

Oracle

A Guidewire database corresponds to an Oracle schema: a user and all the objects owned by that user. So, for Oracle, this command drops all objects owned by the schema owner, and only the user is left with the required permissions. The dropDB command requires SQLPlus, available with the Oracle client installation. Include ORACLE_HOME\bin in the PATH, so that dropDB can locate SQLPlus.

The system-username and system-password attributes of the <reset-tools-params> element must be specified so that the required permissions are available for these actions.

gwb idea

Builds the PolicyCenter Studio project.
gwb inspect

[--include include‑dirs]

[--outputDir output‑dir]

[--profileName profile‑name]

[--profileXML file‑path]

[--scopeXML file‑path]

[--verbose level]

Runs Guidewire Studio inspections.

include include-dirs
Comma separated list of paths to additional directories to include in the inspection analysis. The directories listed here must be located within modules/configuration, and the paths specified must be relative to modules/configuration. The following directories are always included by default:
  • gsrc
  • pcf/web
  • config/rules
  • config/resources/productmodel
outputDir output-dir
The full path to an existing directory where the XML file with the inspection report will be stored.
profileName profile-name
The name of the inspection profile to use for the inspection analysis. You can specify one of profileName or profileXML, but not both.
profileXML file-path
The path to the XML file containing the profile to use for the inspection analysis. You can specify one of profileName or profileXML, but not both.
scopeXML file-path
The path to the XML file containing the scope file to use for the inspection analysis.
verbose level
The logging level. Specify a number between 0 and 3, where 0 means no logging and 3 is frequent logging. The default is 0.

gwb runServer -Denv=env

Starts the bundled QuickStart application server. Depending on what you want to do, use the following command options:

  • To start the server in development mode using socket debugging, use the command gwb runServer --debug-socket --no-suspend.

  • To start the server in development mode in a suspended state using socket debugging, use the command gwb runServer --debug-socket.

  • To start the server in development mode using shared memory debugging, use the command gwb runServer --debug-shmem.

  • To start the server using a non-default port, use the command gwb runServer -Dgw.port=nnnn.

  • To start the server in development mode in a suspended state using shared memory debugging, use the command gwb runServer --debug-shmem --no-suspend.

  • To start the server in a particular environment, set the optional -Denv="env parameter.

IMPORTANT There is a dependency between the gwb runServer command and the gwb compile command. Guidewire recommends that you run the gwb compile command separately, before you run the gwb runServer command, for example:
  • gwb compile
  • gwb runServer -x compile

Use the -x compile option with the runServer command to remove the dependency between the compile and the runServer commands. Otherwise, PolicyCenter must first verify what resources, if any, need to be recompiled, then perform an incremental recompile of those resources before starting the server.

gwb stopServer

Stops the bundled QuickStart application server.

gwb studio

Starts Guidewire Studio.