Message Monitoring
Channel to retrieve the information related to messages:
CC_R_SOAP_AdapterMessageMonitoring
Url: http://host:port/AdapterMessageMonitoring/basic?wsdl=interface&style=document
Authenticating with the basic communications user:
Communication with the backend
For each SAP system we use will have to generate channels for the transmission/reception of information from the SAP system to SAP PI and vice versa. The channel name will be CC_S_ABAP_PROXY and another CC_R_PROXY linked to its corresponding BS. These channels will be of type SOAP based on the protocol XI of similar way to these.
Channels of Information Issuance:
Note: For SAP PI 7.1 versions, the following parameters must be included in the channel module tab (generateSysAck with value true and IgnoreDuplicate with value of true)
Channels for receiving information from SAP PI:
Channels for the Technical Log and Information to Dashboard
CC_S_SOAP_Log_Tecnico y CC_S_SOAP_Procesar_Lote
These channels will be of type SOAP XI. Without any other extra configuration, they are in charge of channeling the information of both the Technical Log and the different steps that the Techedge b+ SII solution is taking.
CC_R_SOAP_LotesWS
SOAP channel in charge of making the call to the Web Service of the Dashboard, which we will supply with information on both the processing of the batches and the technical log.
CC_R_FILE_Lotes_LogTecnico
If you do not have Dashboard, you can generate a File channel in which the Technical Log is written to a file. To do this you can define the channel as follows:
- Filename Scheme: LogTecnico_%guid%.xml
- Processing tab, change File Construction Mode to Append
- In advanced define the field %guid% from the variable substitution
CC_R_AAPP_Procesar_Lote_Orchestrator
This channel will be of type B_PLUS_AAPP_ESP or in its defect a file with the call to the orchestrator in its modules. It is the most important channel and the one that contains all the logic of the process. Section 2.2.4.5 will be defined in more detail.