To use Workplace as
a web application, you must deploy it as an application in the WebSphere® administrative console. You
can specify the context root for the application URL during the deployment.
About this task
To deploy Application Engine (Workplace):
Procedure
- Log on to the WebSphere administrative
console.
- Navigate to .
- Select the file to deploy.
- (If the administrative console is running locally)
Select Local file system and enter or browse
to the location of the app_engine.war or app_engine.ear file
created by the installation program. For example, AE_install_path/deploy/app_engine.war or AE_install_path/deploy/app_engine.ear.
Do not enter the machine name.
- (If the administrative console is remote) Select Remote
file system and enter the fully qualified path name to
the app_engine.war or app_engine.ear file.
For example, AE_install_path/deploy/app_engine.war or AE_install_path/deploy/app_engine.ear.
Do not enter the machine name.
- If you are deploying a WAR file, enter the context root.
Enter Workplace and click Next to
proceed to deploying a new application.
Tip: The
context root is the name of the application you log on to using the
web interface, such as: http://ApplicationEngineServerName:port#/Context_Root.
- Click Prompt only when additional information
is required, and click Next. Complete
the dialogs for installing a new application, using the following
settings:
For Application name,
enter Workplace, or the
name you chose to call the application.
For WebServer,
specify the server you are planning to use. Verify that your application
name is selected and associated with the correct WebServer.
For Map
virtual hosts for Web modules, for virtual host, choose
the default_host.
(WAR file deployment only) For Context
root, specify Workplace,
or whatever you want to call the application.
- Save your configuration.
- Navigate to .
- Set the polling interval for updated files with a number
appropriate for your environment, for example, 3 seconds.
- Change the Class loader order to Classes
loaded with local class loader first (parent last).
- Click Apply.
- Click .
- In the Modules column, click Workplace.
- Change the Class loader order to Classes
loaded with local class loader first (parent last).
Important: Change this setting only for the specific
web application. Do not change the similar settings for the entire
application server.
- If you are using container-managed authentication, navigate
to .
- Select the All Authenticated role
and click Map Special Subjects.
- Map the All Authenticated role
and to All Authenticated in Applications realm.
- Save all your changes to the master configuration.
- Stop and restart the WebSphere Application
Server instance
where the application is installed.
To troubleshoot
the deployment, check the following log:
WAS_install_path/AppServer/profiles/profile_name/logs/server_name/SystemOut.log
- Start Workplace (or
whatever you named your application) from the administrative console.
In
a high availability environment, by using the application server administration
tool, verify that the Application Engine application
is running. - Open a web browser and type in the URL for the Application Engine application.
- If you are using a load-balancer or proxy server the URL has the
form:
- Application Engine
- http://virtual_name:port_number/Workplace
- If connecting to an individual cluster node the URL would have
the form:
- Application Engine
- http://clustered_server_name:port_number/Workplace/
Sign-in by using the virtual name to properly set the base Application Engine URL. If it is not set correctly
you must change it in Site Preferences.
- Verify that the sign-in page displays, and log in as
a user.
- Fail one of the nodes.
- Verify that you can reload the sign-in page, and log
in as the same user.