Install and Configure Southbound Service
Overview
The installation package includes the setup of the Southbound Service from APM to the EAM system. This topic 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 APM system architecture.
Note: This service can be deployed on the APM Connect Server, APM server, or a dedicated server. The service should have access to the APM Connect Postgres Staging Database.
Install Southbound Service
Before You Begin
Before you run the Southbound Service installer, you must ensure that:
- Your system meets the System Requirements.
- You have access to the Southbound Service installation package.
- You can access the APM server host URL and ActiveMQ from the server where the installation is planned.
- You have access to the Postgres IR database of the APM Connect server.
Procedure
What To Do Next
appsettings.json
and then start the service manually.Configure APMC Southbound Service
About This Task
Procedure
Example
//Please remove stars and fill values as mentioned
{
"Urls": "http://0.0.0.0:5013",
"Logging": {
"LogLevel": {
"Default": "Trace",
"Microsoft.AspNetCore": "Trace"
}
},
"Microsoft.AspNetCore.HttpLogging.HttpLoggingMiddleware": "Information",
"FileWSDL": {
"UrlOverride": "",
"VirtualPath": "",
"WebServiceWSDLMapping": {
"EamFileReceiver": {
"UrlOverride": "EamFileReceiver",
"WsdlFile": "EamFileReceiver.wsdl",
"SchemaFolder": "Schemas",
"WsdlFolder": "Schemas"
}
}
},
"AllowedHosts": "*",
"AppConfiguration": {
"IR_Host": "****POSTGRES SERVER HOST****",
"IR_Port": "5432",
"IR_Database": "**IR_POSTGRES_DB_NAME**",
"IR_Schema": "public",
"IR_UserId": "postgres",
"IR_Password": "**IR_POSTGRES_DB_PASSWORD**",
"Is_Linux": false,
"Linux_Base_Path": "",
"Default_Base_Directory": "C:\\APMConnect",
"Apm_Api_Test_Path": "/meridium/api/internal/connect/connectionstatus/ApmcToApm",
"Use_SSL": false,
"StoreLocation": "",
"StorePassword": "",
"CmmsId": "*******CMMS-ID*******",
"Sap_Connection_Type": "Application",
"Use_API_Key": false,
"API_Key": "",
"DownStream_Request_Timeout_In_Minutes": 2,
"Directory_Path": "****ADL Directory folder[Example:\\\\APMCONNECTVM4.meridium.com\\APMConnect\\ADL]****",
"Web_Api_Path": "http://******APM APPLICATION HOST NAME*******/meridium/api/v1",
"Ingestor_Api_Path": "http://******APM APPLICATION HOST NAME*******/meridium/connect/api/v1",
"DatasourceId": "******APM DATASOURCE*******",
"Id": "bl",
"Password": "",
"Polling_Frequency_In_MilliSeconds": 0,
"Max_File_Size_In_Bytes": 100000000,
"Max_Filename_Length": 100,
"Valid_Extensions": "zip,xlsx",
"Valid_Zip_Extensions": "csv"
"Enable_G2DL_Ingestion": true
},
"QueueOptions": {
"ActiveMqHost": "**APM ACTIVE MQ HOST**",
"ActiveMqPort": 61616,
"FailoverHosts": [],
"Username": "admin",
"Password": "admin",
"UseSsl": false
},
"ASPNETCORE_URLS": "http://+:5013",
"DOTNET_PRINT_TELEMETRY_MESSAGE": false,
"ASPNETCORE_ENVIRONMENT": "Production"
}
Customize Southbound Service
Southbound Service supports additional customization for custom RFC and custom field mapping (from APM to SAP) through template-based configuration.
- Notification Create/Update/Close
- Notification user status update
- Work Order Creation
Custom Templates can be used for:
- Map additional APM fields to APM connect baseline RFC parameters.
- Triger custom RFC for below interfaces/endpoints mentioned in table.
The baseline template is available in <southbound Installation folder>\SouthboundService\Templates\sap and sap-pi.
EAM System | Template | Description | Interface |
---|---|---|---|
SAP | createnotification.xslt | Create SAP notification from APM recommendations. Configure/refer XSLT sheet to validate/configure APM fields to SAP RFC parameters. | Recommendations |
SAP | Createnotification_response.xslt | Create notification response from SAP. Configure/refer XSLT sheet to validate/configure SAP RFC response values to APM response load. | Recommendations |
SAP | Updatenotification.xslt | Update SAP notification from APM recommendations. Configure/refer XSLT sheet to validate/configure APM fields mapping to SAP RFC parameters. | Recommendations |
SAP | Updatenotification_response.xslt | Update notification response from SAP. Configure/refer XSLT sheet to map custom fields from SAP RFC response to APM response. | Recommendations |
SAP | Updatenotification_userstatus.xslt | Update notification user status from APM to SAP. Configure XSLT sheet for additional fields mapping from APM to SAP RFC. | Recommendations |
SAP | Updatenotification_userstatus_response.xslt | Response from SAP for update notification user status RFC call. Configure XSLT sheet to map additional/custom fields from RFC to APM response. | Recommendations |
SAP | Closenotification.xslt | Close the SAP notification APM to SAP. Configure XSLT sheet for calling custom RFC or mapping additional/custom fields in SAP. | Recommendations |
SAP | Closenotification_response.xslt | Response from SAP for close notification RFC call. | Recommendations |
SAP | Createworkorder.xslt | Create SAP work order call for inspection and calibration tasks. Configure XSLT sheet for custom or additional fields mapping to SAP RFC parameters. | Work management interface |
SAP | Createworkorder_response.xslt | Response from SAP for create work order RFC call. Configure for additional or custom fields mapping from SAP response to APM response. | Work management interface |
SAP | Createworkorder_notification.xslt | Create SAP notification for inspection and calibration tasks instead of work order. Configure XSLT sheet for custom RFC or additional fields map from APM to SAP. | Work management interface |
SAP | Createworkorder_notification_response.xslt | SAP response for create notification RFC call for inspection and calibration tasks. Configure for additional or custom fields map from SAP RFC response to APM response. | Work management interface |
SAP | Functions.xslt | Used for APM connect xslt transformation. | APM Connect internal use. |
Name | Parameter Type | Sample Config |
---|---|---|
Single value | Import & Export |
|
Structure | Import & export |
|
Table | Table |
|
Note: The RAW Data Type is not supported.
Example: Map additional APM fields to baseline SAP RFC’s.
Requirement: Map additional below two fields from APM recommendation to SAP notification creation RFC.
- CC_REC_CODIN_GROUP_CHR (Coding Group)
- Navigate to <southbound installation folder>\southbound\SouthboundService\Templates\SAP or SAP-PI).
- Access the createnotification.xslt file in an application that can be used to modify XSLT files (for example, Notepad++).
- Search for SAP input parameter name defined in RFC (“NOTIFHEADER”) and add the following additional XML tag to map values from APM recommendation fields.
Example: Custom RFC call
Requirement: APM connect Southbound Service provide the capability to call custom SAP RFC’s. Call custom SAP RFC (ZMIAPM_CREATE_NOTIF) to create SAP notification.
- Navigate to <southbound installation folder>\southbound\SouthboundService.
- Access the appsettings.json file in an application that can be used to modify JSON files (for example, Notepad++).
- Search for "Generalisable" and set the value as true:
"EnableGenericRfc" : true
- Navigate to <southbound installation folder>\southbound\SouthboundService\Templates\SAP or SAP-PI.
- Access the createnotification.xslt file in an application that can be used to modify XSLT files (for example, Notepad++).
- Search for “<NAME>/MIAPM/CREATE_NOTIF</NAME>” and replace the baseline SAP RFC name with custom RFC name as follows:
<NAME >ZMIAPM_CREATE_NOTIF </NAME>
Note: Ensure that you update all the RFC parameters names and columns correctly if they are different than baseline APM connect RFC. That is, update the import parameters with “Z_NOTIFHEADER” instead of “NOTIFHEADER”. - Save the template.
Uninstall Southbound Service
Procedure
- Open the APMConnect - Uninstaller application.
- Select Remove APM Connect Southbound Service checkbox and select Uninstall.
- Open services.msc and verify that the service is removed from the Windows Service Panel.