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:
Before you begin: Make sure you have completed the following tasks:
Recommendation: Determine which resource or provider properties are required.
Steps for this task
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
Example:
/usr/lpp/WebSphere/V5R0M0/bin/clientConfig.shRule: 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.
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.