Introducing the dbDesignGenerator for simple database creation script generation in WebSphere Process Server
Mykyta_Kostovskyy 270000N0GT Visits (3375)
In this post I would like to introduce the Database Design Tool (DDT) that comes with WebSphere Process Server (WPS) V7.
This tool is useful for those who want to configure all the required database resources in WebSphere Process Server: common database, messaging engine database, CEI and BPC databases. This tool is also helpful for those who want to have a custom configuration for each database. For example, when different databases need to be configured on different servers or even, when those databases are of different database types, such as DB2, Oracle or Microsoft SQL Server.
The Database Design Tool is located under <wps
If you start the tool without any options, you will get into interactive mode and will see the following options:
1. Create a database design for Standalone profile or Deployment Environment
As you can see, you may configure a database for a single component or for the entire environment. The most interesting feature available is the ability to generate the database from one that already exists, which may be helpful in creating the production database from the test environment.
If you create a configuration for one of the components, at the end of the wizard you will get <name>.properties files created which are in text property-value format and you can edit parameters inside the files with the text editor. This is quite useful if your Database Administrator (DBA), for example, needs to adjust a port number or some other details that may be not known during the dbDesignGenerator execution.
If you generate a configuration for the entire topology, like the deployment environment, at the end of the wizard you will get a <name>.dbDesign file which can be used later during profile creation in the Profile Management Tool (PMT) to configure the entire WebSphere Process Server database resources and WebSphere Variables to get the database connectivity just after first start of the environment. This will save you a lot of time configuring the separate resources and will prevent you from any typos.
With the .dbDesign file or .properties file in hand, you can let the tool generate SQL scripts for every database at any time you need; they will be saved separated by the component folder chosen before. These SQL scripts than can be used by DBAs to apply it accordingly on the database side. See this sample properties file attachment that was generated with the dbDesignGenerator. (The attachments in this post are plain text files that were saved in HTML format with line breaks.)
Here is an example MyCu
For more information on database usage please refer to the WebSphere Process Server information center: Creating the database design file using the database design tool.
Finally, please keep in mind the limitation it has for the CEI database and in case you need to use a different type of database setting for each component, you will have to additionally go through each database configuration step for each component database in order to define custom parameters, like different hostname, schema name, database types, etc.
Please feel free to leave your feedback below as a comment to my post. I look forward to reading your thoughts as well!