EJB CICS sample application task guide: Deployment

sgd020


The EJB CICS sample application task guide

Install into CICS using CICS Development Deployment Tool

The CICS development deployment tool provides a means of deploying a 1.1 EJB-JAR file into CICS directly from a development workstation without the need create explicit CICS resource definitions. The tool is configured by system programmers by means of the XML deployment configuration file (DCF), which specifies user and CorbaServer information as well as a number of other parameters that relate to the operation of the tool.

Application programmers run the CICS Development Deployment Tool through a standard web browser. Before invoking the tool it is assumed that:

    Install DJAR in CICS

  1. Start web browser and enter the URL of the Web application: http://hostname/CICS_EJB/CICSC021.
    This opens the User Login page.
  2. Enter your user ID and password. This user ID must match the one you use to log on to MVS and must be set up in the deployment configuration file. The user ID must also have access to the required HFS shelf directories. These were set up during the configuration of the CICS Development Deployment tool.
  3. Check the Save details box if you prefer not to enter your user details for every JAR deployment. However this is valid only for the lifetime of the current web browser session. If the current browser session expires, you have to log in again to access the tool.

    Development Deployment Tool page: User log in

  4. Click Submit to open the Deployment Information page.
  5. Choose the Deploy option from the drop-down menu.
  6. Select a target CorbaServer from the list of those available. The selected CorbaServer specifies the run time environment within the CICS EJB server in which the enterprise beans in your selected JAR are to be run. The CORBASERVER name shown corresponds to the value of CSV1 in the sample DCF XML document.
  7. If it is not already shown, enter the full path of the ejb-jar file located on your workstation into the JAR file path field. Sample: C:\cicsejb\SampleEJB.jar

    Development Deployment Tool page: Deployment information

  8. Click Deploy to start the operation.

    Development Deployment Tool page: Progress

    The deploy operation:

    1. Creates the necessary CICS resource definitions and stores the definitions in the ejb-jar file in XMI format for possible later use.
    2. Publishes the name of the ejb-jar file to a nameserver on WebSphere Application Server.
    3. Uploads the ejb-jar file from the client to WebSphere, where it is validated, then transferred by FTP to HFS storage on OS/390. The target HFS directory /usr/deployedJARs corresponds to the value of DeployJarBase defined in the sample sample DCF XML document. The full path created by the development deployment tool to store the JAR file is: /usr/deployedJARs/CICS021/<userid>/CSV1/SampleEJB.jar.
    When the operation is complete, the Deploy Results page is displayed.

    Development Deployment Tool page: Deploy Result

    If a problem occurs during deployment a message is issued. Messages are color coded -- blue for warning, pink for an error. Select the ? icon to the right of the message to display further information about the problem.

  9. Click View CICS definitions to see the CICS resource definitions that have been created for the JAR.

    Development Deployment Tool page: Resource definitions

You are now ready to test your EJB CICS application.

Use the Undeploy option to remove the CICS resource definitions associated with a previously deployed ejb-jar file. Undeploy does not remove the ejb-jar file itself from HFS.