On-premises only: Running the static assembler from the command line
Run the static assembler utility from a command line to optimize your application performance from hardware resources outside of your system cluster. As an alternative to running the static assembler utility from Dev Studio, if you are an on-premises client you can run the utility outside of your system cluster and avoid putting any additional strains on your Pega application computing resources.
The command line static assembler utility can take several
hours to run, depending on such factors as:
- The number of unique rules in your application.
- Whether this is the first time you run the static assembler.
- The number of new rules in your application cache since you last ran the static assembler.
- Log into your local system with secure access to both your Pega application and the Pega database.
- Extract the
StaticAssembler.zipfile to a folder. - In the
~/staticAssembler/staticAssemblerResources/Config/setupDatabasedirectory, edit thesetupDatabase.propertiesfile to define the connection to your database. - 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 prpcUtils.propertiesfile.pega.jdbc.username The user name that is allowed to connect to the database. pega.jdbc.password The password for the user name that is allowed to connect to the database. rules.schema.name The schema name where rule tables reside. data.schema.name Applicable to split-schema installations. Refers to the schema name where data and work tables are located. If not specified, the value given for rules.schema.nameis considered.udb.schema.name 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.) - Save the file.
- In the
staticAssembler/staticAssemblerResources/config/prstaticassemblydirectory, edit theprstaticassembly.propertiesfile to define properties specific to your application. - Specify the following properties appropriate to your Pega application:
Property Description pega.app.root Enter the full path to the prwebdirectory of your environment.Example for Windows:
Example for Linux:D:\\tomcat6\\apache-tomcat-6.0.20\\webapps\\prweb/opt/tomcat/webapps/prwebpega.database.config Enter the absolute location of the setupDatabase.propertiesfile that you edited in step 3.ANT_HOME Specify the location of the Apache Antdirectory on the server.application.name 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 prdeployJAR file in the distribution image.path.antcontrib Enter a full path to the antcontribJAR file in the distribution image. - Save the file.
- Run the appropriate
staticAssmbler/smartStaticAssembly.bat(or.sh) script to start the static assembler process.The utility analyzes the rules in your application and in the built-on application or applications, assembles any rules that have not yet been assembled, and notifies the application cluster about which rules it has reassembled. - When the assembly process is complete, you can view the result log in the
staticAssmbler/staticAssemblerResources/logs/directory.
Previous topic Running the static assembler from Dev Studio Next topic Moving applications between systems