Workflow - Setup

Loading Workflows

Every time a new workflow is created, or an existing workflow is updated, it must be loaded by the DBAs.

Installing Workflows in CMiC R12

There are two options for installing workflows in CMiC 12.

Option 1: Oracle Workflow Builder by Programming

This option requires that a developer connect to the database directly from the Oracle Workflow Builder tool and install the workflow. This option works on either database 12.1 and older, or on 18c databases with authentication security disabled. If authentication security is enabled, the following message will be issued to the developer: “ORA-28040: No matching authentication protocol”.

Since authentication security is enabled on all 18c databases, this option will only work if Oracle Workflow Builder is installed on an 18c Oracle Client. This is outside of the scope of discussion here and the possibility of a project getting Oracle Workflow Builder is outside of DBA control.

For most clients, disabling authentication security is not an option.

Option 2: WFTParser.cmd Utility by CMIC DBAs

This option requires that the system is on patch V12-010-1 or higher.

WFTParser.cmd is located in:

D:\cm\ias\j2ee\ENV\workflow\bin.

To see how it is used:

Run D:\cm\ias\j2ee\ENV\workflow\bin\WFTParser.cmd 

To install a file:

cd /d D:\cm\ias\j2ee\ENV\workflow\bin

WFTParser.cmd <FULL_PATH_NAME_OF_THE_WFT_FILE>

For example, the following is an example using TEST:

cd /d D:\cm\ias\j2ee\j2ee\test\workflow\bin

WFTParser.cmd D:\cm\v12\test\jspsql\MWH_WKF_APREGINV_WFT.wft

Log files from the WFTParser are located in:

D:\cm\ias\j2ee\ENV\workflow\logs

Patches V12-009-2 and Earlier

Instructions and necessary files for installing WFTParser are located in: 

X:\Installation\ias\workflow

For clients on patches V12-009-2 and earlier, the DBAs will need to manually set up the file on the client environments unless the client has no plans to upgrade to patch V12-010-1 and the workflow needs to be loaded.

Manual Method

This section contains procedures for loading workflows for older patches and as an alternative method to the standard method should the need arise.

Execution Command

To load a workflow, DBAs must execute the following command:

java -jar WFTParser.jar <database_name> <username> <password> <workflow>

For example:

java -jar WFTParser.jar devv12c owf_mgr devv12c WKF_CMIC_Registered_Invoice_WFT.wft

The following screenshot shows an example of the command and expected output.

NOTE: Larger workflows may take longer to load.

Troubleshooting During Upload

During upload, the following error may occur:

java.lang.UnsatisfiedLinkError: no ocijdbc11 in Java

or a very similar error message with either ocijdbc11.dll, ocijdbc8.dll or ocijdbc6.dll.

There are two possible explanations for the DLL not being found:

  • The PATH Variable on the OS is not set properly, and it is not finding the DLL.

  • Something is being executed that is setting PATH as part of the script and the PATH Variable is set to exclude the location of the directory where the DLL is found.

The solution is to perform a wild search on the drive/mount where the Oracle software is installed, to search for the missing file. If the file is located, for example in a directory called SOME_ORACLE_HOME\bin, the fix is to set the PATH as:

SET PATH= SOME_ORACLE_HOME\bin;%PATH%

Then re-running the statement again.