General Reference

Maximo

APM stores the time stamp associated with the data extracted from Maximo in UTC and displays the time stamp based on your configured time zone.

SAP

SAP provides a set of baseline time zone codes, which contain most of the standard time zones across the world. SAP also provides the ability for administrators to define their own custom time zone, as needed. Before you use a customized time zone, you must configure the timezone_control table in APM Connect to include the customized time zone.

SAP defines two types of time zones:

• System: This time zone is based on SAP Application Server Operating System and is derived from the context file. You cannot modify this type of time zone.
• User: This time zone is based on the user who created the SAP record. You can modify and store this type of time zone in the SAP user interface.

APM stores the time stamp associated with the data extracted from SAP in UTC and displays the time stamp based on the time zone configured for the user who created the SAP record.

Multiple Source Systems of the Same Type

This scenario is most useful when you all systems you need to support are the same type. The context file configuration for each source system will look the same for the target APM and APM Connect system for all the source systems. The unique parts of the context file are those that describe the particulars of the source system, for example, the system ID and filters used.

Multiple Source Systems of Different Types

Use this scenario if you need to support multiple disparate systems, for example, an SAP and a Maximo system. In this case, you will need to configure context files for each different type of source system, each pointing to the same target APM and APM Connect system. This does not preclude having multiple systems of a specific type (for example, one SAP, one ServiceMax, and two Maximo).

Considerations

There are some things to consider when connecting multiple source systems to a single APM with APM Connect:

• You must make sure that each source system has a unique system ID.
• The logs will contain the messages from all of the source systems. Each message will identify the source system using the system ID.
• Some source system types have unique requirements that must be performed for each source system. For example, you must run the Static Data job for all SAP systems.
• Each source system in a cloud environment will need an intermediate repository, even though they are communicating with a single tenant.
• Do not schedule running the same adapter job types (for example, functional location extractions) simultaneously from different source systems.

Considerations

• The user defined in the source system that communicates with APM must use the same decimal notation.
• You must have unique system IDs and the correct language parameter value or extraction requirements for each plant.
• You must configure filters to make sure that the data is routed correctly to the specific location.