Running the Static Assembler in stand-alone mode
Use the stand-alone mode when using the utility at a command prompt and
when passing connection details through the
setupDatabase.properties file.
/scripts/utils
directory in the application installation directory, you must specify additional information
to configure the Static Assembler.- Extract the
StaticAssembler.zipfile to a folder on the server. - 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.properties 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. rules.schema.name The schema name where rule tables reside. data.schema.name Applicable for split-schema installation. 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.) - In the
staticAssembler/staticAssemblerResources/config/prstaticassemblydirectory, open theprstaticassembly.propertiesfile. - Specify the following properties.
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 2.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. - 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.
- 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. - When the assembly process is complete, you can view the result log in the
staticAssmbler/staticAssemblerResources/logs/directory.
Previous topic Running Static Assembler in utility mode Next topic Packaging your application in a product rule