Adapter metadata in Integration repository

What is the use of maintaining the adapter metadata in Integration repository...jena

Hi,
With adapter metadata you can define configuration data needed for a certain type of adapter at design time. Adapter metadata define the part of a communication channel that is specific to the adapter type.
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/12/f9bb2fe604a94cbcb4c50dc510b799/frameset.htm
Thanks
Swarup

Similar Messages

Integration Directory | Choose Adapter Metadata - No objects found!

Hi friends.
I'm new in XI and I wanted to test some simple scenarios. At the beginning I had a problem with the SLD. We made some post-installation steps and everything was allright. Thus my problem is now: In the Integration Directory I try to create a communication channel - I choose Scenario->Service Without Party -> Business System -> <myBusinessSystem> -> Communication Channel and do a right click on it. I choose NEW and create a new communication channel. But when I use display input help for Adapter Type, it is loading for a while but the list of Adapter engines is empty and there is written - No objects found!. I didn't install XI on our machines and I don't know which installation / post installation steps were done. Adapter Engine in integration server is installed for sure. I looked for some threads on the forum, but I didn't find nothing more specific for my problem. Probably I need to set up something somewhere to obtain a list of adapters for the communication channel. Any help will be rewarded.
Thanks
Ondrej

Ondrej,
You need to import SAP BASIS Software Component Version into Integration Repository.
You need to download it from service market place.
https://websmp205.sap-ag.de/~form/handler?_APP=00200682500000001943&_EVENT=SEARCH&HIDE=&SEARCH_SPAT=X&SEARCH_BPAT=X&SEARCH_CD=X&SEARCH_P=X&SEARCH_PV=X&SEARCH_C=X&SEARCH_CV=X&SEARCH_TA=&SEARCH_V=&HIDE_EXPERT_SEARCH=X&SEARCH_MAX_RESULT=20
In Search Term Enter "SAP BASIS <version>".
Then put this in the import directory: \usr\sap\<SID>\SYS\global\xi\repository_server\import\
Now in IR, TOOLS ---> Import design objects and import it.
After import you should be able to see the namespace under it.
Regards,
Sarvesh

Not able to see "External Definitions" in Integration Repository

Hi Experts,
I am working on PI 7.1.
In the Integration Repository Menu :
SAP Basis --->SAP Basis 7.10 ->http://sap.com/xi/XI/System ->
"Service Interfaces",
"Message Types"
"Fault Message Types",
"Data Types",
"Adapter Metadata"
only are visible.
We need the "External Definitions". Is it not available in the standard SAP PI 7.1 ?
Do we have to import it explicitly?
Kindly advice.
Thanks in advance
~ Suraj

Hey NM,
Thanks a lot for your suggestion. problem got resolved when i did what you said (checking the attributes with developers user id's)
Thanks
Sourav

Basic Dought.. In Integration Repository

Hi All,
Any body Explain me the below topics
Integration Scenario & Integration Process
 - Integration Scenarios,
 - Action,
 - Integration Processes,
Interface object
1. message Interfaces
2. message type
3. fault message types
4. data types
- exchangefaultdata
- exchangeLogData
5. Datatype Enhancements
6. Context Objects
7. External Definitions
Mapping Objects
- Interface Mapping
- Message Mapping
- Mapping Templates
- Imported Archives
Adapter Objects- Adapter Metadata
- Communication Channel Template
This information very use full to me
Thanks & Regards

Hi,
I have taken some time off for you and have given the best possible explanation for the doubts you have.
Integration Scenarios:
An integration scenario completely models the exchange of
messages for a collaborative process and provides an overview of the process flow.
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/ec/21ee117a909f44a8b69794b9ed6221/frameset.htm
Integration Processes
An integration process is an executable, cross-system process for processing messages. In an integration process you define all the process steps that are to be executed and the parameters relevant for controlling the process.
You implement integration processes when you want to define, control, and monitor complex integration processes that extend across enterprise and application boundaries. The design and processing of integration processes is also known as cross-component Business Process Management (cross-component BPM, ccBPM).
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/3c/831620a4f1044dba38b370f77835cc/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/f7/d4653fd1d3b81ae10000000a114084/frameset.htm

Interface object
1. message Interfaces
ou use a message interface to describe a platform-independent or programming-language-independent interface, which you want to use to exchange messages between application components using SAP Exchange Infrastructure.
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/55/c5633c3a892251e10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/06/1522417c22f323e10000000a155106/frameset.htm

2. message type
A message type comprises a data type that describes the structure of a message. At the following points in SAP Exchange Infrastructure you can refer to the message to be exchanged at runtime by using the message type
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/2d/c0633c3a892251e10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/e7/7356405aff1e24e10000000a1550b0/frameset.htm

3. fault message types
Fault message types are designed for application-specific errors that occur on the inbound side and that are reported back to the sender or persisted in monitoring.
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/dd/b7623c6369f454e10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/5d/a45c3cff8ca92be10000000a114084/frameset.htm
4. data types
A data type is a basic unit for defining the structure of the data for a message type and, as a result, for the message to be exchanged.
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/a5/04623c4f69b712e10000000a114084/frameset.htm
exchangefaultdata and exchangeLogData
All fault message types reference the data type ExchangeFaultData for this part and, indirectly, the data type ExchangeLogData. These data types are automatically created in a namespace when you create the first fault message type there.

5. Datatype Enhancements
SAP applications enable customers to enhance application source code without making modifications and thus to meet customer-specific requirements that are not provided for in the standard shipment. The applications can use Business Add-Ins (BAdIs) for this purpose. Furthermore, if customers use applications that exchange messages by using XI, they can define data type enhancements for Integration Repository data types.
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/a8/bfc6373c8fea43bdb3541535bcbd43/frameset.htm
6. Context Objects
Context objects are a simple alternative to XPath expressions for accessing the contents of a message.
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/d6/e44fcf98baa24a9686a7643a33f26f/frameset.htm

7. External Definitions
External definitions enable you to import WSDL, XSD, and DTD documents to the Integration Repository so that you can access the message definitions they contain as external messages.
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/43/ce49ef1019087ae10000000a1553f6/frameset.htm
Mapping Objects

Interface Mapping
Interface mappings register your mapping program for an interface pair in the Integration Repository.
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/4f/ef761a5ecfb1418b79896e10fe4c57/frameset.htm

Message Mapping
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/d9/cea942ad920c31e10000000a1550b0/frameset.htm

Mapping Templates
Just like you can reuse data types in different message types, you can also save parts of message mappings as Mapping Templates and reuse them elsewhere. Once you have saved a mapping template it serves as a copy template that you can then load into other message mappings and modify to fit your requirements.
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/79/2835b7848c458bb42cf8de0bcc1ace/frameset.htm
Adapter Objects
Adapter Metadata
With adapter metadata you can define configuration data needed for a certain type of adapter at design time. Adapter metadata define the part of a communication channel that is specific to the adapter type.
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/12/f9bb2fe604a94cbcb4c50dc510b799/frameset.htm
Communication Channel Template
You can preconfigure a communication channel with a communication channel template. You can use the communication channel template as a template to define a communication channel at configuration time.
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/bd/6af766076e384ebdce621d25161184/frameset.htm
I am sure i have clearly explained your doubts.
Regards,
Abhy
PS: AWARD POINTS FOR HELPFUL ANSWERS.

What is Adapter Metadata in Adapter Objects

Hi All,
Q1) What is Adapter Metadata in Adapter Objects in IR ??
Q2) What is Communication Channel Template ???
Wxplain me the Purposes
Regards
Vamsi

Hi Vamsi,
excuse me for my delayed reply.
We can use Integration Scenario from Integration Repository as a template for generating configuration Objects. It takes you through the configuration process, step-by-step. The objects required for the configuration are created and existing objects are checked to ensure that they can be used before including them in a scenario. The relevant objects are predominantly created automatically. The whole process is logged so that you have a good overview and can analyze and understand the configuration.
So Integration Scenario helps you to generate Configuration objects in ID. The configuration wizard that is already there is different might be both the intensions are same.
>>Here I am Saying We can have all those If we Use Configuration Wizard
yes u are exactly correct
But by importing Integration Scenario from IR you will get Integration Scenario Configurator which will embed all the templates and actions included in IR will be generated.
Hope this time you are clarified.
Regards,
Ramesh P

Adapter Metadata Information Missing

Hi XI Guru's ,
Recently i installed PI 7.0 successfully .
At the time of configuring a scenario in Integration Directory my developer is not getting the Adapter metadata information via the drop down tool (i.e. the tool by which we choose the adapter ).
Did i missed something at the time of configuring the PI server ?
Thanks in advance...

Hi,
This might help you more,
Importing the XI Content for Software Component Version SAP Basis
1. Copy XI3_0_SAP_BASIS_7.00_00_00.tpz (latest file ask your BASIS Consultant) from <installation DVD>/XI_CONTENT to
directory /usr/sap/<SAPSID>/SYS/global/xi/repository_server/import/
2. On your SAP XI host, call transaction SXMB_IFR.
3. Choose Repository (Design).
4. Choose ? Tools ? Import Development Objects
2. Choose the file /usr/sap/<SAPSID>/SYS/global/xi/repository_server/import
XI3_0_SAP_BASIS_7.00_00_00.tpz (latest file ask your BASIS Consultant)
5. Import the file.
Regards,
Ramesh P
Message was edited by:
Ramesh Parashivamurthy

Adapter Metadata

Dear all.....
We are developing a custom adapter to handle EDI 997 acknowledgement file.I would like to know what configurations should be done in Adapter Metadata.....
Helpful answers will be given reward points.........
Regards,
Azahar

Dear Jalaludin,
With adapter metadata you can define configuration data needed for a certain type of adapter at design time. Adapter metadata define the part of a communication channel that is specific to the adapter type.
The functions for creating and editing adapter metadata are intended for parties developing new adapters. They are not intended for general use.
For more information about adapter development, see Adapter and Module Development.
You can export adapter metadata as an XML file and import it into the Integration Directory. In this way you can provide the configuration with new adapter types.
To export adapter metadata, choose Adapter Metadata ® Export XML Description in the object menu bar.
SAP ships adapter metadata for all the adapter types it provides. You can find the adapter metadata shipped by SAP in software component SAP BASIS, software component version SAP BASIS 6.40, in namespace http://sap.com/xi/XI/System.
You can find adapter metadata in the corresponding namespace in the navigation tree of the Integration Builder (Integration Repository) under Adapter Objects ® Adapter Metadata.
For more details see the below link
http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm

Acks and Adapter metadata ?

How many types of acknowledgements are there and how to create it ?
What is adapter metadata ?

Hi chandu devina ,
Acknowledgments enable you to confirm that an asynchronous message has been received. You must explicitly request acknowledgments in the application program and can specify what kind of confirmation you want to receive.
Different types of ackmnts are:
System acknowledgement:Positive system acknowledgment.
The receiver was reached successfully. For server proxies, this means that the implementing class for the server proxy was found and that the method for inbound processing could be called.
SystemErrorAckRequested:Negative system acknowledgment.
SAP Exchange Infrastructure runtime reports that an error has occurred during transfer or processing of the message on its way to the receiver. For example, an error in a mapping program or a missing server proxy in the receiver system could trigger this acknowledgment
ApplicationAckRequested:Positive application acknowledgment
The message was processed by the receiver successfully.
ApplicationErrorAckRequested:Negative application acknowledgment
An error occurred during message processing at the receiver.
IDoc sender adapter requests the following acknowledgements:
SystemErrorAckRequested
ApplicationAckRequested
ApplicationErrorAckRequested
File receiver adapter supports only system acknowledgements and system error acknowledgements if they are requested by the sender.
So you will get:
SystemErrorAck when message has not reached the target system
AckRequestNotSupported for all others acknowledgement types (your case is here)
For IDOC, you could have ALEAUD as an acknowledgment IDOC.
Check this document on handling IDOC acknowledgements. This might give you some pointers.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
have a look at the Alert Framework, which can be configured to send mails to specific persons if an interface processing fails.
http://help.sap.com/saphelp_nw04/helpdata/en/80/942f3ffed33d67e10000000a114084/content.htm
There are two types of JDBC acknowledgements Transport level and application level.
IF the JDBC call is asynchronous you can set up for transport level acknowlegement in the send step in ur BPM.
if the JDBC call is synchronous then JDBC adaptor will generate a response message with a tag update count, which gives you the number of rows that were updated.
refer to the following link, which details about reciever jdbc
http://help.sap.com/saphelp_nw04/helpdata/en/2e/96fd3f2d14e869e10000000a155106/content.htm
just check out these links
http://help.sap.com/saphelp_nw04/helpdata/en/29/345d3b7c32a527e10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/7b/94553b4d53273de10000000a114084/content.htm
The following link has entire configuration of Receiver XI Adapter (including acknowledgements)
http://help.sap.com/saphelp_nw04/helpdata/en/f4/0a1640a991c742e10000000a1550b0/content.htm
ADAPTER METADATA:
With adapter metadata you can define configuration data needed for a certain type of adapter at design time. Adapter metadata define the part of a communication channel that is specific to the adapter type.
The functions for creating and editing adapter metadata are intended for parties developing new adapters. They are not intended for general use.
For more information about adapter development, see Adapter and Module Development.
You can export adapter metadata as an XML file and import it into the Integration Directory. In this way you can provide the configuration with new adapter types.
To export adapter metadata, choose Adapter Metadata ® Export XML Description in the object menu bar.
SAP ships adapter metadata for all the adapter types it provides. You can find the adapter metadata shipped by SAP in software component SAP BASIS, software component version SAP BASIS 6.40, in namespace http://sap.com/xi/XI/System.
You can find adapter metadata in the corresponding namespace in the navigation tree of the Integration Builder (Integration Repository) under Adapter Objects ® Adapter Metadata.
For more details see the below link
http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
Regards,
Vinod.

Does EBS Integration Repository has API capability or Export facility?

Now looking into the Integration repository in V12 from the perspective of application integration. Is is possible to interrogate the repository from an outside program using APIs? Or is the repository only meant to to be a browser within the Oracle Apps environment? It would be very useful to have the API capability so that the discovery, import and mapping activities to the V12 integration objects (interface tables, stored procedures, concurrent program,..) can be performed from an integration program.
If the repository is only a browser and does not expose a queryable API, is there an export facility so that could be exported a whole set of interface metadata and import that into an external integration application?
Edited by: Patty on Nov 9, 2008 5:39 AM
Edited by: Patty on Nov 9, 2008 5:44 AM

Hi Srini,
Thanks for your attention to my question.
As we know, Oracle Integration Repository provides a complete catalog of Oracle E-Business Suite's business service interfaces. One of our applications needs to integrate with Oracle E-Business Suite. That means we need to get all the business service interfaces through IRep. Is there are APIs can be called from integration applications, or IRep metadata can be exported, we can easily implement integration with Oracle E-Business Suite.
Hopefully you can give me some suggestions or information. Thanks.

Duplicate SOAP Adapter metadata

we are using PI 7.11 and would like to know whether it is possible\supported to create a copy of the standard SOAP Adapter metadata in the Integration Builder. We would copy it to a different SWC, namespace and name (e.g. Customer_Basis_SWC, http://customer.com....,CustomerSOAP). The requirement behind this is as follows.
An interface exist between PI and a thrid-party application that causes a large number of timeouts when sending async. SOAP messages to this application. The third-party application can not handle the workload caused by the large number of messages pushed through by SAP PI. The third-party application can not be optimized at this point. We believe the only way around this problem is reducing the number of receiver threads in the SOAP adapter. However by changing the threads on the standard SOAP adapter all other receiver adapters of type SOAP are impacted too. Having a customer\application specific SOAP adapter would probably resolve this issue. We also looked at message prioritization but this wouldn't help in this case either.
If this approach is possible what steps are involved other than copying the metadata to a different SWC, Name and Namespace. We did try this in our sandpit and got an error in the communication channel monitor saying "No adapter registered for this channel", even so the interface we tested with appeared to work using the new adapter. We did not modify the metadata after it was copied into the new SWC. Is there any other configuration step required to get rid of this error message.
Any help would be greatly appreciated.
Dieter

Please check below SAP help on loading metadata.
http://help.sap.com/saphelp_nw73/helpdata/en/65/6f64403899970ae10000000a155106/frameset.htm

Data Services 12.2.3.0 BODI-1112015 Adapter metadata import failed

Hi Experts,
I am using Data Services 12.2.3.0.
I have an issue in importing functions through 'Adapter' type datastore into Data Services. I can open the datastore and see the list of functions available, but when I try to import them, I get the error BODI-1112015 Adapter metadata import failed.
The setup and the errors are as below.
The adapter datastore is setup as below.
I built a new keystore called clientkeystore.jks in the ..\bin.Then created the .CSR file, and then imported the signed chained (I believe it's chained certificate) certificate of the server hosting the wsdl into the keystore.
Thanks for the post http://scn.sap.com/thread/1589052 . After changing the metadata character set to utf-8, I can see a list of functions when I open this New_Datastore in Data Services. It proves that the setup for the datastore has no problem parsing the wsdl file and give me the list of functions in it.
However, the error appears when I try to import them.
Error is:
Adapter metadata import failed. Error message: (BODI-1112015) Error parsing the <TheFunctionToBeImported> included in the XML sent by the adapter to represet a function <Error importing XML Schema from file <adapter_schema_in.xsd>:<XML parser failed: Error <Schema Representation Constraint: Namespace 'http://result.form.v81.api.keysurvey.com' is referenced without <import> declaration> at line <13>, char <46> in < < xsd:schema xmln:xsd=http://www.w3.org/2001/XMLSchema" xmln:tns="http://result.form.v81.api.keystore.com" xmlns:diws="http://businessobjects.com/diwebservice" targetnamespace="http://www.businessobjects.com/diwebservice"><xsd:import namespace='http://v81.api.keysurvey.com' schemaLocation='C:\Program Files\Business Objects\BusinessObjects Data Services\ext\webservice\FormResultManagemenetgetRespondentsgetRespondents0.xsd'/>
<xsd: import namespace='http://result.form.v81.api.keysurvey.com' schemaLocation='C:\Program Files\Business Objects\BusinessObjects Data Services\ext\webservice\FormResultManagemenetgetRespondentsgetRespondents2.xsd'/> ........
When comparing it with the wsdl file(as below), it is worth nothing that the schemaLocation is changed to a local directory under C:\Program Files\Business Objects\BusinessObjects Data Services\ext\webservice while it was not the case in wsdl. The schemaLocation is on the server.
I am wondering if the redirection from the server specified in the wsdl file to the local directory has caused this error. The error 'namespace is reference without <import>' is apparently wrong as the <import> is just there.
Or there is any other reason behind this.
I appreciate any adivce or question from you!

I have reached the exact same error as this post http://scn.sap.com/thread/3190403
The error is
[Mon Jun 18 23:14:28 2012] [error] ..\..\src\core\deployment\conf_builder.c(876) Specifyingservices and modules directories using axis2.xml but path of the library directory is not present
[Mon Jun 18 23:14:28 2012] [error] ..\..\src\core\deployment\conf_builder.c(261) Processing transport senders failed, unable to continue
[Mon Jun 18 23:14:28 2012] [error] ..\..\src\core\deployment\dep_engine.c(939) Populating Axis2 Configuration failed
[Mon Jun 18 23:14:28 2012] [error] ..\..\src\core\deployment\conf_init.c(195) Loading deployment engine failed for client repository C:\Program Files (x86)\SAP BusinessObjects\Data Services\ext\webservice-c\axis2.xml
As it is identified as an version problem, this issue is not going to be investigated any further.
As an alternative, can try to use Oracle 11g SOAP_API.sql.

Problem importing idoc to XI integration repository

I have deleoped a custom IDOC and released in SAP/R3. Next I have imported it to XI using transaction IDX2 without problems.
However, when I try to import the metadata to the integration repository, I can't find it in the list of available IDOcs. I have tried to refresh the catches, and even restartet the XI server, but i doesn't help.
Any suggestions ?

Hi Henrik,
See if these threads help :
importing IDOC in XI for interface mapping
IDOC in IDX2 is not visible in while importing into XI Design Component.
Settings in XI side to receive IDOC from application server
Check this link to know minimum authorizations required for a user to import RFC/Idocs.
http://help.sap.com/saphelp_nw04/helpdata/en/2b/a48f3c685bc358e10000000a11405a/content.htm

Adapter Metadata problem

Hi guys,
I have transported a scenario from XI 3.0 to PI 7.1 and, now, when i try to activate my comunicatio channels (in 7.1) I get the following error: "Exception: Attempt to read object Adapter Metadata File...from application REPOSITORY on system REPOSITORY failed."
I have imported the SAP BASIS 7.1 component in IR, but i wondered if my comunication channels are looking for the SAP BASIS 6.40 component instead.
Please advice.
thanks

Thomas,
Indeed the communication channels load their metadata from the imported software component version in the Enterprise Services Builder. If your communication channels are configured using metadata from SAP BASIS 6.40, you will need to import this SWCV in the ESR.
You could, however, also consider to re-configure the communication channels with the metadata from SAP BASIS 7.10. In order to do so, re-select the adapter type in the communication channels and enter the required parameters.
Kind regards,
Koen

Integration Repository objects for EDI adapters

Hi,
We are currently evaluating EDI integration options, and I need some information.
Does anybody know where I can find a list of Integration Repository (or any other) objects such as mappings, mapping templates, msg types, etc that are provided with the EDI adapters from Seeburger or iWay ?
If you know where I could get my hands on some technical documentation of the adapters themselves, that would be great too!
Thanks and Regards
Manish

hi,
>>>>Does anybody know where I can find a list of Integration Repository (or any other) objects such as mappings, mapping templates, msg types, etc that are provided with the EDI adapters from Seeburger or iWay ?
you get them if you buy the adapter
>>>If you know where I could get my hands on some technical documentation of the adapters themselves, that would be great too!
I have one presentation about the seeburger
if you want check my e-mail in my business card
and send me an e-mail
I'll send you this presentation back
Regards,
michal

Adapter metadata import failed

I get 'Adapter metadata import failed' error while trying to import a put operation in the Business Objects Data Services designer in the JMSADAPTER type datastore. The xsd file is in place but the error message says that 'File <ADAPTER_MESSAGE_SCHEMA.XSD> is not a valid XML schema. The XSD that I specified in the operation is of a different name, and am not able to figure out where an XSD for this name comes in.
The same job in the same repository happens to work with no errors on a different Job server.The error it gives is 'File <ADAPTER_MESSAGE_SCHEMA.xsd> is not a valid XML Schema specification.'
Edited by: ssharma6 on Apr 9, 2010 11:28 AM

I have DI 11.7.3.2 and the error is almost the same, BODI-1112010 : metadata import failed, the service is define as:
http://clwlkd2:19080/.wowlink-services-router-http/services/IAlertPortTypePort
and the wsdl file is:
http://clwlkd2:19080/.wowlink-services-router-http/services/IAlertPortTypePort/wsdl/v1/alert/services/wowlink/woolworths/com/au/AlertService.wsdl
this service is not using http basic authentication, the security is inside every object.
Looks that DI probably is transparently following the HTTP redirect from
 http://clwlkd2:19080/.wowlink-services-router-http/services/IAlertPortTypePort?wsdl
to:
 http://clwlkd2:19080/.wowlink-services-router-http/services/IAlertPortTypePort/wsdl/v1/alert/services/wowlink/woolworths/com/au/AlertService.wsdl
Then when it attempts to resolve v1.alert.services.wowlink.woolworths.com.au.wsdl , it issues a request for:
 http://clwlkd2:19080/.wowlink-services-router-http/services/ v1.alert.services.wowlink.woolworths.com.au.wsdl
instead issuing a request for:
 http://clwlkd2:19080/.wowlink-services-router-http/services/IAlertPortTypePort/wsdl/v1/alert/services/wowlink/woolworths/com/au/v1.alert.services.wowlink.woolworths.com.au.wsdl
which is where the resource actually is.
Did someone see this redirection issue before?

Adapter metadata in Integration repository

Similar Messages

Maybe you are looking for