Show TOC

Naming ConventionsLocate this document in the navigation structure

Use

To avoid naming conflicts when you ship Java software, you must stick to certain rules when you configure the CMS domains.

Customers

All CMS domains are registered automatically with their domain ID in the System Landscape Directory (SLD). If a customer uses only one SLD server (Single SLD Server) or a group of SLD servers with synchronized data (Distributed SLD Servers), then it is guaranteed that the domain IDs cannot be used more than once.

If multiple SLD servers are used, and their data is not synchronized, then customers must themselves make sure that all the CMS domains are unique within their enterprise. If this rule is not followed, transport problems can arise between different CMS domains with identical IDs.

Note

If the Template Installer is used to configure the SAP NetWeaver Development Infrastructure (NWDI), the domain ID is the same as the system ID (SID).

Partners and Software Vendors

Normally the domain IDs generated by the Template Installer during the configuration of NWDI are enough to guarantee the uniqueness of software components (SCs). However, in the following scenario there is a slight risk of problems arising with regard to the uniqueness of SCs:

Example

A partner or software vendor modifies SAP SCs and ships them to customers. The customer makes new modifications to these SCs and by chance uses the same domain ID as the partner or software vendor. In this case, Software Update Manager (SUM), or Java Support Package Manager (JSPM) in previous releases (see SAP Note 1589311 Information published on SAP site) cannot tell the difference between the partner version and the customer version and any updates would overwrite the customer version (see Maintenance of an NWDI-Driven System Landscape ).

You can avoid this problem in the following ways:

  • The partner or software vendor informs customers that they are not permitted to use a domain with the same ID.

  • The partner or software vendor applies for a four-character namespace prefix from SAP and then uses a domain with a four-character domain ID for development work. This provides a sure means of avoiding naming conflicts. (See Name Reservation in the SLD). The reservation of a four-character domain ID for the NWDI uniquely identifies the software component archives (SCAs) that you ship.

    Note

    You must register four-character domain IDs with SAP.

If you want to use a four-character domain, you have the following options:

  • Use an existing prefix namespace in the format /<four-character Namespace>/ as the domain ID in the JAVA environment too.

  • Reserve a prefix namespace in the format /<four-character Domain ID>/ as described in Note 105132 Information published on SAP site.

    Note

    If the namespace is only for use in the JAVA environment, you do not need to enter an installation number or generate namespace keys.

SAP

All CMS domains from which software is shipped at SAP must have four-character domain IDs. To avoid naming conflicts with partners and software vendors, namespace prefixes are also reserved for the SAP domains.

See:

Name Reservation in SLD