Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Running Static Assembler in utility mode

Updated on August 25, 2021

Run the Static Assembler from the /scripts/utils directory within the extracted application installation directory. This is the best practice because the Static Assembler uses information that is in the application installation directory.

  1. On your application server, extract the file from the /scripts/utils/ directory on the application distribution media to the same directory.
  2. Create the <>/WEB-INF/lib directory.
  3. In the WEB-INF/lib directory of the prweb.war file or in the APP-INFAPP-INF/lib of the prpc_j2ee*.ear file, locate the following JAR files:
    • sr94-1.0.jar
    • prbootstrap.jar
    • prdbcdp.jar
    • prbootstrap-api.jar
  4. Copy the four JAR files to the <>/WEB-INF/lib directory.
  5. In the scripts/utils/staticAssemblerResources/config/prstaticassembly directory,open the file.
  6. Specify the following properties.
    PropertyDescription the full path to the <> directory of your environment.

    Example for Windows: D:\\prpcmedia\\scripts\\utils\\pegaapprootpegaapproot

    After each backslash (\), include a backslash escape character (\).

    Example for Linux: /opt/prpcmedia/scripts/utils/pegaapproot

    application.nameEnter 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.versionEnter the version number of the application.
    accessgroupEnter the access group that provides access to the application version.
    path.prdeployOptional. The default path is to the JAR file in the distribution image.
    path.antcontribOptional. The default path is to the JAR file in the distribution image. Change the path to specify a different antcontrib JAR file.
  7. In the scripts/utils/ directory, open the file to define the connection to your database.
  8. Specify the following variables that are specific for your database vendor.
    pega.jdbc.driver.jarThe full path to the JDBC driver JAR file.
    pega.jdbc.driver.classThe Java class name of the JDBC driver.
    pega.database.typeSelect the database vendor from the list of supported vendors.
    pega.jdbc.urlThe URL connection for your database. Refer to the examples in the file.
    pega.jdbc.usernameThe user name allowed to connect to the database.
    pegajdbc.passwordThe password for the user name allowed to connect to the database.
  9. Stop the application server.
    Note: You must stop the application server because the Static Assembler starts three JVM instances and an instance of the application engine by default.
  10. Run the 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.
  11. When the assembly process is complete, you can view the result log in the scripts/utils/staticAssemblerResources/logs/ directory.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us