Deploy SAP PI
Upgrade the SAP PI Adapters to SAP PI UDLP V2.5.0
The following tables outlines the steps that you must complete to upgrade this module to SAP PI UDLP V2.5.0.
Before you begin
About this task
These tasks may be completed by multiple people in your organization. We recommend, however, that the tasks be completed in the order in which they are listed.
Procedure
- Upgrade from SAP UDLP V2.3.0 through SAP UDLP V2.4.0
- Upgrade the APM Connect Base.
- Complete the steps to deploy the SAP adapters for the first time.
- Complete the steps to deploy the SAP PI adapters for the first time.
- To Upgrade from EAM SAP PI V1.0.0 through V1.2.0
- Upgrade the APM Connect Base.
- Complete the steps to deploy the SAP adapters for the first time.
- Complete the steps to deploy the SAP PI adapters for the first time.
Deploy the SAP PI Adapters for the First Time
The following table outlines the steps that you must complete to deploy and configure this module for the first time. These instructions assume that you have completed the steps for deploying the basic GE Digital APM system architecture.
About this task
These tasks may be completed by multiple people in your organization. We recommend, however, that the tasks be completed in the order in which they are listed.
Create an SAP PI EAM System Record
You must configure an EAM System Record to establish a connection between any EAM system and GE Digital APM.
Procedure
Results
- An EAM system record is created for the EAM system that defines a connection with GE Digital APM. The ID for this EAM record should now be used in the Name field of a Site Reference field record.
- Linking an EAM system to an EAM System record enables the APM Connect Adapters to create Notifications against that EAM System.
Import the Design Objects
Procedure
Import the Configuration Object
Procedure
Modify the Baseline Communication Channels
Use this procedure to configure the baseline SAP PI communication channels.
About this task
- If the FILE_MOVE_USE_PI parameter is set to false in the context file, you can skip this procedure, except step 9 if you are using SSL.
- These instructions describe using the SAP PI 7.3 configuration interface. Different versions may have minor differences in interface labels or steps.
The SAP PI adapters have the following baseline communication channels that you will need to modify:
- FileSender_SAP_Equipment
- FileSender_SAP_FLOC
- FileSender_SAP_StaticData
- FileSender_SAP_TC_EQUI
- FileSender_SAP_TC_IFLOT
- FileSender_SAP_WMI
- FileSender_SAP_Workhistory
- FileReceiver_APMConnect_Equipment
- FileReceiver_APMConnect_FLOC
- FileReceiver_APMConnect_StaticData
- FileReceiver_APMConnect_TC_EQUI
- FileReceiver_APMConnect_TC_IFLOT
- FileReceiver_APMConnect_WMI
- FileReceiver_APMConnect_Workhistory
Procedure
Results
Activate the RFCReceiver_SAP Object
Use this procedure to activate the RFCReceiver_SAP Object for SAP PI.
Procedure
Define the Command Name in SAP
If you are using a compression option in the context file, you need to define the command name for the compression type you are using. There are two types of compressions for APM Connect SAPCAR and ZIP. You can only use one type of compression.
About this task
- If you are not using a compression method during the extraction, then you can skip this procedure.
- It is recommended to use SAPCAR as your compression type.
Procedure
Install the SAPCAR File on the APM Connect Server
To use SAPCAR to compress files, you must install the file on the APM Connect Server.
About this task
Procedure
- On the SAP Server, copy the SAPCAR.exe file.
- Access the APM Connect Server.
- In the windows\system32 directory, paste the SAPCAR.exe file, as shown in the following image:
Results
Create SAP PI Directory Structure
You will need to set up a directory structure on your SAP server to facilitate transfers from SAP PI to APM Connect.
About this task
The structure depends on the FILE_MOVE_USE_PI parameter and the COMPRESS_TYPE parameter usage in the context file.
Procedure
If FILE_MOVE_USE_PI is... | ...adn COMPRESS_TYPE is... | ... create the following directory structure |
---|---|---|
false | NONE | <root:>/<New Directory Name> |
false | ZIP or SAPCAR | <root:><New Directory Name>/Compress |
true | NONE | <root:>/<New Directory Name> |
true | ZIP or SAPCAR | <root:>/<New Directory Name>/Compress |