Skip to main content

Table of Contents

Running the Static Assembler in stand-alone mode


Only available versions of this content are shown in the dropdown

Use the stand-alone mode when using the utility at a command prompt and when passing connection details through the file.

Run the Static Assembler outside of the context of the application installation folder. When you run the Static Assembler from a location other than the /scripts/utils directory in the application installation directory, you must specify additional information to configure the Static Assembler.

  1. Extract the file to a folder on the server.

  2. In the staticAssembler/staticAssemblerResources/Config/setupDatabase directory, edit the file to define the connection to your database.

  3. Specify the following variables that are specific to 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 file.
    pega.jdbc.username The user name allowed to connect to the database.
    pega.jdbc.password The password for the user name allowed to connect to the database. The schema name where rule tables reside. Applicable for split-schema installation. Refers to the schema name where data and work tables are located. If not specified, the value given for is considered. The UDB data base type used to specify the name of the schema used by the application database. (In most cases, leave blank to accept the default value pega.jdbc.username.)
  4. In the staticAssembler/staticAssemblerResources/config/prstaticassembly directory, open the file.

  5. Specify the following properties.

    Property Description Enter the full path to the prweb directory of your environment.

    Example for Windows: D:\\tomcat6\\apache-tomcat-6.0.20\\webapps\\prweb

    Example for Linux: /opt/tomcat/webapps/prweb
    pega.database.config Enter the absolute location of the file that you edited in step 2.
    ANT_HOME Specify the location of the Apache Ant directory on the server. Enter the name of the application that serves as 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 Enter a full path to the prdeploy JAR file in the distribution image.
    path.antcontrib Enter a full path to the antcontrib JAR file in the distribution image.
  6. 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.

  7. Run the staticAssmbler/smartStaticAssembly.bat (or .sh) script to start the static assembly process. The Static Assembler analyzes the rule in the specified 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.

  8. When the assembly process is complete, you can view the result log in the staticAssmbler/staticAssemblerResources/logs/ directory.

Did you find this content helpful?

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us