Note your IBM® WebSphere® Application Server and
DBMS installation and configuration settings on this form. You will
need this information when you install or upgrade the IBM Records Manager engine, administration client,
and supporting utilities.
You can find your WebSphere Application Server configuration
settings in the WebSphere Application Server administrative
console under .
Table 1. WebSphere Application Server configuration| Setting |
Default Value |
Description |
Actual Value |
| WebSphere Application Server directory |
none |
The directory where WebSphere Application Server is installed. Tip: For
the Solaris operating system on Sun's Opteron platform, the installation
program does not automatically detect the WebSphere Application Server installation path and pre-populate
the field. You must browse to the WebSphere Application Server installation
directory.
|
|
| Application server name |
AppSrv01/server1 |
The profile name and application server
name where the IBM Records Manager engine and
administration client components will be deployed. |
|
Table 2. WebSphere Application Server security configuration (if
administrative security is enabled)| Setting |
Default Value |
Description |
Actual Value |
| WebSphere Application Server administration
ID and password |
|
The login ID and password for the user who
has administrative privileges. Required if WebSphere Application Server security is enabled. |
|
Table 3. Connection
factory configuration| Setting |
Default Value |
Description |
Actual Value |
| Connection user ID |
none |
The ID of the user. The ID is required if
security is enabled: If you have enabled administrative security for WebSphere Application Server, enter the alias that specifies
the user ID used to authenticate the creation of a new connection
to the JMS provider. The ID must exist in the active user registry. |
|
| Connection user password |
none |
Password for the connection user ID. |
|
Table 4. Engine
configuration| Setting |
Default Value |
Description |
Actual Value |
| Data source name |
none |
The name you choose for the data source. |
|
| DBMS server name |
none |
The name of your DB2, Oracle, or SQL Server
server |
|
Table 5. IBM Records Manager Administration client configuration| Setting |
Default value |
Description |
Actual value |
| Context root |
IRMClient |
The unique identifier used to
start theIBM Records Manager administration
client on the application server. This is a customizable value, and
is the ending of the URL.
For example, using the default context
root you would start theIBM Records Manager administration
client on the server localhost, by entering: http://localhost:9080/IRMClient/.
|
|
| Host name |
none |
The host name or IP address of the machine where
the IBM Records Manager engine is installed. |
|
| BOOTSTRAP_ADDRESS port |
none |
The JNDI service port for the host
where you are installing the IBM Records Manager engine.
This field specifies the port number on which the application server
Object Request Broker (ORB) listens for requests. The port number
can be found in the WebSphere Application Server administrative
console as BOOTSTRAP_ ADDRESS in Ports. |
|
| Records administrator ID |
none |
The name or ID of the user who has administrator
privileges in the IBM Records Manager administrative
client. |
|
| Password |
none |
The password that the records administrator
uses to log in to the IBM Records Manager administrative
client. |
|
Table 6. Web
services configuration| Setting |
Default value |
Description |
Actual value |
| Context root |
IRMWebServices |
The unique identifier used to
access the IBM Records Manager engine on the
application server. This is a customizable value, and is the ending
of the URL.
For example, using the default context root you
would start theIBM Records Manager engine on
the server called irmut03, by entering: http://irmut03:9080/IRMWebServices/services/LoginManagerEJB."
|
|
Table 7. Import/export
utility configuration| Setting |
Default value |
Description |
Actual value |
| Host name |
none |
The host name of the system where
the IBM Records Manager engine is installed. |
|
| BOOTSTRAP_ADDRESS port |
none |
The port number on which the application
server Object Request Broker (ORB) listens for requests. The port
number can be found in the WebSphere Application Server administrative
console as BOOTSTRAP_ ADDRESS. |
|