test

Working With the Master Index Data Manager

Logging in to the Master Index Data Manager

Before you can use the MIDM, you must first log in to the application by entering the correct URL in your web browser and then specifying your login ID and password. Make sure you have a user ID and password for the master index application before logging in. The application server running the master index application must be started before you can log in to the MIDM.

The URL for the MIDM is:


http://host:http_port/app_nameMIDM

where

Note –

The “MIDM” at the end of the URL is case-sensitive and must be entered in all capital letters.

The HTTP port number for the Sun Java System Application Server is listed in the domain.xml file in the http-listener element (8080 by default). The domain.xml file is located in app_server_home\domains\domain_name\config. The port number is also listed on the Client and Server page of the HTTP Monitor of the NetBeans IDE.

ProcedureTo Log in to the MIDM

  1. Launch a web browser.

  2. In the Address field, enter the appropriate URL.

    The login page appears.

    Figure 1 MIDM Login Page

    Figure shows the login page of the MIDM.

  3. In the upper right portion of the page, select the language for the MIDM display.

  4. Enter your user ID and password in the appropriate fields.

  5. Click Login.

    The initial page appears. (By default, the initial page is the Record Details page, but this is configurable.)

    Note –

    After a certain period of inactivity, the MIDM automatically logs off and returns you to the Login page when you try to perform an activity on the MIDM. Simply reenter your user name and password to access the MIDM again. The system administrator can set the inactivity period at the server level in the session-timeout element of default-web.xml (in appserver_home\domains\domain_name\config) or at the application level in web.xml in the master index application .war file (located in the deployment .ear file) or in the deployment folder itself. The application level overrides any values set at the server level. The default inactivity period is 30 minutes.