Copying data or running a program based on the success or failure of a Process step (step injection)

This scenario builds on the basic Connect:Direct® configuration by adding step injection functions to the PNODE connection.

About this task

Step injection allows you to insert Connect:Direct Process statements into the communications session with the SNODE independent of the PNODE Process statements. These injected statements can provide real-time notification of file delivery, submit applications, run operating system jobs and commands, and submit other Connect:Direct Processes, all without needing to provide an exit program on the SNODE or without changing the PNODE Process. Even though the PNODE has no indication that these steps executed on the SNODE, step injection is defined on the PNODE record in Secure Proxy. The results of these steps are logged in the statistics file of the SNODE.

Procedure

To use step injection, define one or more of the following step injection functions:
  • Copy session or certificate information to a file at the SNODE at the end of a successful step.
  • Execute a Connect:Direct Runtask, Runjob, or Submit step on the SNODE at the end of a successful step or run operating system commands, jobs, or programs.
  • Copy session or certificate information to a file at the SNODE at the end of a failed step.
  • Execute a Connect:Direct Runtask, Runjob, or Submit step on the SNODE at the end of a failed step or run operating system commands, jobs, or programs.
  • Use variables to define file names and parameters in a Runtask, Runjob, or Process step.

Results

Step Injection actions that are referenced in a netmap entry are only performed when the node is communicating as the PNODE in the transaction.