Skip to main content

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

Running the Static Assembler in stand-alone mode

Updated on May 11, 2022

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.
    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.username The user name allowed to connect to the database.
    pega.jdbc.passwordThe password for the user name allowed to connect to the database.
    rules.schema.nameThe schema name where rule tables reside.
    data.schema.nameApplicable 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.
    udb.schema.nameThe 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.
    PropertyDescription 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.configEnter the absolute location of the file that you edited in step 2.
    ANT_HOMESpecify the location of the Apache Ant directory on the server.
    application.nameEnter 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.versionEnter the version number of the application.
    accessgroupEnter the access group that provides access to the application version.
    path.prdeployEnter a full path to the prdeploy JAR file in the distribution image.
    path.antcontribEnter 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.

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