Testing your scenario

If you have configured your identity mapping correctly, you can now run the ECIDateTime application successfully to test the scenario and verify that the application is being run with the correctly mapped RACF® ID.

  1. On CICS®, start CEDX debugging on the CSMI mirror transaction on the CICS server by issuing the following CEDX CSMI command:
    CEDX CSMI
    This switches on the debug tool.
  2. On IBM® WebSphere® Application Server, run the ECIDateTime application. To do this, start launchClient from the command line by issuing the following command: 
    app_server_root/bin/launchClient path/ECIDateTime.ear
    app_server_root/bin/launchClient path/ECIDateTime.ear
    Where path is the path to the ECIDateTime.ear file.
  3. On IBM WebSphere Application Server, when prompted for a user name and password, provide the user name and password defined in the LDAP server: 
    uid=CTGuser1,ou=TMS,dc=CTGTest,o=COMPANYCTG
    On CICS, when the transaction starts, CEDX intercepts the program and displays the program initiation screen until you press the Enter key. You can now examine the task ID number before the transaction completes:
    Figure 1. Program initiation screen
  4. On CICS, use a second sign-on to log on to the server and run CEMT INQ TASK on the CSMI task:
    Figure 2. CEMT INQ task screen

    The Use field contains the RACF ID to which the distinguished name maps. The RACF ID in this scenario is TESTID and is evidence that the scenario is operating correctly.

  5. On CICS, unlock the CEDX session by pressing the PF3 key. On IBM WebSphere Application Server, the launchClient returns the date and time:
    WSCL0014I: Invoking the Application Client class 
com.ibm.ctg.samples.jee.ECIDateTimeClient 
CICS Date/Time=27/10/09 15:48:45
    WSCL0014I: Invoking the Application Client class 
com.ibm.ctg.samples.jee.ECIDateTimeClient 
CICS Date/Time=27/10/09 15:48:45