cancel
Showing results for 
Search instead for 
Did you mean: 

When mapp interface to web service, it gets problem (PI 7.1)

Former Member
0 Kudos

Hi,

I'm trying to map Interface (synchronous) to Webservice. (PI 7.1)

I imported .wsdl file in external definition.I defined data types, message types and i used SoapIn and SoapOut to Message types.

Now i'm trying to map Message interface to SoapIn in Request tab and SoapOut in Response Tab.

It does not get SoapIn and SoapOut in list.

I had to write manuely them. When i mapp Message Interface to SoapIn (Request).

When i click Response tab at the right side it writes SoapIn (not SoapOut).

I saved Interface mapping.

When i activate, it get error. It says error below.

How can i solve this problem?

Thanks.

Eroor Message on activate the interface mapping

Check result for Operation Mapping: IM_Ws | http://avea.com/asset_manager:

Target interface Operation: Method1SoapIn | http://avea.com/asset_manager is not activated in the Enterprise Services Repository

Request message Message Type: Method1SoapIn | http://avea.com/asset_manager is not activated

Response message Message Type: Method1SoapIn | http://avea.com/asset_manager is not activated

Mapping program Message Mapping MM_WsIn | http://avea.com/asset_manager does not match request target message İFMMESSAGE Method1SoapIn | http://avea.com/asset_manager. Target message External Message Service1 | http://avea.com/asset_manager | Method1SoapIn | http://tempuri.org/ of the message mapping is different to this.

Mapping program Message Mapping MM_WsOut | http://avea.com/asset_manager does not match response source message İFMMESSAGE Method1SoapIn | http://avea.com/asset_manager. Source message External Message Service1 | http://avea.com/asset_manager | Method1SoapOut | http://tempuri.org/ of the message mapping is different to this.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Cemil,

You would have messed up with message interfaces like doing outbound for an inbound. So please change it and test once again.

Regards,

---Satish

Answers (3)

Answers (3)

Former Member
0 Kudos

I solved.In PI 7.1 it must be defined interface object for Soap.

With external message instead of IFMMESSAGE

Former Member
0 Kudos

Hi,

Pls close this thread and rewards points to all accordingly

Abid!

Former Member
0 Kudos

Hi,

In Design Time:

1) Create Data type, Message type and Outbound Syncronous Service Interface for Sender.

2) Import the WSDL file (which is under porttypes folder) as external definitions. The request and the

response messages are seen in the messages tab.

3) Create Inbound Syncronous Service Interface using the message types in external definition.

4) You need to create two Objets mapping OM_Request and OM_Response

Request Object mapping between request MT and the SOAPIN message from the WSDL.

Similarly, Response Object mapping between the response MT and the SOAPOUT message from

the WSDL

5) Create one Interface mapping for request and response. Click on Read messages.....and then include

the MMs created in 1 and 2 as Req and Response messages accordingly....

Aactivat all the objects. Hope this help you

Abid

former_member200962
Active Contributor
0 Kudos

What you need to do:

1) Create a Req Message Mapping between the req MT (you created) and the SOAPIN message from the WSDL

2) Create aResp Message Mapping between the resp MT (you created) and the SOAPOUT message from the WSDL

3) Create a OM (include the SI containing the req MT and resp MT as Input and Output messages on the source side...this SI will be Sync)....(include the SI containing SOAPIN and SOAPOUT as input and Output messages on the Target side....this SI will be SYNC)

4) Click on Read messages.....and then include the MMs created in 1 and 2 as Req and Response messages accordingly....

Looking at the error log I can say that

1) You have not activated the DT, MT, External Defintion (for WSDL)

2) You have mismatched the messages that need to be included in the MM and correspondingly in OM....

regards,

Abhishek.