Repository Namespaces in XI 3.0

Hi people!
For the original setup of XI we are looking at how to set up the namespaces within the SWCV.
On the forum people say it is wise to setup a new namespace for each interface. In the demo examples that are delivered in the XI content this approach is not chosen. It looks like they use 'party' as a reason for a new namespace.
In the examples in the book 'SAP Exchange Infrastucture' it looks like they use a different namespace for each interfaceprocess.
What is your experience on this?
What are the advantages and disadvantages of the different approaches?
thanks a lot for your help!

Hi Alexander,
In our project we have chosen for a generic solution in which SWCV's names are based on Business Processes and all contained within one single product.
Namespaces in these SWC's are created based on the "type" of interface they represent i.e. a combination of sender/receiver party and message type. This last identifier in the namespace has been introduced in order to minimize the risks of having ambiguous namespaces.
This approach supports modularity in your SWC and also provides a flexible way to independently deploy interfaces. Last but not least; by using this approach you can clearly manage how you share/reuse objects from the different namespaces within one SWC.
Hope you have now a better picture of how to carry on with your namespaces.
Cheers,
Rob.

Similar Messages

Repository filter (namespace) project structure

Hi:
We are developing a repository namespace filter to enable
manage the visibility and other aspects of news items
created using xmlforms builder iview.
We use EP60SP2P3HF7 with NWDS 2.0.5.
The wizard to create the namespace filter project created
the portal project like...
-Project folder
--src.api(with packages containing filter classes)
--src.core
--dist(containing PORTAL-INF,css,etc..folders)
--src.config
In this folder there is install,local folders;
In these foders configuration XML files are located.
After overriding filter() and other methods, when tried
to deploy, nothing happened.
But after mimicking the example in one of ThiloBrandt's
documentation, it did get deployed, but NWDS par deploy
screen doesn't close. I need to shutdown the studio.
I did even upgrade to NWDS 2.0.8 too, but invain.
Does any body have a good documentation regarding
developing these filters ?
Thank you much inadvance, for the help,
Prasad Nutalapati

Hi,
the most irritating in your posting at least for me was this combination: EP60SP2P3HF7 with NWDS 2.0.5.
I'm really not that deep in the NWDS infrastructure, but I have been teached only to use the NWDS version for the corresponding WAS version - that means at least 6.40, not 6.20 etc.
So why don't you use Eclipse with the provided KM-plugins?! This should more or less work (at least for the repository services the wizard works except for one error it produces, but at least this one is irrelevant for a repository filer).
Hope it helps
Detlev

ABAP development namespace prefix and XI naming

Hi,
while going to establish company wide SAP XI naming conventions the question arised, if there should be any relationship between naming for XI design and configuration objects and the so called "reserved development namespace prefix" known from ABAP programming. Is it, e.g. advisable to use the reserved ABAP namespace prefix as part of XI repository namespaces?
Any experiences?
Thanks and best regards,
Barbara

Hi Barbara,
Setting up XI naming conventions for a company needs a holistic approach looking what is already out there for java, abap, xml etc. so there is no easy answer to any question regarding naming conventions, only ideas. You have to look at how these ideas fit into your existing conventions, so let me give you my idea on that:
if your company has its own reserved ABAP namespace like /COMP/, you should definitely use that in Proxy Generation as prefix. However a usage in XI namespaces depends on what the Abap NS looks like. SAPs suggestion is to use a namespace like http://company.com/xi/... and i think, it is a very good suggestion, so i would definitely use something similar. Normally i would use the URL similar to the companies website e.g. if the website is http://www.company.com, i would just delete the www out of it. Now you might have a company with a very long name and even website URL and namespaces are restricted to 60 characters so you possibly run into length issues and decide to use an abbreviation, in that case i would definitely use an existing abap namespace as abbreviation if the namespace is somehow descriptive.
Regards
Christine

Global namespace

Hi,
can someone tell me what the difference is between what is the reason SAP puts objects in
http://sap.com/xi/<software_component>/Global or http://sap.com/xi/<software_component>/Global2 or http://sap.com/xi/<software_component>
What does Global or Global2 mean in this context ? Can't seem to find a clear description for this.
Thanks.

Hello
I don't think there is any specific significance behind the use of "Global" and "Global2" in these namespaces. These are just unique identifiers and are used to store configuration objects, data types etc.
Repository Namespaces
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/a3/cc132914cf41e4a193c32627a87542/frameset.htm
Regards
Mark

Changing Namespace section of the XML

Hello,
Following section is generated from one of my outbound IDoc:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:cXML xmlns:ns0="http://abc.com/xi/module" paloadID="700997" lang="en" timestamp="2006/03/07">
But the vendor is expecting this section as below:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE cXML SYSTEM "http://xml.cxml.org/schemas/cXML/1.1.009/cXML.dtd">
<cXML payloadID="[email protected]" timestamp="2005-09-07T16:10:45-08:00" xml:lang="en-US">
Is there any way to solve this problem?
Thanks
Message was edited by: Peter Livingstone

Hello Peter,
if i see that correctly, XI currently puts in an XML namespace whereas your partner expects no namespace at all. This can easily be achieved in XI. Just go to your message type, change to edit mode and then delete the value in field XML Namespace. This will delete the targetNamespace tag from the XSD definition so that all messages will be generated without a message namespace. The principial behind this is, that the XML namespace is not necessarily the same as the Integration Repository Namespace of the objects in XI but will be set to the repository namespace by default.
Regards
Christine

PI 7.1 XML Validation in Integration Engine.

Hi Experts,
In PI 7.1 XML vallidation in AAE what would be the proper path drectories structure?
Sri

Hi,
>> In PI 7.1 XML vallidation in AAE what would be the proper path drectories structure?
Create appropriate directories structure where you have to save our structure (xsd).
\usr\sap\<system id>\SYS\global\xi\runtime_server\A\B\C\D\E\F
A - validation
B - schema
C - GUID of the SWCV where service interface reside.
D - Repository Namespace where Service Interface is created.
E - Service Interface Name
F - Repository Namespace where Message Type or External Definition is assigned.
Note: If your ESR namespace contains special character then do replace it with u201C~u201D in folder name.
If namespace is http://sapxi.com/XI/FileToFile then folder name should be httpsapxi..comXI~FileToFile
Abid Mazhar

Java.lang.Exception error during XML validation by Integration Engine

Hi professionals,
We are trying to use XML validation by the Integration Engine.
Step 1:
We created an appropriate directory structure where we had to store the structure (xsd).
\usr\sap\<system id>\SYS\global\xi\runtime_server\A\B\C\D\E\F
A - validation
B - schema
C - GUID of the SWCV where service interface reside.
D - Repository Namespace where Service Interface is created.
E - Service Interface Name
F - Repository Namespace where Message Type or External Definition is
assigned.
Step 2:
We also changed the references in the xsd to exclude all the subdirectory references.
e.g folder1/folder2/abc.xsd is become abc.xsd only
Step 3:
We stored both xsdu2019s (schema xsd and referenced xsd to the directory created in step 1)
Step 4:
We changed the directory and xsdu2019s permissions to 777 (we chose 777 for testing purpose).
Step 5:
We changed the property schema validation of the sender agreement to Validation by Integration Engine.
Step 6:
We checked RFC destination for AI_VALIDATION_JCOSERVER on AS ABAP and AS Java and establish an successful connection test.
RESTULTS
The result of those steps is an error message in the message monitor of PI with the error tekst:
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="XML_VALIDATION_INB">CX_XMS_SYSERR_VALIDATION</SAP:Code>
<SAP:P1>java.lang.Exception</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>not used at the moment.</SAP:AdditionalText>
<SAP:Stack>System error occurred during XML validation</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please assist in how to solve this issueu2026.
Regards, Sjaak.

I would suggest follow Appendix A to know the exact path and since you have one XSD referring other XSD check the steps mentioned in Appendix B .... there seems to be some error in referencing ...Appendix A and B are on page 12 & 13 of this document:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d06dff94-9913-2b10-6f82-9717d9f83df1?quicklink=index&overridelayout=true
Regards,
Abhishek.

Strange Problem in BPM.

In sxi_cache we are finding some BPM's in 99 status.In the list displayed in sxi_cache we cannot see the repository namespace and SWCV in the integration processs link of sxi_cache.When I tried to re-activate from the sxi_ccahe browser I get a strange error saying "Container element does not exist"...Can anyone help?

Michael,
Iam just waiting for a reply from you.
I understand and the fact is that sxi_cache just displays the entries in SWFXICACHE and when I execute sxi_cache in full mode the table entries are filled through some system RFC's and not sure why there are errors in same BPM.
We are in the QA server and donot want to re-activate the BPM in IR since as per the standard process we should not modify the IR objects in QA.
I have trouble shooted the problem to a certain extent.The problem is due to even type linkage of that workflow is not activated in the QA.This entries are missing in the SWE2 and also when I go to SWDD transaction and select on the recieve step..the right pane does not show me a link to the proxy and says binding does not exist?
Can you crack it???

Doubts in File to RFC scenario

Scenario we are working on:
Legacy System -> Flat File -> XI2.0 -> RFC -> SAP R/3 470 ( WAS 620 )
What we have done till now:
1. Created technical system for XI server and the SAP 620 ( target system )
2. Created business system for XI Server and target system
3. Created a software product for legacy system and the corresponding technical system and the business system
4. Defined the business scenario in Repository including Actions, Message Interface, Message Type, Data Type (for source file), Imported RFC signature from target system, message mappings and message interfaces.
5. Configured the file adapter.
6. Configured business scenario in Integration Directory including interface determination and receiver end points
Where we are stuck:
1. Currently I have created the entire set of objects under the new software component I created for source system. I want to know how to decide under which software component should I create the design objects, e.g under the software component for source system, or under the software component for target system or am I supposed to create a new product altogether including all the software components in my scenario.
2. What is the significance/dependency of namespace in the design process?
3. I have configured the inbound file adapter (attached is the configuration file). How do I integrate it with the Integration server? In other words where to specify the link between my business scenario the file adapter. How do they talk to each other?
4. We are not able to configure the RFC adapter. Can we get a configuration file for a working adapter? Are there any pre-requisites for the RFC adapter configuration? Also once configured how will it talk to Integration Server?
5. Is it possible to use proxies on Integration server in our scenario? Our XI system is installed on WAS 620 with J2EE 620 and the target system is also WAS 620.
6. Is it possible to send email notification from XI in case or any errors e.g while accepting the file, while mapping, or while passing to target system

Hi Satinder,
Below are the answers for your questions:
Regards
Prasad
Netweaver RIG-XI
SAP Labs LLC.
Ans1: If you are creating a new sceanrio, you can create a product and a software component in SLD and import the software component into Int.Repository. You can define 1 namespace or mutliple namespaces under this SC.
It all depends on how are desiging your objects in SLD, Int Rep etc. This can be done in various ways.
Ans2:
Namespaces Definition:
Namespaces in the Integration Builder are namespaces in the sense of XML namespaces that are sub-divided further into semantic units within the Integration Builder software component versions. Objects of a namespace can only be shipped as part of the corresponding software component version and not separately.
XML Namespace Definition: An XML namespace is a collection of names, identified by a URI reference , which are used in XML documents as element types and attribute names
RFC2396
IETF (Internet Engineering Task Force) RFC 2396: Uniform Resource Identifiers (URI): Generic Syntax
Use
The following types of namespaces exist in SAP Exchange Infrastructure:
· Repository namespaces are displayed in the Integration Builder (Design) navigation tree. They are all assigned to a software component version but are used differently:
¡ Repository namespaces are used to avoid naming conflicts. For objects of the same object type, it is not possible to have duplicate object names within a repository namespace. In other words, a repository namespace is a quantity in the Integration Repository in which the object names are unique.
¡ Software component versions are used to define shipment units. It is not possible to ship objects in a namespace (business scenario objects, business process objects, interface objects, mapping objects, and adapter objects) on their own. Instead, they are shipped as a part of the relevant software component version.
Although repository namespaces are assigned to the software component version in the navigation tree, the software component version does not affect the uniqueness of the object names.
· XML namespaces are used as identifiers for message instances or customer-specific fields in the instance. You can specify XML namespaces as an attribute of (fault) message types and data type enhancements.
· Namespaces in the System Landscape Directory (SLD), which have nothing to do with repository or XML namespaces (see: Namespace).
· Internal namespaces, which are required in message instances, for example. The internal namespace for fields in the message header is: http://sap.com/exchange/MessageFormat, for example. These namespaces are of no further interest for SAP XI users.
Ans3: Check the Adpater Documentation. In your case, the legacy system will be creating a file in the file system where the file adpater is installed.You have to mention this path in your FA configuration. Once the FA is running, The file is polled automatically. The parameter defined in the config file will send direct the message to XI server. For Ex:
XMB.TargetURL=http://:8000/sap/xi/engine?type=entry
Ans4: Check the documentation for RFC Adapter Config. Once configured it will talk to XI via JCO. send me an email if you have more questions.
Ans5: Yes you can use Proxies as your target system is was620.
Ans6: this is possible in XI-3.0 -SP04 as the SMTP adpater is available. You have to model the message in XI-3.0 when to send an email message.

XML file 2 XML file

Hi all,
I have low experience with XI but I have created a scenario XML file to XML file (reference wiki.sdn.sap.com) where sender e receiver files are located into XI folders . The steps defined are :
product;
software component;
technical system (thirdy-part);
business system;
import sofware component into integration repository;
namespaces;
data type (sender/receiver);
message type;
message interface;
message mapping;
interface mapping;
configuration scenario into integration config.;
assign business system;
communication channel;
file adapter with source e destination directory (folder XI), file name e processing parameters;
receiver and interface determination
sender and receiver agreement.
When put the input file into sender folder I don't have output file and sxmb_moni is empty for XML message.
Thanks in advance.
Miki

Hi Maurizio,
you don't see anything entering inside your sxmb_monitoring: do you mean that the payload is empty or that you don't see any messages in the overview table?
If you don't see any messages, this means that in the message is not send from your adapter engine towards your integration engine.
Check wether:
1) your communication is set up properly and is active
2) your communication channel is functioning correctly via communication channel monitoring in the runtime workbench (goto the integration builder --> runtime workbench --> Component monitoring --> click on display --> click on adapter engine --> click on communication channel monitoring --> search for you communication channel and check for errors.
3) check your sender agreement
If you have an empty payload, check your payload in the first step of your message pipeline and check wether the payload has the expected layout.
Kind regards
Joris

Regarding error in xml validation 7.1

Hi
I am doing file to idoc scenario. In the sender agreement i selected validation by Adapter and uploaded the particular xsd.after executing the scenario in runtime workbench it is showing sucessfully processed but in the MDT audit log I am getting following error.without validation the file is posting in target system.but when I check the validation by adapter it is giving following error.
Received XI System Error. ErrorCode: CX_XMS_SYSERR_VALIDATION ErrorText: not used at the moment. ErrorStack: System error occurred during XML validation
Transmitting the message to endpoint http://orcdapp1.edfapps.edfenergy.net:51100/sap/xi/engine?type=entry using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: CX_XMS_SYSERR_VALIDATION:not used at the moment..
Please give me your inputs.
Regards
venkat.

Hi Venky,
This error due to incorrect path So please check whether you have used the correct path or not?
Create appropriate directories structure where we have to save your structure (xsd).
\usr\sap\<system id>\SYS\global\xi\runtime_server\A\B\C\D\E\F
A - validation
B - schema
C - GUID of the SWCV where service interface reside.
D - Repository Namespace where Service Interface is created.
E - Service Interface Name
F - Repository Namespace where Message Type or External Definition is assigned.
Note: if your ESR namespace contains special character then do replace it with u201C~u201D in folder name.
If namespace is http://abc.com/XI/FileToFile then folder name should be replace with httpabc.comXI~FileToFile
Export schema from the ESR and save it in folder u201CFu201D with name <<RootElementOfMessageType>>.xsd. So in this case it is MT_File_Sender.xsd
Regards,
Sameer
Edited by: sameer Khanna on May 27, 2009 10:14 AM

WebSevice Problem in IDOC2Webservice

Dear Friends,
I'm doing IDOC to Webservices scenario, where in IDOC is generated in CRM server and posted to PI then the fileds of IDOC has to be mapped to webservices.
I have got the webservice that is generated from a .net server, when I'm consuming the webservice, it was not showing all the required fields that are to be mapped with an IDOC fields in mapping.
These fields can be visible in xmlspy.
Have any one worked on this scenario please help me out.
I feel there if problem with some name spaces in the imported wsdl.
Please dont provide any links.
If you want furthur information I will provide.
Thanks in advance
Praveen

check.
Symptom
In the Integration Builder of SAP NetWeaver 2004 and SAP NetWeaver 2004s ,
problems occur during the import of xsd and wsdl files as external
definitions if the target namespace contains more than 60 characters. The
system does not issue any error message, however, the list of the
recognized messages remains empty.
More Terms
Namespace, repository namespace, XML Namespace, Integration Repository,
External Definition
Cause and Prerequisites
In SAP NetWeaver 2004 and SAP NetWeaver 2004s, repository namespaces cannot
contain more than 60 characters. When the system reads xsd and wsdl files
as external definitions, it automatically uses the respective target
namespace as the repository namespace of the external messages extracted
from that namespace. If this target namespace has more than 60 characters,
the system does not extract any message.
Solution
For a wsdl file, you simply need to edit the target namespace manually (
attribute "targetNamespace" of the wsdl:definitions element) and reduce the
number of characters to less than 60. For the structure of the extracted
messages (exception: import assuming rpc style binding, see below), this
target namespace does not have any importance.
For a xsd file, refer to the first case. Import the xsd file, navigate to
the tab with the generated wsdl file, copy this to an editor and shorten
the target namespace. Then, import the edited wsdl file as an external
definition.
There is no length limit for the xml namespace name for definitions of
message mappings. If you want to generate a proxy from the external
message, the xml namespace must not be longer than 250 characters.
In SAP NetWeaver 2004 as of SP16 and AP NetWeaver 2004s as of SP07, you can
extract messages from wsdl files with rpc style binding. In this case, the
system uses the target namespace of the wsdl definition as the xml
namespace for the messages. If the target namespace is too long, first
import the file with the selection for using the rpc style, copy the
generated file into an editor and shorten the target namespace. Then,
re-import the file but use the selection "from all contained message
definitions".

Issue while importing the WSDL file in the External Definitions - PI 7.0

Dear all Experts
After importing the WSDL file in the external External Definitions we are not able to view the " name and namespace " in the messages tab.
Request you to advise on the issue.
We are using the PI 7.0
Regards
Machindra Patade

Dear All
Got the answer"
The problem is in the namespace description LENGTH,
Note the following restrictions for XI or PI installations:
· Maximum length of repository namespaces and XML namespaces: 60 Characters. Due to this restriction, the import of XSD files and WSDL files prepares difficulties as an external definition; you can solve these difficulties using Note 901988.
· Maximum length of object names in the Integration Repository and Integration Directory: 120 characters
As of SAP NetWeaver Process Integration 7.10 Support Package 7, the enhancement of the maximum length of namespaces to 255 is supported in the configuration and runtime.
Please check the below SAP 2 notes in regards to above mail.
SAP Note 901988 - Integration Builder: Namespace of external definitions
SAP Note 870809 - Integration Builder: Length of namespaces and object names

Repository Filter (Namespace) INamespaceFilter no livecycle

Hallo,
I generated a Namespace Filter and connect it to a repository. But the filter has no effect.
From the exteded AbstractNamespaceFilterManager I get logger infos only from constructor and startUpImpl(). But i get no infos from getFilterForRead(). But i used the repository.
Please help me,
Norbert

Hi Norbert,
first, did you follow one / both tutorials:
- How to create namespace filter for KM
- https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/70ee3a57-0701-0010-3e9a-ddae7e4e0521
Second, I have deployed your PAR. After some deactivating / removing / creating / activating of the instance of the filter, I could start to debug the filter method itself. Anyhow, it throws some StackOverflowException, but that should be examined by yours (don't have the time at the moment).
Alternatively, try to restart the server where you have deployed your stuff. But anyhow, try to debug the code instead of (only) printing log messages.
Oh. I have to add that I have tested this on NW04 and you are working on SP2, I expect. Anyhow, the example from Thilo is developed on SP2, so maybe you should start with that PAR example.
Hope it helps
Detlev

Audit WMI Repository. Record all namespace removal events.

Hello,
Every night some of the namespaces in my WMI repository are removed by an unknown source. I have enabled WMI auditing and "Other object access events" in order to populate the security log with WMI access events. The unfortunate thing is that a
full search of the events does not even mention the namespace that was deleted after an overnight log. Yet in the morning, the namespace is gone. I am looking for a way to audit the repository for all deleted namespaces and who the source was (PID, Login Name,
etc)

Hi,
Have you configured System Access Control Lists (SACL) on the security tab of the WMI Control?
If yes, please ensure that auditing has been enabled correctly. You may use Auditpol /get command to display auditing settings of the local machine.
Auditpol get
https://technet.microsoft.com/en-us/library/cc772576.aspx
Please note that namespace auditing is not available on Windows Server 2003.
More information for you:
Access to WMI Namespaces
https://technet.microsoft.com/en-us/scriptcenter/aa822575
Best Regards,
Amy
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]

Repository Namespaces in XI 3.0

Similar Messages

Maybe you are looking for