The Profile Management Tool can create or augment a configuration
for one or more WebSphere® ESB stand-alone
server profiles configured with a DB2® for i5/OS® database on a remote i5/OS server. The remote i5/OS server hosting the DB2 for i5/OS database does not have WebSphere ESB installed
on it.
Before you begin
If your WebSphere ESB installation
resides on a Linux®, UNIX®, or Windows® server and your database resides
on a remote i5/OS server,
you must download the IBM® Toolbox
for Java™ JDBC driver (jt400.jar)
from the SOURCEFORGE.NET Web site at https://sourceforge.net/projects/jt400 to
a local temporary directory.
Procedure
- In the Welcome panel for the Profile Management Tool click Next.
Note: If any WebSphere Application Server profiles
are found that can be augmented into WebSphere ESB profiles,
the Existing Profile Detection panel is displayed. Do not augment
an existing profile, but instead choose to create a new profile.
- In the Environment Selection panel, select WebSphere
Enterprise Service Bus. Click Next.
- In the Profile Type Selection panel, select the option
to create a Stand-alone server profile. ClickNext.
- In the Profile Creation Options panel, you can specify
whether to create a Typical profile using default settings, or an
Advanced profile. Select Advanced profile creation.
Click Next.
- In the Optional Application Deployment panel, ensure that
the check box for deployment of the administrative console is selected,
and accept the default for the deployment of the default and sample
applications. Click Next.
- In the Profile Name and Location panel, enter a unique
name and unique location for this profile. A default name and location
are presented initially. A default directory is presented under $user_data_root/profiles/profile_name.
If any other profiles exist, you are given the option of making this
new profile the default profile. You can also select to create the
server with a development template. Click Next.
- In the Node, Host, and Cell Names panel, you must specify
a unique node. A default node name is provided, but you can change
the node name providing the new name is unique. Click Next.
- In the Administrative Security panel, either clear the
check box or provide user ID and password information. Click Next.
- In the Port value assignment panel, default port values
are provided. You can specify different port values if necessary.
Click Next.
- If this WebSphere ESB profile
creation is on Windows or Linux, you are presented with
the Windows or Linux service definition panel and can optionally
set up this profile to run as a Windows or Linux service. The server hosting
the WebSphere ESB must
have a relational database entry pointing to the remote server, or
you must create such an entry if one does not exist. Click Next.
- Optional: In the Web Server Definition panel,
you have the option of choosing to create a Web server definition.
Click Next.
Note: On i5/OS it is recommended to
not create
the Web server definition using the Profile Management Tool. Therefore,
do not enable this option on the Web Server Definition panel. You
will need to use the IBM HTTP
Server for iSeries® configuration
and administration forms which both creates the Web server definition
and an HTTP server instance. It also correctly associates the HTTP
server to this Web server definition. For more information, see the
topic
Configuring an HTTP server instance in the WebSphere Application Server
Network Deployment for i5/OS,
version 6.1 information center.
- On the Business Space Configuration
panel, select the Configure Business Space check
box to set up Business Space powered by WebSphere,
an integrated user experience for application users across the IBM Websphere Business Process Management
portfolio and then click Next. Configuring Business Space sets up an
integrated GUI for the business users of your application for this
profile.
Important: Business Space is supported
with the following database products: Derby Embedded, Derby Network
Server, DB2 Universal, DB2 Universal Runtime Client, DB2 for i5/OS, Oracle 9i, Oracle 10g, and Oracle 11g.
If
the database you use for WebSphere ESB does
not match the supported databases for Business Space, a Derby Embedded
database is selected for the Business Space configuration.
You cannot federate this profile into a deployment environment later,
because Derby Embedded is not supported for deployment environments.
- In the Database Configuration panel,
select the entry for DB2 UDB for iSeries (Toolbox) under Choose
a database product. This causes *SYSBAS to appear in the Database
name field.
- Select Create a new remote database.
- Select the check box next to Delay execution
of database scripts (must select if using a remote database) if
you want to copy and run the database scripts manually on the remote
database server.
- Select Use this database for Messaging Engines
(MEs).
- Click Next.
- In the Database Configuration (Part 2) panel, enter a valid
User Name and Password to authenticate to the remote i5/OS DB2 database.
- Enter the Location (directory) of the JDBC driver class
path files (jt400.jar).
- Enter the Database server host name (for example IP
address) of the i5/OS server
where the remote DB2 for i5/OS database is located.
- Enter the Database collection name, WPRCSDB by default.
The first three characters of the Schema name must be unique for the
database that is being hosted on the remote i5/OS server.
- Click Next.
- The Profile summary panel is displayed. Click Next.
- The profile creation is complete and deselects the Launch
First steps option. Click Finish.
- Export the DDL if needed for both the Common Event Infrastructure
and the Common database to the remote i5/OS system.
The DDL, in the form of generated database scripts, are in locations
you specified earlier in the Common Event Infrastructure database
configuration panels and the Database configuration panels. You can
provide the scripts by a number of different methods to the Administrator.
- The Administrator must run the CEI scripts to set up the
remote DB2 database tables for
EVENT if both the local and remote database systems are not i5/OS platforms, or if Delay
execution of database scripts (must select if using a remote database) was
selected. The Administrator must also run the commonDB scripts for
WPRCSDB on the remote i5/OS system
if Create a new remote database was not selected.
- If your WebSphere ESB installation
resides on a Linux, UNIX, or Windows server and your database resides
on a remote i5/OS server,
start the server and use the administrative console to verify that
the value of the WebSphere Application
Server environment variable OS400_TOOLBOX_JDBC_DRIVER_PATH to the
location of the jt400.jar file you downloaded.
Then stop and restart the server.
Important: You
might receive error messages when you start the server before you
set the environment variable. These errors resolve when you stop and
restart the server.
Results
You have created a stand-alone profile to connect to a remote
database.
DB2 for i5/OS tables and collections have
been generated on a remote i5/OS system
for CEI (EVENT), CommonDB,
Service Integration Bus, and WebSphere Enterprise
Service Bus Message
Logger.