For one of our clients, we are working on integrating Solution Manager
7.1’s service desk with the 3rd party CA Unicenter Service Desk. The
integration is at a very high level, and the objective is to be able to
create a ticket directly from the SAP satellite systems connected to
solution manager, in the CA USD. We have completed 60% of this
integration without using any middleware, like PI or webmethods.
since Solution Manager has the capability to capture the system data,
Transactions component details, and users authorization data. We want
to send this data in the form of an attachment into the CA USDs ticket.
We have integrated it by consuming the web proxy (WSDL) given to us by
the CA USD team. We are passing all the necessary parameters to a
method in that WSDL called CREATE_REQUEST. We are also able to receive
the ticket # back from their system.
We are stuck right now with the attachments part. We are not able to
send an attachment using that WSDL, it keeps throwing an error as shown
below :-
SoapFaulCodeName: Server.generalException |SoapFaulCodeNamespace:
http://schemas.xmlsoap.org/soap/envelope/ Error - could not perform the
operation, policy limit exceeded
Attached is the technical reference guide given to us that team. In the
page # 983, it talks about the error and it solution. The solution
which it says talks about SOAP implementation to support DIME format. I
am not sure how this would work in our scenario. Can you please help me
with handling attachments when using WSDL?
The error that we are receiving is as shown below
Could not perform the operation, policy limit exceeded
Symptom:
When using the createAttachment() web service method to attach a
document to an existing request or incident, you receive this error,
even when the web services policy setting for attachments is set to -1
(unlimited), which is the out-of-the-box default setting. You may
receive this error when calling the web service method if there are no
attached files in the received SOAP message. You must attach at least
one file to the SOAP message before calling the createAttachment() web
service method.
the solution which is given by CA team is as follows
Solution:
Set your SOAP implementation to support Direct Internet Message
Encapsulation (DIME), and attach the file to be uploaded manually using
DIME support before calling the createAttachment() method.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.