Creating the DB2 databases and storage groups using SPUFI or DSNTEP2

The zWBMConfig.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.

1. Create the DB2 for z/OS storage groups.
2. Populate the databases using the generated DDL scripts. The location of the generated DDL scripts depends on how they were generated.
   The default location for DDL generated by DbDesignGenerator.sh is in the directories under the following locations:

   • <WAS_ROOT>/AppServer/util/dbUtils for a stand-alone configuration.
   • <WAS_ROOT>/DeploymentManager/util/dbUtils for a network deployment configuration.
   For DDL generated by other means, the DDL is in the directories under the following locations:

   • <WAS_ROOT>/AppServer/profiles/profile_name/dbScripts for a stand-alone configuration.
   • <WAS_ROOT>/DeploymentManager/profiles/profile_name/dbScripts.wbm for a network deployment configuration.

   Where <WAS_ROOT> is the high level directory of your WebSphere® Application Server configuration.

3. If you are running the DDL from a USS environment, assign the appropriate permissions to the copies of the files; for example:

   chmod 755 createDatabase.sql
   chmod 755 createTables.sql

4. Edit the values in the file to suit your needs. The database names, storage groups and schema names are customized 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 database.
   Note: The files can be 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 createDatabase.sql > 
   createDatabase_EBCDIC.sql
   iconv –t IBM-1047 –f ISO8859-1 createTables.sql > 
   createTables_EBCDIC.sql

   If you have converted 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 createDatabase_EBCDIC.sql >
   createDatabase.sql
   iconv -t ISO8859-1 -f IBM-1047 createTables_EBCDIC.sql >
   createTables.sql

5. Optional: If you want to create database objects outside of the USS environment, for example via SPUFI or DSNTEP2, you can copy the customized DDL from USS to a partitioned dataset.
6. 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.

   DSNTEP2

   A sample dynamic SQL program provided with the DB2 for z/OS product.

7. Verify that the database, storage group, and tables have been created successfully with no errors by inspecting the output.
8. If you are creating a stand-alone configuration, verify the IBM Business Monitor installation:
   1. Start the server.
   2. 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

   3. Log in to the administrative console.
   4. Verify that you can see IBM Business Monitor for z/OS on the Welcome page. You can click it for more information.
   5. Navigate around the console to check that the server has a status of started. Also check that 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 details about the failure.