Migrating Indexes 

Prerequisites

You have:

·        Read and write access to the registry.

·        Set the user database login parameters in the registry.

·        A user ID and password for the CRM server you want to connect to.

You must know the details of the CRM server you want to connect to.

You can get the server details in the SAP Logon screen.

Procedure

...

       1.      Invoke ClientIndexMigration.exe.

The Client Indices Migration screen appears.

       2.      Under CRM server Details, enter the following data:

Field name	Description	Req./Opt./Dep.	User action and values	Comment
Destination	Indicates the name of the CRM server	Req.	Enter the name of the CRM server.	You need to enter the name of the CRM server only when you migrate indexes for the first time. The next time if you want to connect to the same CRM server, you can select the name of the CRM server from the drop-down list. In such a case, the Application Server, System Number, Client, and Language fields are automatically populated.
Application Server	Identifies the application server	Req.	Enter the name of the application server.
System Number	Indicates the system number of the CRM server	Opt.	Enter the system number of the CRM server.
Client	Indicates the client of the CRM server	Dep.	Enter the client for the CRM server.
Language	Indicates the language in which you want to connect to the CRM server	Dep.	Enter the language.

       3.      Under CRM server Login Parameters, in the Login and Password fields, enter your username and password to connect to the CRM server.

       4.      In the Transport Request field, enter an open transport request.

       5.      In the Migration Log File Path field, enter the path that specifies the location of the log file.

In addition, you can choose Ellipsis to specify the path.

       6.      Choose OK.

Result

After the migration of indexes is complete, a message appears indicating that index migration was successful. However, if the state of an index is inconsistent, you need to resolve the inconsistency by the using the Mobile Client Index Manager. In addition, a migration log is generated that contains information associated with the migration process. For more information, see The Migration Log.