How to configure Blue Yonder WMS to record Cycle's MOCA executions in the System Auditing table
Problem
With a MOCA connection Cycle can perform many functions in the WMS including executing MOCA commands and making local syntax calls. While these commands and calls are usually necessary for test automation, Cycle is an external application acting on the WMS. It may be beneficial or even required for application owners to track exactly what Cycle is executing.
Solution
The Cycle MOCA connection step, I connect to MOCA at "<ADDRESS>" logged in as "<USERNAME>" with password "<PASSWORD>" publishes out CYCLE as its application identifier. This allows the Blue Yonder WMS to track any execution performed in the session. All queries, updates, inserts, scripts or MOCA commands will be recorded in the sys_audit table.
Below is the standard WMS policy SYSTEM-AUDITING->INTERACTIVE-AUDITING->APPS-TO-AUDIT. To enable the WMS to track Cycle activity set Return String One = CYCLE and Return Number One = 1 (shown below).
NOTE: This policy change requires a hard bounce of the MOCA instance.
Example
The Feature Scenario shown below connects to MOCA, runs 3 execution types against the WMS and closes the MOCA connection.
After running the Feature, System Audit Record Maintenance (sys_audit table) will show the commands executed identifying Cycle as the application. Some command text may be too long for the Blue Yonder grid to show but a hover over of the field will display the syntax.
Related Articles
How to control Blue Yonder WMS authorization of Cycle MOCA connections
Problem When connecting Cycle to a Blue Yonder WMS, it may be necessary to limit Cycle's access. Solution The Cycle MOCA connection step, I connect to MOCA at "<ADDRESS>" logged in as "<USERNAME>" with password "<PASSWORD>" includes a check of the ...How to use MOCA Examples as a Scenario Outline data source
With the enhancements to Scenario Outlines, it is now possible to use multiple sources for test parameter data. Previously, parameters were set in the Feature in an Examples section specified and maintained by the user. The addition of Example Row, ..."Unexpected error occurred communicating with MOCA server: General SSLEngine problem."
Problem I receive the error: "Unexpected error occurred communicating with MOCA server: General SSLEngine problem." while trying to connect to a JDA WMS instance in Cycle. Solution This error occurs when there is an issue with SSL validation. Cycle ...Does Cycle have a way to test the Integration Layer of my WMS?
Problem System communications while critical can be overlooked in the testing Cycle. Especially when the integration layer is run by different groups within an organization, trying to get valid data coordinated is often difficult. Solution Cycle ...Can Cycle execute MOCA and Local Syntax?
Problem Cycle Features built to interact with and test the JDA WMS need to run queries, execute statements and perform validations directly against the database. Solution JDA WMS provides a framework to ease database interaction called MOCA. Cycle ...