Option

Checks

IDES Existence on Client Check

·        Whether the IDES database exists on the mobile client.

The IDES database must not exist on the network. If it exists on the network, a bulk insert into the database fails. In such a case, the database switches to a single insert mode, which has a severe impact on performance.

·        Whether Microsoft SQL Server and Data Source Name (DSN) use the same type of authentication to connect to the IDES database.

If the authentication type is different, you cannot connect to the IDES database.

Replication Enabled Check

Whether replication is enabled on the IDES database.

Replication must be enabled on the IDES database.

Option

Checks

Primary Key Check

Whether a primary key constraint has been defined for each table in the IDES database.

Each table in the IDES database must have a primary key constraint.

Timestamp Check

The data type of the TIMESTAMP field.

The data type of the TIMESTAMP field must be TimeStamp. If the data type is different, you cannot detect errors related to database conflicts.

Unique Indexes Check for Table

The tables in the IDES database for unique indexes.

If unique indexes exist, a bulk insert into the IDES database fails. In such a case, the database switches to a single insert mode, which has a severe impact on performance.

Option

Checks

DSN Check

The configuration of the DSN to the IDES database and the availability of the same in the registry.

When the mobile client application connects to the IDES database, the default DSN, user ID, and password are derived from the registry.

IDES Connection Check

The validity of the login parameters to connect to the IDES database.

SQL Trace Enabled Check

The status of Microsoft SQL Server trace.

Microsoft SQL Server trace must not be enabled unless it is required. If Microsoft SQL Server trace is enabled, it affects the performance of the system as more memory is consumed during tracing.

IDES Admin Rights Check

Whether the user of the IDES database has administrative rights.

To perform operations, such as creating stored procedures and views and assigning a Site ID to the mobile client, the user must have administrative rights on the IDES database.

Registry Admin Rights Check

Whether the windows user has Read and Write access to the registry.

Based on the operation the user performs, Client Console reads or writes certain key values in the registry. Therefore, the user must have Read and Write access to the registry else the selected operation may fail.

MSA Registry completion

The availability and status of the TransferService, MW, Security, TL, RFC, and ConnTrans registry entries.

During the processing of messages, the BDoc layer uses the values in these registry entries. If these entries are not complete, you might not get the desired results.

@@ ServerName Check

Whether the value of the @@ServerName parameter in the IDES database is the name of the Microsoft SQL Server.

During the processing of messages, the BDoc layer uses the server name specified in the @@ServerName parameter. If this server name is different from the name of the Microsoft SQL Server, it results in the failure of operations such as SELECT, INSERT, UPDATE, and DELETE.

Upgrade.sql file Check

Whether the Upgrade.sql file exists in the application path. This file contains all the stored procedures that are required for creating tables in the IDES database and processing messages in the inbound and outbound queues of the mobile client.

This file must exist in the application path.

Conntrans startup file rights

Whether:

·        The <Application root>\ConnTrans and <Application Root>\ConnTrans\Startup directories exist

The <Application Root> refers to the mobile directory.

·        The ConnTrans_Startup.xml has read and write access to ensure logging of runtime information associated with the execution of ConnTrans.

SiteID Consistency

The following details associated with assigning a Site ID to the mobile client:

·        The Site ID has been assigned to the mobile client.

·        The value in the SITE_ID registry entry and IDES database is same.

·        The value in the SITE_ID registry entry and Queue Tables is same.

·        The DBID value in the IDES database and the CRM server is same.

Option

Checks

CDB Table Availability Check

The availability of all the CDB tables in the IDES database. In addition, it checks the consistency of the structure of tables between the CDB and the IDES database.

If any of the CDB tables are not available in the IDES database, metadata generation fails. In addition, you cannot save data into the IDES database.

TL Stored Procedures Check

The availability of TL_INDEX_SCRIPTER, TL_INDEX_RECREATOR, and SP_MAKESP stored procedures in the IDES database.

These stored procedures are required to generate metadata and process messages in the inbound queue of the mobile client.

Conntrans StoredProc check

Whether all the stored procedures related to ConnTrans exist in the user database. In addition, to check the consistency of these stored procedures, this check executes the stored procedures. These stored procedures are used when ConnTrans starts the import of data into the application tables in the user database.

The errors (if any) related to the execution of stored procedures are displayed in the Log window.

Check Metadata

·        The availability of stored procedures in the CRM server and mobile client.

·        The availability of views in the IDES database.

·        The availability of the TPS.net file in the registry under HKEY_LOCAL_MACHINE\SOFTWARE\SAP\MW\TL\Repository_Cache_Dir.

·        The availability of the BDoc type details in the TPS.net file.

·        The consistency of metadata between the CRM server and mobile client.

Option

Checks

Hard Disk Space Check

The availability of sufficient hard disk space.

RAM Size Check

The availability of sufficient RAM in the system.

Page File Size Check

The availability of sufficient page file size.

Option

Checks

SQL Installation Check

Whether Microsoft SQL Server is installed on the mobile client.

IDES Availability Check

The availability of the IDES database in the mobile client.

DLL Existence In System Path

Whether the LIBRFC32.dll, DRVADODB.dll, and SRFC2COM.dll exist in the windows system path.

If these DLLs exist in a different path, you will encounter problems while processing the messages in the inbound and outbound queues of the mobile client.

ADO Version Check

The version of ActiveX Data Object (ADO) in the mobile client.

The version of ADO in the mobile client must be 2.5 or higher.

Comm.Station Domain Check

Whether the domain of the Communication Station is the same as that of the mobile client.

If the Communication Station is from a different domain, the authentication used to connect to the Communication Station fails.

Check DLLs

The following details for CRM Middleware related DLLs:

·        All the required DLLs are registered in the mobile client.

·        The QMTCLIENT.dll on the mobile client is compatible with the QMTSRV.dll on the Communication Station.

Check Third-party Controls

Whether all the required third party DLLs and controls (OCXs) related to CRM Middleware are available and registered on the mobile client.

If any of the controls are not available on the mobile client, you might not get the desired runtime behavior of the system.