<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:test:company">
<soapenv:Header/>
<soapenv:Body>
<urn:CompanyInfo_Request>
<CompanyID>771575035533</CompanyID >
</urn:CompanyInfo_Request>
</soapenv:Body>
</soapenv:Envelope>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:test:company">
<soapenv:Header/>
<soapenv:Body>
<urn:CompanyInfo_Response>
<status>0</status>
<error_text/>
<DateExcerpt>2017-04-28</DateExcerpt>
<OGRN>317774600137769</OGRN>
<DateOGRN>2017-03-22</DateOGRN>
<INN>771575035533</INN>
<CodeTypeIP>1</CodeTypeIP>
<NameTypeIP>1</NameTypeIP>
<PhysicalPerson>
<DateStart>2017-03-22</DateStart>
<GRN>317774600137769</GRN>
<PhysicalNameRus>
<FirstName>Sergey</FirstName>
<LastName>Alekseev</LastName>
<MiddleName>Aleksandrovich</MiddleName>
</PhysicalNameRus>
</PhysicalPerson>
</urn:CompanyInfo_Response>
</soapenv:Body>
</soapenv:Envelope>
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Body>
<SOAP:Fault>
<faultcode>SOAP:Server</faultcode>
<faultstring>Server Error</faultstring>
<detail>
<s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
<context>XIAdapter</context>
<code>ADAPTER.JAVA_EXCEPTION</code>
<text>com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error when attempting to get processing resources: com.sap.aii.af.lib.util.concurrent.ResourcePoolException: Unable to create new pooled resource: DriverManagerException: Cannot establish connection with the registered driver. com.microsoft.sqlserver.jdbc.SQLServerDriver returns: Login failed for user 'test1'..
: com.microsoft.sqlserver.jdbc.SQLServerException: Login failed for user 'test1'.
at com.sap.aii.adapter.soap.web.SOAPHandler.processSOAPtoXMB(SOAPHandler.java:772)
at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:530)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.__AW_service(HttpServlet.java:847)
at javax.servlet.http.HttpServlet.service(HttpServlet.java)
. . .
</text>
</s:SystemError>
</detail>
</SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
Parameter name | Available values | Default value | Obligatory parameter | Description |
catchException | true/false | false | no | True – when exception/error being occurred, its being caught by module and processed considering parameters listed below. False – module works just as a standard module which has been removed from processing sequence. Being used for switching to standard message processing on the go. |
moduleName | string value | localejbs/CallSapAdapter | no | Name of standard module that has been removed from processing sequence. |
operationSpecific | true/false | false | no | True – in case of multiple operations on sender service interface for every operation distinct operation mapping will be executed in case of exception/error. |
operationMappingName | string value | yes, when operationSpecific = false | Operation mapping name which going to be executed upon exception/error while processing message. Has to be unique across the whole ESR. | |
operationName.* where * - serial number of service interface operation | string value | yes, when operationSpecific = true | Name of service interface operation. | |
operationMappingName.* where * is a serial number of service interface operation, which particular operation mapping will be called for | string value | yes, when operationSpecific = true | Operation mapping name which is going to be executed for particular service interface operation in case of exception/error while processing message. When set up as “null” no operation mapping for particular service interface operation will be executed. Sender-system will receive error message in default adapter format. Has to be unique across the whole ESR. | |
saveOriginalMessage | true/false | false | no | True – original request from sender system (BI version) will be transferred to error handling operation mapping from module’s parameter. Vice versa, when set as “false”, AM version of original request will be transferred to error handling operation mapping from module’s parameter. Keep in mind “false” value requires additional attention to message structures when creating ErrorHandling operation mapping. For example, if exception/error will take place before AM version of original request has been created in pipeline, module will try to execute ErrorHandling operation mapping for BI version of original request. |
saveException | true/false | false | no | True – error description being saved in attachment with opportunity of its following extraction in operation mapping. |
wsUser | string value | yes | Name of SAP PI user account. User has to be able to call web services (SAP_XI_APPL_SERV_USER role) | |
pwd.wsPassword | string value | yes | User account password. | |
saveLogVersion | true/false | false | no | True – after execution of operation mapping which has been set up in parameter message version being saved in Message Editor: Versions, displayed with caption “Fault”. |
Parameter name | Parameter value |
catchException | true |
operationMappingName | om_getCompany_errorHandling |
saveException | true |
saveOriginalMessage | true |
wsUser | pi_user |
pwd.wsPassword | ***** |
public String getAttachmentById(String id, Container container) throws StreamTransformationException {
InputAttachments inputAttach = container.getGlobalContainer().getInputAttachments();
if (inputAttach.areAttachmentsAvailable()) {
Attachment attach = inputAttach.getAttachment(id);
if (attach == null) {
throw new StreamTransformationException("Unable to find attachment with id: " + id);
}
return new String(attach.getContent());
} else {
throw new StreamTransformationException("Attachments not available. Please check that the parameter 'Read attachment' in operation mapping is set to true");
}
}
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:test:company">
<soapenv:Header/>
<soapenv:Body>
<urn:CompanyInfo_Request>
<CompanyID>771575035533</CompanyID >
</urn:CompanyInfo_Request>
</soapenv:Body>
</soapenv:Envelope>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:test:company">
<soapenv:Header/>
<soapenv:Body>
<urn:CompanyInfo_Response>
<status>1</status>
<error_text>Error while get info for Company with id 771575035533: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error when attempting to get processing resources: com.sap.aii.af.lib.util.concurrent.ResourcePoolException: Unable to create new pooled resource: DriverManagerException: Cannot establish connection with the registered driver. com.microsoft.sqlserver.jdbc.SQLServerDriver returns: Login failed for user 'test1'..: com.microsoft.sqlserver.jdbc.SQLServerException: Login failed for user 'test1'</error_text>
</urn:CompanyInfo_Response>
</soapenv:Body>
</soapenv:Envelope>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
11 | |
9 | |
7 | |
6 | |
4 | |
4 | |
3 | |
3 | |
3 | |
3 |