Running Static Assembler in utility mode
Run the Static Assembler from the
within the extracted application installation directory. This is the best practice because
the Static Assembler uses information that is in the application installation
On your application server, extract the
StaticAssembler.zipfile from the
/scripts/utils/directory on the application distribution media to the same directory.
WEB-INF/libdirectory of the
prweb.warfile or in the
prpc_j2ee*.earfile, locate the following JAR files:
Copy the four JAR files to the
Specify the following properties.
Property Description pega.app.root Enter the full path to the
<pega.app.root>directory of your environment.
Example for Windows:After each backslash (\), include a backslash escape character (\).
Example for Linux:
application.name Enter the name of the application rule that is the starting point of the assembly process. Rules that belong to any built-on applications are also assembled. application.version Enter the version number of the application. accessgroup Enter the access group that provides access to the application version. path.prdeploy Optional. The default path is to the JAR file in the distribution image. path.antcontrib Optional. The default path is to the JAR file in the distribution image. Change the path to specify a different
scripts/utils/prpcUtils.propertiesdirectory, open the
prpcUtils.propertiesfile to define the connection to your database.
Specify the following variables that are specific for your database vendor.
Variable Description pega.jdbc.driver.jar The full path to the JDBC driver JAR file. pega.jdbc.driver.class The Java class name of the JDBC driver. pega.database.type Select the database vendor from the list of supported vendors. pega.jdbc.url The URL connection for your database. Refer to the examples in the
pega.jdbc.username The user name allowed to connect to the database. pegajdbc.password The password for the user name allowed to connect to the database.
Stop the application server.You must stop the application server because the Static Assembler starts three JVM instances and an instance of the application engine by default.
scripts/utils/smartStaticAssembly.bat(or .sh) script to start the static assembly process. The Static Assembler analyzes the rule in the specific application and in the built-on application or applications and assembles any rules that have not yet been assembled. Processing can take from one to several hours.
When the assembly process is complete, you can view the result log in the