Skip to Content

A brief background.

NetWeaver Development Infrastucture (NWDI)

SAP NetWeaver provides a platform for your Java-based development called NWDI. NWDI provides a centralized development environment for the entire software lifecycle.

NetWeaver Developer Studio (NWDS)

The NWDS provides access to the NWDI. The NWDS consists of Local Development Environments (IDE) on the PCs of the developers and Services that provide the development team with a consistent development environment.

In this blog i will describe a common problem that can occur when Creating a Development Component in NWDS, in this example, the vendor and names on the dropdownlist cannot be selected as they are grayed out.

Steps to Recreate:

1. Start the NWDS (Netweaver Developer Studio).
2. In “Development Infrastructure Perspective” log on to Netweaver Development Infrastructure (NWDI).
3. Create Development Component (Right click on track > context menu appears > Choose “New”).

4. You may notice that you are not able to edit the Vendor field as it is grayed out and set to “sap.com”.

vendor.PNG

Cause:
Prefixes for development components must consist of at least two components (Vendor/Name Prefix).
If you want to allow all of the prefixes under your vendor, enter “xxx.com/*” see note 710315.

Another cause can be that all of the steps have not been completed.

Check the following steps to ensure that you proceeded correctly;

Step 1. Stop NWDS.

Step 2. Open SLD.

http://<host>:<port>/sld/
> Name Reservation.
> List Namespace Prefixes.
> Select Development Component Name.

NEWnamres1.PNG

Apart from the “sap.com” default namespaces you can see here what namespaces have been defined (newcompany.com/appl, etc).

http://<host>:<port>/sld/
> Name Reservation.
> List Namespace Prefixes.
> Select Design Time Package.

NEWnameres2.PNG

Notice the syntax difference (org.newcompany.appl, etc).

Step 3. Restart SLD from SLD > Administration.

Step 4. Update CMS and Re-save the track

/wp-content/uploads/2011/05/ervin4_262469.png

Step 5. Update the Development Configuration in NWDS (on NWDS releases where this feature is not available ensure that there are no open activities, then delete and reimport the development configuration)

/wp-content/uploads/2011/05/ervin5_262470.png

Step 6. Start NWDS and logon to NWDI.

If you start NWDS but don’t logon, then try to create a new DC, it will look like this;

NEWnamres3.PNG

Step 7. Logon to NWDS with your Developer user and create a new DC.

It should look like this;

NEWnamres4.PNG

Another cause can be the Object Server.

In the following example;
I created a new namespace prefix, but I’ve previously changed the object server in the SLD > Administration > Settings > Server Configuration > Object Server.

Restart SLD from SLD > Administration.

NEWnamres5.PNG

I added a new Prefix newcompany.org/os.
Now go to SLD > CIM Instance / CIM Classes > Classes with Instances > Select Allowed Namespace Prefix (num).

NEWnamres6.PNG

Be aware: Since you have changed the object server, only one of the prefixes will be available in NWDS when you try to create a new DC. See Note 935245.

Reference Notes:
#710315  New prefix namespace for SAP NetWeaver.  
#876701  Name reservation of CMS domains in NWDI.
#935245  Importance of “Object Server” SLD parameter.

If you see the below error;

/wp-content/uploads/2011/05/ervinnwds_336450.jpg

Please apply the following note;

#1816503 NWDS not identifying Vendor/Name Prefix defined in SLD

To report this post you need to login first.

3 Comments

You must be Logged on to comment or reply to a post.

  1. Andy Silvey
    Hi Kenny,

    I have seen this problem at three companies, you solved it for me via an OSS Message the first time I came across it.

    I guess you’ve had so many questions on this it’s time that it’s blogged 🙂

    I’d like to say you have solved many issues at different companies I have been it via OSS in the area of NWDI and J2EE – so thank you very much, keep up the good work and we always know we’re in safe hands when you’re the message processor.

    All the best,

    Petr.

    (0) 

Leave a Reply