The zWESBConfig.sh configuration script generates
Data Definition Language (DDL) scripts that you can use to create
the DB2® database objects for the configuration. There
are several tools that you can use to run the DDL scripts to create
the database objects for your configuration.
Before you begin
Before you create the DB2 databases and storage groups,
you must complete the following task:
About this task
You can run the DDL scripts using DB2 Connect™, SPUFI, or DSNTEP2.
If you want to work in the USS environment, you
can run the DDL scripts using the DBUtility.sh script, which is also
supplied with WebSphere® ESB.
Important: After converting
from ASCII to EBCDIC check that no SQL statements exceed 71 characters
in length because this will lead to line truncation and invalid statements
when copying to fixed width MVS datasets.
Procedure
- Create the databases and storage groups using the sample
scripts. Copy and paste the scripts into the environment
appropriate to the tool you will use and customize the values as required;
for example copy to MVS data sets if you are using SPUFI or copy to
scripts in USS if you are using DBUtility.sh.
- Populate the databases using the DDL scripts that were
generated by the configuration script. Copy the generated DDL script
files from the following locations to your working directory.
For a stand-alone configuration:
- /WebSphere/V6R2M0/AppServer/profiles/default/dbscripts/CommonDB/database_type/database_name
- /WebSphere/V6R2M0/AppServer/profiles/default/dbscripts/CEI_database_name/ddl
For a network deployment configuration (only the CommonDB
database is populated at this stage):
- /WebSphere/V6R2M0/DeploymentManager/profiles/default/dbscripts/CommonDB/ database_type /database_name
Where database_type is the database
version (for example, DB2zOSV8 for DB2 for z/OS® version 8.1), database_name is the name
of the database that you are creating (which you specified in the
response file for the configuration script), CEI_database_name is the name of the CEI database.
- Assign the appropriate permissions to the copies of the
files; for example:
chmod 755 createTable_AppScheduler.sql
- Edit the values in the file to suit your needs. The database names, storage groups and schema names are customised
by the product configuration process. Check the values in each file
to make sure they match the values that you entered in the response
file that provided input to the configuration script and are suitable
for your data base.
Note: The files are provided in ASCII format.
If the tools that you use to view, edit, and run the scripts require
the scripts to be in EBCDIC format, use the
iconv command to convert the file to EBCDIC. For example:
iconv –t IBM-1047 –f ISO8859-1 createTable_AppScheduler.sql >
createTable_AppScheduler_EBCDIC.sql
If you the convert the file from ASCII format to EBCDIC
but need to run the file in ASCII format, use iconv to convert the file back to ASCII. For example:
iconv -t ISO8859-1 -f IBM-1047 createTable_AppScheduler_EBCDIC.sql >
createTable_AppScheduler.sql
- Run the customized scripts using the tool of your choice. For example:
- SPUFI
- A utility that runs SQL scripts from z/OS.
SPUFI uses EBCDIC input.
- DBUtility.sh
- DBUtility.sh is a utility that is supplied with WebSphere ESB for z/OS and installed
in the installation file system. For example: /usr/lpp/zWESB/V6R2/bin/DBUtility.sh. You can use this utility to create the database and storage groups,
as well as to run the SQL to create the database tables later, from
USS. DBUtility.sh uses ASCII input. Here is an example of the syntax
used with the DBUtility.sh script:
/WebSphere/V6S03Z1/AppServer/profiles/default/bin/DBUtility.sh
createTable
-DdbStorageGroup=S3DBSTO
-DdbSchemaName=S3CELL
-DsqlScriptName.default=createTable_AppScheduler.sql
-DsqlScriptPath.default=/WebSphere/V6S03Z1/AppServer/profiles/default/dbscripts/CommonDB/DB2zOSV8/S3CELLDB/createTable_AppScheduler.sql
-DdbType=DB2UDBOS390_V8_1
-DdbName=S3CELLDB
-DprofileName=default
-DprofilePath=/WebSphere/V6S03Z1/AppServer/profiles/default
-DdbJDBCProperties=/wps/dbscripts/db2v8
-DdbConnectionLocation=DSN810PP
-DdbJDBCClasspath=/usr/lpp/db2810/db2810/jcc/classes
-DdbUserId=wsadmin
-DdbPassword=password
-DdbDelayConfig=false
-DdbCreateNew=false
-DdbHostName=winmvsp1.hursley.ibm.com
-DdbServerPort=448
>/tmp/output.out 2>>/tmp/error.out
- Verify that the database, storage group and tables have
been created successfully with no errors by inspecting the output.
- If you are creating a stand-alone configuration, verify
the WebSphere Process Server installation:
- Start the server.
- Open the administrative console by opening a browser
window and typing the URL of the server that you want to view. For
example:
http://server_name.domain_name:port_number/admin
- Log in to the administrative console.
- Verify you can see WebSphere ESB on the Welcome
page. You can click on this for more information.
- Navigate around the console to check that the server
has a status of started. Also check all the applications are started,
and that the messaging engines are started. If anything has failed
to start you can look in the server job logs for "SEVERE" or "WARNING"
messages that provide detail about the failure.
Results
The DB2 databases and storage groups are created
and populated with the necessary database objects, such as tables
and indexes.
What to do next
If you are creating a stand-alone configuration, you can
now deploy applications to the server.
If you are creating a
network deployment configuration, next, you must create one or more
empty nodes to add to the deployment manager cell. See Configuring an empty node with WebSphere ESB.