Before creating or augmenting a profile, you must ensure
that a series of prerequisites have been met.
Note: You can deploy WebSphere® Service Registry and Repository
to a specific federated server or cluster only once. However, you
can deploy it to multiple federated servers or clusters in the same
cell.
The prerequisites are as follows:
You must have an existing installation of WebSphere Service Registry and Repository.
If you do not, see Installing the software for installation procedures.
You must create profiles using the same user ID used to install
the product.
You must know the type of profile you want to create or augment.
For more information about profiles, see Profiles.
You must follow the correct procedure to create or augment
the profile:
- If you want to create a new profile rather than augment an existing
profile, see one of the following topics:
- If you want to augment an existing WebSphere Application Server, WebSphere Application Server Network Deployment, Business Process Management profile into a WebSphere Service Registry
and Repository profile, see one of the following topics
You must shut down any servers associated with a profile you
plan to augment.
You must review Naming considerations for profiles, nodes, servers, hosts, and cells for
information about reserved terms and issues that you must consider
when naming your profile, node, host, server (if applicable), and
cell (if applicable).
You must have enough disk and temporary space to create or
augment the new profile. For information about space requirements,
see WSRR detailed
system requirements at http://www.ibm.com/software/integration/wsrr/sysreqs/ and
select the link to your version of WSRR.
The following prerequisites relate to product databases:
- During the profile creation or augmentation process for stand-alone profiles, you are configuring
the database used by WebSphere Service
Registry and Repository, the WSRR Activity Logging database and the
Service Integration Bus Message Engine database. Whether you plan
to create new databases and tables or postpone actual database configuration
by producing scripts that must be run manually by you or your database
administrator (DBA), you must know the database details listed in
the following topic:
- If you plan to use Oracle as your database product, you must have
a user ID that has SYSDBA privileges before creating any profile.
- If you plan to use or create the WSRR database(s) on a remote
server, you must create it(them) before beginning to create or augment
the profile. You can create a database on the local server or use
an existing one on a remote server. See Creating the WSRR database from scripts you have created for the location of default
scripts you can use to create this database.
- If you plan to use DB2®,
you must perform the following steps before creating or augmenting
a profile:
- Ensure that DB2 is started
by the database instance owner.
- If you are configuring a DB2 database
on a DB2 client with the server
on a remote system, make sure the client system is configured to communicate
with the server and that the DB2 node
is cataloged. For more information, refer to the DB2 Universal Database™ documentation.
On Linux and UNIX platforms: If you are
configuring a DB2 database on
a Linux or UNIX system, source the database environment
by performing the following steps: - Modify /etc/group and make sure the user
ID that installed the product is in the same group as the db2instance.
- Source the database environment by running the db2instance/sqllib/db2profile script
(replace db2instance with the name of your database
instance).
After you have reviewed these prerequisites, return to the topic
from which you accessed this one.