Changing the context root of an applicationAdded by IBM on February 2, 2011 | Version 1 (Original)
|The Web address from which a Lotus® Connections application is available contains a default context root value. After installing the application, you can change this value to a different context root to conform to corporate restrictions or policies that limit where server applications can be deployed and how they can be addressed.
The Web address from which a Lotus® Connections application is available contains a default context root value. After installing the application, you can change this value to a different context root to conform to corporate restrictions or policies that limit where server applications can be deployed and how they can be addressed.
Before you begin
This is an optional configuration. If you do decide to change the context roots of the applications, be sure to do so before you map the applications to the IBM® HTTP Server or edit the IBM HTTP Server configuration file for any other reason, such as to redirect HTTP requests to support third-party authentication mechanisms.
About this task
For example, the Blogs application is available from <your_host_server>/blogs by default. You can change that base Web address to <your_host_server>/LotusConnectionsBlogs to differentiate it from another available blogging service or conform to corporate guidelines.
To change the context root of an application, complete the following steps:
Regenerate the plugin-cfg.xml file for the IBM HTTP Server in the WebSphere Application Server Integrated Solutions Console. To do so, complete the following steps:
- Log into the WebSphere® Application Server Integration Solutions Console for the server hosting the Lotus Connections application for which you want to change the context root.
- Expand Applications -> Application Types, and then select WebSphere enterprise applications.
- Click the name of the server hosting the application with the context root that you want to change, and then under Web Module Properties, click Context Root For Web Modules.
- Edit the values in the Context Root column of the table to change the term that identifies the application. The paths must continue to begin with a forward slash (/) and must not contain spaces.
Do not specify a single forward slash (/) as the full context root because it prevents applications from being able to retrieve Atom feeds properly. Using the default application context ("/") is not supported.
- Click OK, and then click OK from the server properties page to save the change.
- Start the wsadmin client from the following directory of the system on which you installed the deployment manager:
You must start the client from this directory or subsequent commands that you try to run will not execute properly. See Starting the wsadmin client
for more details.
- Update the Lotus Connections configuration file to reflect this context root change. Use the wsadmin client to access and check out the Lotus Connections configuration files.
- Enter the following command to access the IBM Lotus Connections configuration file: execfile("connectionsConfig.py")
If you are prompted to specify which server to connect to, type 1.
Note: This information is not used by the wsadmin client when you are making configuration changes.
- Enter the following command to check out the Lotus Connections configuration files:
- <working_directory> is the temporary working directory to which the configuration XML and XSD files are copied and are stored while you make changes to them. Use forward slashes to separate directories in the file path, even if you are using the Microsoft® Windows® operating system.
AIX and Linux only: The directory must grant write permissions or the command does not run successfully.
- <cell_name> is the name of the WebSphere Application Server cell hosting the Lotus Connections application. This argument is case-sensitive, so type it with care. If you do not know the cell name, type the following command while in the wsadmin command processor:print AdminControl.getCell()
- AIX or Linux:LCConfigService.checkOutConfig("/opt/temp","foo01Cell01")
- Microsoft Windows:LCConfigService.checkOutConfig("c:/temp","foo01Cell01")
- Update the value of the href prefix using the following command:
Name of the Web module for the application. Each application has one or more Web modules that are configured in WebSphere Application Server. The options are the following:Table 1. Application Web modules
|Application or Service name||Web modules|
|Home page||homepage, news|
Value you defined for the application's Web UI context root in Step 4.
Note: Do not specify a single forward slash (/) as the full context root because it prevents applications from being able to retrieve Atom feeds properly.
For example, to change the context root of the Profiles application, you would use the following commands:
- Save your changes to the LotusConnections-config.xml file.
- After making changes, you must check the configuration files back in and you must do so during the same wsadmin session in which you checked them out for the changes to take effect. See Applying common configuration property changes for information about how to save and apply your changes.
- Files and Wikis only: Perform the following steps:
- Check out the Files and Wikis configuration files. See the topic Changing configuration property values in the Administering Files and Administering Wikis sections of the product documentation.
- Locate the following property:
<logout href="/files/ibm_security_logout" />
- Change it to this:
<logout href="<new_context_root_value>/ibm_security_logout" />
- Perform either of the following actions to update existing links to uploaded files:
Restart the IBM HTTP Server.
Rebuild the search index by deleting the index and letting the indexing task recreate it when it runs. By default, the indexing task runs every 15 minutes. See Deleting the index for more information.
- Open the WebSphere Application Server Integrated Solutions Console.
- Expand Servers -> Server Types, and then select Web servers.
- Select the check box beside the IBM HTTP Server name. For example: webserver1.
- Click Generate Plug-in to regenerate the plugin-cfg.xml file.
- If necessary. click Propagate Plug-in to copy the plugin-cfg.xml file from the local directory where the Application Server is installed to the remote machine.
Parent topic: Administering applications
Optional post-installation tasks
Starting the wsadmin client
Applying common configuration property changes
Deleting the index
Changing Files configuration property values
Changing Wikis configuration property values