Testing the Make connection details for Invoke Command workflow

In this task, you verify that the workflow creates a connection details concept.

Before you begin

To test the workflow, you must know the name that was assigned to the ro-adapter-command-line adapter when it was configured on the grid. If you do not know the name, you can use the Grid Manager Manage> Adapters tab to find the name.

To test the workflow

1. In the TrueSight Orchestration Development Studio toolbar below the menu bar, click ExecuteProcessAction .
   If you have not already logged on to the grid, TrueSight Orchestration Development Studio displays the Login dialog box. TrueSight Orchestration Development Studio uses the peers and adapters on the grid to test the workflow.
2. If you have not already logged on to the grid, log on; otherwise, proceed to step 3.
3. In the Execution Mode dialog box, select Test as if triggered by a rule, schedule or SOAP, and then click OK.
4. In the Job Input Parameters dialog box, double-click in the Value field for the adapter parameter and type the name that was assigned to the ro-adapter-command-line adapter when it was configured on the grid.
   For this test, you do not need to provide values for any of the other input parameters.
5. Click OK.
   TrueSight Orchestration Development Studio runs the Make connection details for Invoke Command workflow. The console window opens below the design canvas, and the Process Log tab displays the results of the workflow execution. These are the same results that are posted to the processes.log file when the workflow is run on the grid. On the design canvas, the Make connection details Assign activity has a brown box around it to indicate that it has been executed.

6. Verify that the last line in the console window is The process terminated in the completed state.
   This message indicates that the workflow that you created ran to completion.

   Warning

   Note

   Do not clear or close the console window.

7. (optional) Review the contents of the console window.
   This is the information that would have been written to the log file if the workflow had been run on the grid.
   The connection details concept is shown immediately after "After Execution".

To gather sample data

1. Open a text editor and create a blank document.

2. From the console window, copy the XML definition of the ConnectionDetails and paste it in the blank document.
   The ConnectionDetails definition begins after the following text:
   After execution [connection details=
   An example definition is as follows:

   <ConnectionDetails xmlns="AutoPilot-OA-Common_Utilities">
     <adapter-name xmlns="">commandLineAdapter</adapter-name>
     <invocation-mechanism xmlns="">command-line</invocation-mechanism>
     <hostname xmlns="" />
     <port xmlns="" />
     <username xmlns="" />
     <password xmlns="" />
     <password-encryption-type xmlns="" />
     <target xmlns="" />
     <prompt xmlns="" />
     <login-prompt xmlns="" />
     <password-prompt xmlns="" />
     <working-dir xmlns=""></working-dir>
     <command-dir xmlns=""></command-dir>
     <command-encryption-type xmlns=""></command-encryption-type>
     <timeout xmlns=""></timeout>
     <connection-name xmlns="" />
     <terminate-connection xmlns="" />
     <known-hosts-config xmlns="" />
     <allow-unknown-hosts xmlns="" />
     <preferred-pk-algorithm xmlns="" />
   </ConnectionDetails>

   Success

   Tip

   When copying the definition, do not copy the square bracket ( ] ) that follows it in the console window.

3. Save the document as Conn_Details.txt.
4. In the console window, click Clear and then click Close.