This article explains how to make an impact analysis on a production database using the Business Process Deployer tool.
Export your Business Process Diagrams from the IDE by selecting Tools > Workflow > Create business process deploy file.
Once the diagrams have been exported, run the Business Process Deployer. To do so, go to Start > Programs > GXflowX > Business Process Deployer and the following sequence of wizards will appear.
In the first one, select the deployment file created in Step 1.
Next, set your deployment preferences.
- Create new version of business processes: A new version of the business processes is created. This option is recommended to avoid changing the flow of active processes that are running with a previous version of the business processes.
- Automatically detect and execute needed reorganizations: The version in the database will be automatically detected and all the needed reorganizations will be executed.
- Force workflow tables creation: When you force the creation of workflow tables, the tables will be overwritten and no reorganizations will be done. All the processes that are running will be lost, so it is not advisable if you are in a production state. Also, if your licenses are local, they will be lost. Therefore, it is recommended to uninstall them first, then create the tables, and finally request them again.
- Execute needed reorganizations assuming a specific current workflow runtime version: You must select the current version in the database and all the needed reorganizations will be executed.
This step will vary depending on the environment you are using. If your deployment file is for a Java environment, an Execution section will be displayed and, in the additional classpath field, you must indicate at least the *.jar file of JTDS (located in <GeneXus installation>\gxjava\drivers). If your application uses other external Java resources, you must include them too. When your file is for a .NET Framework or .NET Environment, the Execution section is not displayed and a "Use Windows NT integrated security" option is available to authenticate to the database.
- Below is an example of a classpath you might need: C:\KBs\<KBName>\JavaSQLServer\Web\dependencies\bcprov-jdk18on-1.75.jar;C:\KBs\<KBName>\JavaSQLServer\Web\dependencies\bcutil-jdk18on-1.75.jar;C:\KBs\<KBName>\JavaSQLServer\Web\dependencies\commons-collections4-4.4.jar;C:\KBs\<KBName>\JavaSQLServer\Web\dependencies\commons-io-2.11.0.jar;C:\KBs\<KBName>\JavaSQLServer\Web\dependencies\commons-lang-2.6.jar;C:\KBs\<KBName>\JavaSQLServer\Web\dependencies\GeneXus.jar;C:\KBs\<KBName>\JavaSQLServer\Web\dependencies\gxclassR-4.4.0.jar;C:\KBs\<KBName>\JavaSQLServer\Web\dependencies\gxcommon-4.4.0.jar;C:\KBs\<KBName>\JavaSQLServer\Web\dependencies\gxwrappercommon-4.4.0.jar;C:\KBs\<KBName>\JavaSQLServer\Web\dependencies\gxwrapperjavax-4.4.0.jar;C:\KBs\<KBName>\JavaSQLServer\Web\dependencies\jtds-1.2.jar;C:\KBs\<KBName>\JavaSQLServer\Web\dependencies\log4j-api-2.21.1.jar;C:\KBs\<KBName>\JavaSQLServer\Web\dependencies\log4j-core-2.21.1.jar;C:\KBs\<KBName>\JavaSQLServer\Web\dependencies\mssql-jdbc-10.2.0.jre8.jar;C:\KBs\<KBName>\JavaSQLServer\Web\dependencies\xercesImpl-2.12.2.jar;C:\KBs\<KBName>\JavaSQLServer\Web\build\libs\wfcache.jar;
Finally, click on the Deploy button to start the deployment process.
HowTo: Deploy a Workflow-based Application
Business Process Deployer Command line
HowTo: Enable Log for GXflow BPDeployer