Accessing the Mid Tier Configuration Tool

You can access the Mid Tier Configuration Tool in any of the following ways:

Open a browser and enter the following URL:
http://hostName:portNumber/contextPath/shared/config/config.jsp
- hostName is the name of the host computer for the .
- portNumber is an optional port number; it is required if the web server is not using the default port (port 80).
- contextPath is the path to the location of the in the Oracle JSP engine (arsys by default).
If the mid tier is installed on the local computer using the default context path, enter the following URL in your browser: http://localHost/arsys/shared/config/config.jsp
For this the URL to work, localhost must be correctly entered in the hosts file.
On a Windows computer where the mid tier is installed on the local computer, select Start > Programs > BMC Software > AR System > Remedy Mid Tier > Configure ARSYSTEM on Localhost.

To log on to the Mid Tier Configuration Tool as a administrator

In the ARServer Name field, enter a valid name.
(Optional) If you have installed by using a port, enter the port number In the Port field.
In the User Name and Password fields, enter credentials for an administrator.
Click Log in.
The Mid Tier Configuration Tool Overview page appears. It displays the current settings for your installation. Use the navigation pane at the left to select configuration tasks.

Troubleshooting an authentication error when logging in to the Mid Tier Configuration Tool

An authentication error occurs and the following message is displayed if you try to login to the when the is down:

You are redirected to the config page.

Perform the following steps:

Click the link given in the message and open the Mid Tier configuration page.
Enter the details of the that is up and running.

Changing password of the Mid Tier Configuration Tool

If you select the Force Password Change On Login check box on the User form, you can change the password for the Mid Tier Configuration Tool by using the Change Password form. For more information, see Enforcing-restrictions-on-passwords.

Using the Mid Tier Configuration Tool with a load balancer

If you are using the Mid Tier Configuration Tool with a load balancer, you must use the web server's real IP address, not a virtual IP address, to open the Mid Tier Configuration Tool. Explicitly configure each mid tier instance directly, not through the load balancer's virtual IP. The Mid Tier Configuration Tool will not function as expected if you use a virtual server to open it.

Each web server must have its own . You must configure each mid tier individually, and you must configure each identically.

Best practice
When you have a load balancer between a and a group, we recommend that you configure the load balancer without using a "sticky bit" (session affinity) to allow sessions from any server to be distributed to any on the fly.

A persistent session allows login content to be maintained. Session migration between JSP engine instances is not supported.