After you install IBM® InfoSphere™ Enterprise Records,
you must deploy the web application on WebSphere® Application
Server. You might need to recreate
the WAR or EAR files before you can deploy the web application.
To deploy the InfoSphere Enterprise
Records web
application:
- From the WebSphere Application
Server administrative
console, expand the Applications container
and select Install New Application.
- Select the file to deploy by completing the following
sub-steps:
- If the WebSphere Application
Server administrative
console is running locally, select Local Path and
enter or browse to the location of the records_manager.war or records_manager.ear file
created by Setup. By default, the files are located under RM_install_path/deploy.
Do not enter the machine name.
- If the WebSphere Application
Server administrative
console is remote, select Server path and enter
the fully qualified path to the records_manager.war or records_manager.ear file.
Do not enter the machine name.
- If you are deploying a WAR file, enter the context root
(for example, RecordsManager,
and click Next tp proceed to deploying a new
application. The context root is the name of the application
you log in to using the web interface, such as: http://RecordsManagerServerName:port#/ContextRoot
- For WebSphere Application
Server 7.0,
at Preparing for the application installation,
select Fast Path.
- At Install New Application, Step 1,
specify the application name and click Next. For example, specify RecordsManager,
or the name you chose to call the application.
- At Install New Application, Step 2, Map
modules to servers, check RecordsManager and
click Next.
- At Install New Application, Step 3, Map
virtual hosts for Web Modules, check the application name
and keep the default virtual host (default_host),
and then click Next.
- At Install New Application, Step 4,
verify your configuration and click Finish.
- Save the configuration.
- Configure the class loader settings, as follows:
- From the Administrative Console,
expand Applications.
- Click Enterprise Applications.
- Click the application name (default RecordsManager).
- From the Configuration tab, click Class
loading and update detection.
- Change Class loader order to Classes
loaded with application class loader first for WebSphere Application
Server 6.1 or Classes
loaded with application class loader first (parent last) for WebSphere Application
Server 7.0.
Important: Do this only for the specific web application. Do
not change the similar settings for the entire application server.
- Change the polling interval to a number appropriate
for your environment.
- Click Apply.
- If InfoSphere Enterprise
Records was
installed with Container Managed Authentication:
- From the WebSphere Application
Server administrative
console, expand Applications, click Enterprise
Applications, and then click your application name.
- From the Configuration tab, click Security
roles to users/group mapping.
- For WebSphere Application
Server 6.1, for
the All Authenticated role row, verify that
only the check box in the All Authenticated? column
is selected. For the Everyone role row, verify
that only the check box in the Everyone? column
is selected.
- For WebSphere Application
Server 7.0, navigate
to . Select the All Authenticated role
and click Map Special Subjects. Map the All
Authenticated role to the All Authenticated
in Applications realm. Select the Everyone role
and click Map Special Subjects. Map the Everyone role
to Everyone.
- Click Apply, click Save,
and then click Save changes to the Master Configuration.
Important: Verify that the changes were saved before
you proceed with the next step.
- Click Next.
- Configure the Web Module class loader setting:
- In the WebSphere Application
Server administrative
console, expand Applications.
- Click Enterprise Applications.
- Click the application name (default RecordsManager).
- Under Modules, click Manage
Modules.
- Select the application name.
- Change Class loader order to Classes
loaded with application class loader first for WebSphere Application
Server 6.1 or Classes
loaded with application class loader first (parent last) for WebSphere Application
Server 7.0.
Restriction: Do this only for the specific web application.
There are similar settings for the entire application server. Do not
change these settings.
- Click Apply, click Save,
and then click Save changes to the Master Configuration.
Important: Verify that the changes were saved before
you proceed with the next step.
- Stop and restart the application server.
- Start the enterprise application, as follows:
- From the WebSphere Application
Server administrative
console, expand Applications.
- Click Enterprise Application.
- Select the box to the left of the application name and
click Start.