PI 7.11 Adapter Metadata

I have installed a new PI 7.11 system.
According to the PI sap help at http://help.sap.com/saphelp_nwpi711/helpdata/en/12/f9bb2fe604a94cbcb4c50dc510b799/frameset.htm
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 7.10, in namespace http://sap.com/xi/XI/System.
But in our newly installed PI 7.11, under ESR-Software Component u2018SAP Basisu201D, I see SAP Basis 7.11. But I do not find u201CAdapter Metadatau201D under the name space http://sap.com/xi/XI/System
Is it expected? If not, which part could have been missed. What could be done to see the u201CAdapter Metadatau201D (which list all the sub items: BC, CIDX, File, HTTP, IDoc, JDBC, JMS, Mail, Marketplace, RFC, u2026.).
I appreciate any inputs you have.
Thank you very much, and best regards,
Joanna

Abhishek,
You are amazing in response.
The item 8 is:
"XI CONTENT SAP_BASIS 7.11
Maintenance Software Component (Current View)"
This 8th item lists SP01, SP02, SP03, SP04 for XI CONTENT SAP_BASIS 7.11.
Is this item what you've recommended? Or should I down load the
"XI CONTENT SAP_BASIS 7.11
Installation Software Component (Current View)" (which does not have download file on SMP swdc )
Over one week ago, I downloaded the SP04 for XI Content SAP_Basis 7.11 (the file name is XICNTSAPBASIS04_0-10005649.ZIP, size of 5408393 bytes).
I unzipped it, getting the file XI7_11_SAP_BASIS_7.11_04_00.tpz
and then imported it using "Import Design Object" in ESR, and getting the message:
"Import source XI7_11_SAP_BASIS_7.11_04_00_2010-01-15_10-58.tpz imported successfully
Import file moved to server directory importedFiles
4224 object(s) imported"
Also, checked the component system info:
SAP_CNT_SAP_BASIS 7.1100.20081021173332.0000
There is one OSS note 1119255 (not sure it applied to PI 7.11), pointed to by SAP. The note says for PI 7.1:
24/MAR/08....III...XI_CNT_SAP_BASIS and XI_CNT_SAP_ABA stay at start SP
Wirth SP04 import for XI Content SAP_Basis 7.11, I see our version stays at the start SP with 7.110 (instead of expected 7.114).
This problem has been my road blocker for over the last few days. I was not able to get much help from SAP through OSS message.
Thank you very much for all your inputs, and regards,
Joanna

Similar Messages

How to incorporate adapter module while writing the adapter metadata for it

Hi all,
We are developing a adapter and the custom adapter module has been prepared.Now we need to write our own adapter metadata. So I need to know in detail how to incorporate our custom adapter module into our adapter metadata.
Paul

hi
check the below links
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/daa51a96-0b01-0010-738f-a0ecfd06104e
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/7086f109-aaa7-2a10-0cb5-f69bd2affd2b
https://www.sdn.sap.com/irj/sdn/teched2004
note:reward points if solution found helpfull.....
regards
chandrakanth.k

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

SOAP Adapter Metadata Missing

Hello,
The SOAP adapter metadata is missing from the http://sap.com/xi/XI/System namespace. All the others are present. How can we get the adapter ?
Does it come as part of some patch.
Regards,
Durga

Hi, we're reimporting the SAP BASIS software component (XI3_0_SAP_BASIS_6.40_00_00.tpz).
The present our situation is:
SAP_JTECHF 6.40 SP11 (1000.6.40.11.0.20050221011822) SAP AG 20050425182200
sap.com SAP-JEECOR 6.40 SP11 (1000.6.40.11.0.20050221011406) SAP AG 20050425182155
sap.com SAP-JEE 6.40 SP11 (1000.6.40.11.0.20050221011617) SAP AG 20050425182238
sap.com SAP_JTECHS 6.40 SP11 (1000.6.40.11.0.20050221012022) SAP AG 20050425182237
sap.com LM-SERVICE 6.40 SP11 (1000.6.40.11.0.20050221012100) SAP AG 20050425182231
sap.com SAP-XIAFC 3.0 SP11 (1000.3.0.11.2.20050407085022) SAP AG 20050425212631
sap.com SAP_XIAF 3.0 SP11 (1000.3.0.11.1.20050324062550) SAP AG 20050425220610
sap.com SAP_XITOOL 3.0 SP11 (1000.3.0.11.3.20050405055844) SAP AG 20050425222949
But the SOAP Adatper still missing.
Is there a newly version to install ?
Regards
Gianfranco

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.

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

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.
<i>>>Here I am Saying We can have all those If we Use Configuration Wizard</i>
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 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

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

Adapter MetaData problem (PI installation).

Hi All,
I had installed 'PI' and as part of post installation, i imported the CR_Content.zip into the SLD. After doing that when i import the SAP BASIS 7.00 Software component into the repository, to my surprise it is imported but doesn't contain anything. As a result i dont have the adapter metadata and is not able to find any kind of adapters in the creation of communication channels. i have gone through the 'SAP Exchange Infrastructure Release 3.0 SR1' in which it is mentioned that
1. Copy XI3_0_SAP_BASIS_6.40_09_00.tpz from <Components DVD>/XI /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 Design Objects
2. Choose the file /usr/sap/<SAPSID>/SYS/global/xi/repository_server/import XI3_0_SAP_BASIS_6.40_09_00.tpz
5. Import the file.
But this is not listed in the SR2 (which is mine). But in my installation DVDs (for SR2) i dint find any XI Content anywhere.
I had also checked out the document Readiness Check Version 3.0. My installation passed all the check points. i had also checked out the notes 669669, 959860, 954820. but none of them are helpful for me.Can anyone help me out in this case"
Any help wud b highly appreciated.
Thnx in Advance
Anil Kumar Veepuri

Hi Anil,
you can download the BASIS component here:
https://smpdl.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
put it to your import folder and import like described.
Regards,
Udo

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

Adapter Metadata not present in SAP BASIS 7.00..

Hi Gurus,
   We hav installed PI 7.0 training server..we call it XIT...In SLD, SAP BASIS 7.00 is there in the s/w components.....but when i import it from SLD to IR its showing no objects presnet in it....specially i need http://sap.com/xi/XI/System where adapter metadata resides.....due to dis prb, i cant create comm channel in ID.....wht went wrong in post installation steps???....i hav seen available support packages does not exit SWCV details....is tht causing the prob???.....we r using SP14 for DEV and QUA...our basis team told me tht SAP BASIS 7.00 has been downloaded from marketplace....should i tell them to download again wid proper support packages and patches??.....waiting for ur valuable inputs...
Regds,
Pinangshuk.

HI Pinangshuk ,
The following thread discuss the similar issue .Please take a look whether it helps you out
       Re: No Objects for SAP BASIS 7.00
      Adapter MetaData problem (PI installation).
       Re: No Adapter Objects Present
Thanks,
Ram.

Linkage between Adapter's code and Adapter metadata

Hi All,
I'm trying to develop an XI adapter and write a corresponding XML adapter metadata. But I still have no idea which part of that metadata refers to the adapter's code. In the sample adapter's metadata, I haven't seen any statement referring to the SDA file or classes of the adapter. Do you have any idea about the relationship between the adapters and metadata?
Thanks + Best Regards
Jerome

hi Jerome,
do adapter developement check the description of this book:
http://www.sap-hefte.de/1478
it should answer all of your questions at once
Regards,
michal

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.

PI 7.11 Adapter Metadata

Similar Messages

Maybe you are looking for