Naming Convention for Creating the Namespace in IR

[Former Member]

Hi,

In our XI box we doesnt have any Name spaces created in the IR and I need to create one...

I wanted to know the way in which we decide the naming convention for the Namespaces ?

Can anyone help me out in knowing the same so that i could start out creating one.

Thanks a lot in Advance.

Regards,

Kittu.

[Former Member]

Please see if SAP's naming standards guide helps you...

https://websmp103.sap-ag.de/~sapdownload/011000358700004455192006E/NameConventions.pdf

Thanks.

[Shabarish_Nair]

First to note would be that you can start the naming with either <b>http,urn</b> or <b>url</b>.

then it can be followed by what ever you decide on.

Usually a client comes up with the naming convention used. In my experience it usually has been.

xxx://<Company>/<ProjectName>/<ObjectID>

xxx can be <b>http,urn</b> or <b>url</b>.

[Former Member]

HI,

Repository namespaces are used to avoid naming conflicts within object types in the Integration Repository. SAP XI assumes in most cases that it can identify a design object uniquely (at least within one system) from its name and repository namespace, as is shown in the following examples:

· Proxy generation regards the name and repository namespace as an identifier. This applies for ABAP and Java.

· The inbound interface is identified by its name and repository namespace in an interface determination in the Integration Directory. If the receiver system were to have two interfaces with the same name and namespace, it would not be possible to identify the interface uniquely.

· The name and repository namespace of the sender interface is part of the message header and is evaluated during routing.

In the Integration Builder, ‘repository namespace’ is shortened to ‘namespace’. In this documentation, they are referred to as repository namespaces to distinguish them from XML namespaces.

You can use the same repository namespace in the different versions of a software component. However, you must use different repository namespaces in different software components. If this is not the case, the Integration Builder displays a relevant warning message.

Imagine you have the software component APO in your system landscape. It has a software component version APO 1.0 and a repository namespace myAPO. At the end of development, all objects are transferred to the new version 2.0 of the software component APO. The same repository namespace myAPO must be used here. Therefore, the namespace myAPO is available in both version 1.0 and version 2.0 of software component APO. It cannot be used in a version of a different software component, for example CRM 3.0.

Integration

General

To create design objects (mappings, interfaces, integration processes, and integration scenarios) in the Integration Builder, you must create at least one repository namespace for an imported software component version (see also: Displaying/Editing Software Component Versions). Each software component version can have multiple namespaces.

You can use http,urn,url as prefix for your namesapce as unique name..

Regards

Chilla..

It is possible to delete, but not rename empty namespaces. If you want to copy the objects in one namespace to another namespace, you must manually copy the relative object references for each object. (Also see: Object References).

Predefined Repository Namespaces

Besides the namespaces you create yourself, there are also predefined namespaces:

urn:sap-com:document:sap:idoc:messages Namespace for imported IDoc interfaces

urn:sap-com:document:sap:rfc:functions Namespace for imported RFC interfaces

See also: Importing IDocs and RFCs.

Referencing Objects from Other Namespaces

Whether objects from one namespace can reference objects from another namespace depends on the type of object and on the software component versions that the namespace is assigned to. For more information, see: Object References.

Transferring Objects to a new Software Component Version

When a new version of a software component becomes available, you usually transfer all namespaces and objects from the old version to the new version by means of a release transfer. For this reason, a repository namespace is usually assigned to multiple software component versions of the same software component.

http://help.sap.com/saphelp_nw04/helpdata/en/4e/83623c9c6b530de10000000a114084/frameset.htm

Regards

Chilla..

[Former Member]

Hi Kittu,

for namespace you can use the below convention:

http://<customer website>/<Functional group relating to scenario>/<Integration Scenario Number>

So for example, below can be a namespace:

http://xyz.com/sd/is0001

where xyz.com is your customer website for whom you are using XI, sd is Sales Distribution and is001 is Integration Scenario Number.

Thanks,

Rajeev Gupta

Message was edited by:

RAJEEV GUPTA

[Former Member]

http://companyname/division/objectname

or

urn:companyname:division:objectname