!--a11y-->
Setting Up the Name Service 
To avoid naming conflicts with development objects in a runtime environment, SAP introduced a name reservation service within the context of the development infrastructure.

Although the name reservation service is not mandatory within the development infrastructure, we recommend that you use it.
The name reservation service runs on the same technical basis as the SLD. It is therefore possible to run these two features in a single system. But this is not necessary.

Do not activate more than one name service in a single landscape. One landscape should use only one name reservation service.
● You have installed an SLD.
○ The procedure differs depending on whether you use one SLD with both roles specified above or separate SLDs for each of the roles.

If you run the two features of SLD and name reservation service in one system in parallel, the server must have both roles of Landscape Server and Name Server. To achieve this, in the Technical System Browser, select the newly created SLD, assign the additional role Name Server to it, and save your entries.
○ You have released the SLD for CIM clients; if you have not done so yet, proceed as follows:
...
i. Open the Visual Administrator and log on as an administrator.
ii. Choose Server ® Services ® SLD Data Supplier.
iii. Choose the tab page CIM Client Generation Settings.
iv. Mark the checkbox of the following entry: sap.com/com.sap.lcr/lcrcimom.jar.
○ The steps below are usually part of the installation:
■ SAP Master Component Information has been imported.
■ SLD Data Suppliers have been configured.
● For the name server, the Object Server name must be a namespace reserved and declared as SAP NetWeaver Name Server at SAP Service Marketplace.

For testing purposes, the system ID is sufficient as an object server entry.
● In addition to the prerequisites for the SLD server, you have reserved at least one name prefix at SAP Service Marketplace. More information about namespace reservation: SAP Note 710315.

After you have configured the name reservation, enter the chosen server in DTR. More information: DTR Configuration Areas.
...
1. On the SLD start page, choose SLD à Name Reservation.
2. Choose Enable Name Reservation for NWDI to assign the Name Server role to the SLD you are using.
If you do not see this pushbutton, the SLD has not yet been registered. In this case, proceed as follows:
a. Start the data transfer to the SLD:
i. Open the Visual Administrator in the installation directory of your AS Java (on Windows platforms, for example, in \usr\sap\JC<instance number>\j2ee\admin\go.bat) and log on as an administrator.
ii. Choose Cluster ® Server ® Services ® SLD Data Supplier.
iii. Choose the HTTP Settings tab.
iv. Specify the host, port, user, and password, if required.
v. Start the data transfer to the SLD by choosing This triggers data transfer… (the pushbutton with the blue lightning icon). This process is also started by the system from time to time.
vi. If the process is successful, you can close the Visual Administrator.
b. Restart the SLD server.
i. Log on to the System Landscape Directory (SLD) as the SLD administrator under http://<host>:<port>/sld on the installation of your AS Java.
ii. On the SLD Home page, choose Administration.
A entry shows you the status of the server.
iii. If the SLD server is running, choose Stop Server.
iv. If the SLD server has stopped, choose Start Server.
c. On the SLD home page you now see the Enable Name Reservation for NWDI pushbutton. Use this button to assign the Name Server role to the SLD you are using.
You now see the Disable Name Reservation for NWDI pushbutton. You can use this button to disable this SLD role again, for example if you have configured a separate name server.

Alternatively, you can proceed as described below and select both roles for the SLD.
1. Go to the initial page of the SLD.
2. Choose Landscapes.
The Create New Landscape page appears.
3. Select the landscape type NWDI System.
4. Enter a name for the landscape, for example “NWDI”.
5. Choose Create.
The new landscape is displayed.
6. Select the new landscape.
You see the details on the landscape.
7. Choose Add System to Landscape.
8. Select the hosted system type System Landscape Directory.
You see the installed SLD.
9. Click OK.
10. Select the SLD.
The details view appears.
11. Select the roles Landscape Server and/or Name Server.
12. Save your changes.
The name server is now known to the NWDI and can be used there. Only now can you create valid development configurations.
To set up the name server, proceed as described in Preparing the System Landscape Directory (SLD). Perform the following steps:
...
1. Activate the name server. For the name server, the Object Server name must be a namespace reserved and declared as SAP NetWeaver Name Server at SAP Service Marketplace.
2. Import the SAP master component information.
3. Configure the SLD data suppliers.
4. Register the name server in the SLD of your landscape; this declares it as the name server for the development infrastructure. In this case, the role of the server must be Name Server.
The SAP NetWeaver namespace prefixes reserved on SAP Service Marketplace must be entered in the name server so that namespaces for development objects with those prefixes can be created in the name server. The name server supports different types of development object names. For details, read SAP Note 710315.
To register a prefix, proceed as follows:
...
1. On the SLD initial page, choose Development ® Name Reservation ® Define Namespace Prefix.
2. On the Define Namespace Prefix page, specify the name category and the namespace prefix and then choose Create.
You can use a reserved namespace prefix for all object name types in parallel. Register the prefixes for different name categories as follows:
○
By convention: <reserved prefix>
Enter the NetWeaver
namespace prefix reserved on SAP Service Marketplace here (without any
slashes).
○
Design Time Package
Follows the syntax of the programming language. For instance, Java package
names use reversed Internet domain names like com.company.project.*.
○ Development Component: <vendor>/<reserved prefix>*, where the slash (/) is used as a separator of name segments.