Application Client Resource Configuration Scripting tool for z/OS

Syntax

This section describes the command line syntax for the z/OS scripting version of the Application Client Resource Configuration Tool (ACRCT). The ACRCT scripting tool for z/OS allows you to:

For define and delete actions, the ACRCT scripting tool alters the Enterprise Archive (EAR) file for the application client, as instructed by options you specify. If the ACRCT scripting tool encounters an error at any time during its processing, the tool issues an error message to the MVS console and terminates without changing the original contents of the application client EAR file.

When you use the ACRCT scripting tool, you may specify:

The command line invocation syntax for the ACRCT scripting tool follows. When you have a choice of one required keyword, those keywords appear within brackets [].

Parameters

where:

-earfile
Is a required parameter that indicates the input filename of the application client EAR file.
earfilename
Identifies the location and name of the EAR file that contains the application client. This path and filename must directly follow the -earfile parameter.
-define
Instructs the scripting tool to define a provider or resource based on the input properties.
-delete
Instructs the scripting tool to delete a provider or resource based on the input properties.
-list
Instructs the scripting tool to the properties of a particular provider or resource, based on the input properties.
-help
Instructs the scripting tool to list basic examples and guidelines for using quotes around key values.
-provider
Indicates that the object to be defined or deleted, or for which properties are to be listed, is a provider.
-resource
Indicates that the object to be defined or deleted, or for which properties are to be listed, is a resource.
-f
Indicates that the input properties for the provider or resource are provided in an input file, rather than specified directly on the command line.
inputfile
Identifies the location and name of the input file that contains the provider or resource properties. This path and filename must directly follow the -f parameter.
key=value
Specifies an input property for the provider or resource, in the form of key and value pairs.

Rules:

  • You must use lowercase for keys.
  • You cannot use blanks within a key and value pair; a blank signals the end of one key/value pair.
  • Because blanks separate key and value pairs, you must be careful when a value you supply contains blanks. When you specify a value that contains blanks, enclose the value in single quotes or double quotes. Because some shells processes quotes differently, you might have to do some testing to determine whether you must use single or double quotes.

    Example: Suppose you invoke the scripting tool, passing this input:

    /WebSphere/V5R0M0/AppServer/bin:>acrct -earfile 
    usr/lpp/myapps/applclient2.ear -define 
    -provider providername='WebSphere JMS Provider'

    The response is an error message along with an echo of the input string that the shell receives, followed by the input string as the scripting tool will process it:

    -earfile usr/lpp/myapps/applclient2.ear -define 
    -provider providername=WebSphere JMS Provider
    
    
    String to be parsed by the Scripting Tool:
    
    -earfile usr/lpp/myapps/applclient2.ear -define 
    -provider providername=WebSphere JMS Provider
    
    
    Ear file is missing or is improperly specified.
    Invalid syntax: -earfile usr/lpp/myapps/applclient2.ear -define -provider providername=WebSphere JMS Provider
    
    As you can see from the response, the shell has stripped off the single quotes, and passes invalid input to the scripting tool. To correct the problem, you need to use double quotes.

  • The number of key and value pairs you specify depends on the type of resource or provider you are configuring. For each resource to be configured, use this information to determine which resource or provider properties are required.

Example

The following examples demonstrate correct syntax:

Defining a new provider for an application client, using an input file:
acrct -earfile usr/lpp/myapps/applclient1.ear -define -provider -f usr/lpp/myapps/inputProvider1.def
Defining a new provider for an application client, specifying properties directly on the command line:
acrct -earfile usr/lpp/myapps/applclient2.ear -define -provider -p providertype=DataSourceProvider name=DB2UDBV7
Defining a new provider and deleting the resource it replaces, in the same EAR file:
acrct -earfile usr/lpp/myapps/applclient1.ear -define -provider -f usr/lpp/myapps/inputProvider2.def -delete -resource -f usr/lpp/myapps/inputProvider1.def
Defining a new provider in more than one EAR file:
acrct -earfile usr/lpp/myapps/applclient1.ear -define -provider -f usr/lpp/myapps/inputProvider2.def -earfile usr/lpp/myapps/applclient2.ear -define -provider -f usr/lpp/myapps/inputProvider2.def



Searchable topic ID:   rcli_configclientzoscmd
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/rcli_configclientzoscmd.html

Library | Support | Terms of Use | Feedback