Deploying application clients on z/OS

Why and when to perform this task

For J2EE application clients that will run on z/OS or OS/390, you may use one of the following options to define resources:

Both options produce identical output with one possible exception: the sequence in which resource definitions are stored in the Enterprise Archive (EAR) file of the application client. The client container on z/OS uses these resource definitions for resolving and creating an instance of the resources for the application client.

Before you begin: Make sure you have completed the following tasks:

  1. Develop the J2EE application client according to guidelines.
  2. Assemble the application client.
  3. Find out what resources are available on the z/OS system on which you will install the client. These resources include:
    • Enterprise beans
    • JMS message resources
    • JDBC databases
    • Java Mail providers
    • Environment entries (native types)
    • URLs
  4. Decide whether you want to provide resource properties for the ACRCT scripting tool on the command line or through an input file. If you do not specify required properties, the ACRCT scripting tool issues an error message to the MVS console and ends its processing.

    Recommendation: Determine which resource or provider properties are required.

Steps for this task

  1. Use the administrative console to install the application client on z/OS or OS/390.
  2. (Optional) Set up a plain text input file to provide on the command line when you start the ACRCT scripting tool.

    Rules:

    Sample: Input file for a data source provider:

    providertype=DataSourceProvider
    providername=DB2UDBV7
    name="PolicyDatasource"
    description="Datasource for Policy App"
    jndiname=jdbc/PolicyDS
    databasename=POLICYAPP
    user=dbuser
    password=dbpw
    reenterpassword=dbpw
    property.my.resource.property.one=value1
    property.my.resource.property.two=value2

  3. On z/OS or OS/390, start the ACRCT scripting tool by invoking the shell script clientConfig in the UNIX System Services (USS) environment.

    Example:

    /usr/lpp/WebSphere/V5R0M0/bin/clientConfig.sh

    Rule: You must specify the application client's Enterprise Archive (EAR) file on the command line. You may either specify resource parameters directly on the command line, or specify an input file. The syntax and parameter descriptions appear in Application Client Resource Configuration Tool (ACRCT) Scripting tool for z/OS.
    • If the resource parameters are properly specified, the ACRCT scripting tool updates the application client's client-resources.xmi file with appropriate resource definitions.
    • If the resource parameters are not properly specified or are missing, the ACRCT scripting tool issues an error message to the MVS console, and ends its processing.

    Tip: If you receive an error message in response to the invocation, consider using the help function described in Application Client Resource Configuration Tool (ACRCT) Scripting tool for z/OS.

Results

When the scripting tool successfully completes, the application client's EAR file is updated with the appropriate resource definitions.

What to do next

When you have finished defining or updating the application client's resources, launch the application client.

Related reference
Properties for data source providers
Properties for data sources
Properties for mail providers
Properties for mail sessions



Searchable topic ID:   tcli_tconfigclientzos
Last updated: Jun 21, 2007 9:56:50 PM CDT    WebSphere Application Server for z/OS, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.zseries.doc/info/zseries/ae/tcli_tconfigclientzos.html

Library | Support | Terms of Use | Feedback