The Profile Management Tool can create a WebSphere® ESB deployment
manager profile configured with a DB2® for i5/OS® database on a remote i5/OS server. In a similar way,
the Profile Management Tool can augment a WebSphere Application Server Network Deployment
manager profile into a WebSphere ESB deployment
manager profile configured for a remote database connection. The remote i5/OS server hosting the DB2 for i5/OS database does not have the WebSphere ESB product
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 the WebSphere ESB option.
Click Next.
- In the Profile Type Selection panel, select the option
to create a Deployment Manager profile. Click Next.
- In the Profile Creation Options panel, you can specify
whether to create a Typical profile using default settings, or an
Advanced profile. Click Advanced profile creation.
Click Next.
- In the Optional Application Deployment panel, ensure that
the check box for deployment of the administrative console is selected.
Click Next.
- In the 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 and cell name. Default node names and cell names are
provided, but you can change the node name providing the new name
is unique. Click Next.
- In the Administrative Security panel, do not enable administrative
security. 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. 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 create the Web server definition and an HTTP server instance.
They also correctly associate 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.
- 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 Toolbox 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 collection name must be unique for
the database that is being hosted on the remote i5/OS server.
- Click Next.
- The Profile summary panel displays. Click Next.
- The Profile creation is complete, and the Launch
first steps option is unselected. Click Finish.
Results
You have created a deployment manager
profile to connect to a remote database. DB2 for i5/OS tables and collections have
been generated on a remote i5/OS system
for Common
database, Service Integration Bus, and WebSphere Enterprise
Service Bus Message
Logger.
What to do next
You can start the deployment manager. In
a deployment environment, you must create and configure other databases,
create custom profiles and federate them to your deployment manager,
create servers, create clusters if you want workload management capabilities,
and perform other tasks specific to your planned installation environment.
Your planned environment dictates which tasks you must perform and
the order in which you perform them.