When IBM® InfoSphere™ Enterprise Records is
being installed in an environment with WebSphere® Application
Server 5, you must complete several
specific procedures to deploy the web application. The procedures
differ depending on whether you are doing a local or a remote installation,
and whether you are deploying from a WAR or an EAR file.
To deploy the InfoSphere Enterprise
Records web
application:
- In the WebSphere Application
Server administrative
console, expand the Applications container,
and select Install New Application.
In
the Preparing for the application installation window,
you have several options:
- If the WebSphere Application
Server administrative
console is running locally, select Local Path and
enter or browse for the records_manager.war or records_manager.ear file
under the deploy folder. Do not enter the machine
name.
- To deploy from a WAR file, select the following file: RM_install_path/FileNet/RM/deploy/records_manager.war
- To deploy from an EAR file, select the following file: RM_install_path/FileNet/RM/deploy/records_manager.ear
- If the administrative console is running remotely, select
Server path and enter or browse to the fully qualified path to the records_manager.war or records_manager.ear file.
Do not enter the machine name.
- To deploy from a WAR file, select the following file: RM_install_path/FileNet/RM/deploy/records_manager.war
- To deploy from an EAR file, select the following file: RM_install_path/FileNet/RM/deploy/records_manager.ear
- If you are deploying from a WAR file, enter RecordsManager as
the context root, and click Next to deploy
a new application.
Tip: The context
root is the name of the application that you log in to by using the
Web interface, such as http://RecordsManagerServerName:port#/ContextRoot.
- In the Generate Default Bindings window,
leave the default values and click Next.
- (Deploying using WAR file only) In the Application
Security Warning window, click Continue.
- In the Install New Application Step 1 window,
specify the application name.
Enter RecordsManager,
or the name that you chose to call the application, and click Next.
- In the Install New Application Step 2 window,
specify the virtual host that you want to use. Check RecordsManager,
keep the default virtual host (default_host), and click Next.
- In the Install New Application Step 3 window,
configure your application server and click Next.
- In the Install New Application, Step 4 window,
verify your configuration, and click Finish.
After the configuration is saved, click Save to Master
Configuration.
- Configure the Classloader settings:
- In the WebSphere Application
Server administrative
console, expand Applications, click Enterprise Applications,
and then select your application. The default application is RecordsManager.
- In the Configuration tab, set the Classloader Mode to Parent
Last.
- Verify that the WAR Classloader Policy is set to Module.
Do this step only for the specific Web application. There are
similar settings for the entire application server. Do not change
these settings.
- Configure the Web Module Classloader setting:
- In the WebSphere Application
Server administrative
console, expand Applications.
- Click Enterprise Applications,
and then select your application. The default application is RecordsManager.
- Under Related Items, click Web Modules,
then click records_manager.war.
- In the Configuration tab, set the Classloader Mode to Parent
Last. Do this step only for the specific Web
application. There are similar settings for the entire application
server. Do not change these settings.
- Click , and Save changes to the Master Configuration.
Important:
Verify that the changes were
saved before you proceed with the next step.
- Stop and restart the WebSphere Application
Server.
If installed, restart the HTTP server.
- Log on to the WebSphere Application
Server administrative
console.
- Verify that the InfoSphere Enterprise
Records Web
application is running.
- In the WebSphere Application
Server administrative
console, expand Applications and click Enterprise Application.
- If the RecordsManager application has not been started,
select the box to the left of the RecordsManager application, or whatever
you named it, and click Start.