How to look like a hero with Netweaver CE ESR & SR

[former_member199115]

I often receive questions from both customers and consultants experiencing similar issues with the Enterprise Services Repository (ESR) and Services Registry (SR). This blog aims to point out some of the common issues encountered with the ESR/SR and provide you with a list of solutions.   After working with the ESR/SR for some time now I have come to the conclusion that there are only a handful of problems that people encounter. My goal is that this blog will equip you with the answers and help you get the ESR/SR up and running in your environment and make you look like a hero.

Please note that this blog should not be used as a replacement for the CE master installation and upgrade guides.

First let me prefix the discussion by saying that this blog only deals with the ESR and SR as it relates to the Netweaver Composition Environment CE SP3 and SP4.  Keep in mind that for SP3 and SP4 the ESR comes bundled as a separate installation – it is not part of the basic CE installation. Starting with SP5 the ESR will be fully integrated and part of the CE installation.

As a introduction let me set the stage by briefly mentioning the differences between the ESR and the SR. The ESR contains the metadata of your enterprise services, the meta data consists of artifacts like process component models, service interfaces, operations, message types and data types. All of the meta data is manipulated through a modeling tool that is referred to as the Enterprise Services Builder (ESB). Keep in mind that the ESR contains only unimplemented services that do not have endpoints. This is where the Services Registry comes into play. Once the enterprise service is implemented in either a ABAP or Java system it can then be published to the SR with an endpoint and made publicly available to anyone that would like to consume that enterprise service. 

With that said let's jump into the details with a quick re-cap of the 3 vital configuration steps that need to be completed after the ESR is installed. They are the SLD, SR and ESR configuration wizards found within the Netweaver Administrator (NWA > Configuration Management > Scenarios > Configuration Wizard). The wizards will do the initial setup of the mentioned components so that you do not have to do it manually. Without first running these wizards you will be really disappointed with the product as you will have a hard time getting everything to work properly.

The following is a list of common issues that you may encounter.

1) ESR Configuration Wizard fails (Issue valid for SP3 & SP4)

The configuration wizard fails near the end when trying to import XI content with the following error message.  "Connection to system Integration Builder using application CMS-Transport lost”

• When asked how to proceed select “Skip step” and wait for the wizard to finish.
• Refer to note 1004684 to increase the timeout and maxlocks settings then proceed to execute the Wizard again.  If you continue to encounter the same error or if you are not able to execute the Wizard again proceed with the following manual steps. 
• Simply import the XI objects manually through the Enterprise Services Builder (ESB).
• Once logged into the ESB (http://servername:port/rep > Enterprise Services Builder), from the tools menu select > Import Design Objects > Client
• Then point to this directory where the file is located \usr\sap\CE1\SYS\global\xi\content\XI7_1_SAP_BASIS.tpz
• Proceed to Import the file. Be patient as this may take some time. 

XI content is not delivered in the standard SAP patches format but rather in an archive (.tpz) like all other XI content. Here is location where to download XI content for the ESR: Service Market place > Software Download > Download > Support Packages and Patches > Enter by Application Group > Netweaver > SAP Netweaver > SAP Netweaver CE 7.1 > ESR FOR SAP NETWEAVER CE 7.1 > XI CONTENT SAP_BASIS 7.10

2) ESR Configuration Wizard fails (Issue valid for SP4)

The configuration wizard fails near the end with the following error message: com.sap.xi.ctc.app not found. 

• When asked how to proceed select “Skip step” and wait for the wizard to finish.
• Refer to note 1144861.
• Although the Configuration Wizard cannot trigger the import of the XI content, you can still import the XI content manually.
• Proceed to import the XI content as discussed in issue 1, however please make sure to import the SP4 Basis content objects.
• Download the SP4 (XI CONTENT SAP_BASIS) from Service Market Place, unzip the file and import the .tpz file into the ESB as described in issue 1 & 7

3) Enterprise Services do not get published to the Services Registry (Issue valid for SP3 and SP4)

After creating a public restriction within (NWA > SOA Management > Business Administration > Public Restrictions)  the services do not appear within the Services Registry. 

• Check the ServiceRegistrySi port setting, the port is automatically set to 50100. Change the setting to reflect your java node port. Also select basic authentication and supply a valid username and password. NWA > SOA Management > Business Administration > Web Service Administration > Select Proxy Definition Name > Click Go. Select ServiceRegistrySi > Click on the Configuration Tab > Click on the Logical Ports Tab > Select ServicesRegistrySiPort > Click Edit to change the WS Endpoint URL field.
• Verify that the enterprise service is started. NWA > Configuration Management > Infrastructure > Application Modules > Start & Stop Java EE Applications
• If you cannot find the service verify that the enterprise service is deployed within the Web Services Navigator. (http://servername:port/wsnavigator)
• If the enterprise service is not deployed proceed to deploy it again.

Please note the 5 minute window before services will appear in the Services Registry. 

4) Enterprise Services Builder startup fails (Issue valid for SP3 and SP4)

You cannot start or load the ESB Java Web Start client application; after you click on the link you get one of the following error: “Unable to launch ESR”, or “Checking for updates”, or, “An error occurred while launching/running the application“, or “JAR Resources in JNLP File are not signed by same Certificate”

Quick fix temporary Solution

• Remove any ESB client applications from within Web Start.
• For Windows open Java Web Start. You can use this short cut: Start > Run (and type) javaws (or javaws -viewer for JRE 1.6x+)
• Remove all/any ESR Web Start Applications

Permanent Solution

• Open the default ESR start page located at http://servername:port/rep
• Click on the Administration link in the right top corner and logon
• Select Java Web Start Administration
• Click on the second option "Restore Archives and Generate Signature”
• Then click on the JNLP File Url Link (Actually make sure you click the Execute link)
• Wait 10-20 minutes for the JAR files to re-generate 

5) Enterprise Services Builder displays an error message – BASIS Missing (Issue valid for SP3 and SP4)

Just before the ESB loads you may see an warning: “system does not contain software component version SAP Basis 710 (SAP_BASIS_710_Missing)”.

• Perform manual XI import as discussed in issue 1 for SP3/4.
• Perform manual XI import as discussed in issue 8 for SP4.

6) ESR Modeler does not add any operations to the Service Interface (Issue valid for SP3)

You model your business process and drag operation elements into the modeler. Unfortunately when you view your service interface the operations are not there.  You may also encounter an error message when trying to double click on each assignment within the model.

This is a known issue with SP3 – unfortunately you cannot create operations from within the modeler. This issue is solved in SP4

• The work around is to manually re-create the operations within the Service Interface.
• Or if you are on SP4 simply download this file (SAPBASIS Content for SP4) from service marketplace.
• Then unzip the file and import the .tpz file into the ESB as described in issue 1. 

7) SP4 XI Basis objects are missing (Issue valid for SP4)

After performing the SP4 Upgrade the XI Basis Objects still shows SP3 in the ESB

• Download the SP4 Basis content (XI CONTENT SAP_BASIS) from service marketplace
• Unzip the file and import the .tpz file into the ESB as described in issue 1 

😎 Cannot create ESR models as model types are missing (Issue valid for SP3 and SP4)

Within the ESB when trying to create a model the model types drop down list is empty, for example the SAP Procomp model is not present.

• Import the XI Basis objects as described in issue 1, depending on your SP level please import the correct XI CONTENT SAP_BASIS file.

9) Enterprise Services Builder fails to connect to SLD (Issue valid for SP3 and SP4)

When browsing the SLD from within the ESB you get an authorization exception error

• Check user permissions for user ESRSLD, the user needs to have 2 roles assigned: SAP_XI_IR_SERV_USER & SAP_SLD_CONFIGURATOR

10) Fail to see local development objects from outside of ESR (Issue valid for SP3 and SP4)

You created a local component that contains your model and service interfaces using the ESB. When trying to query the ESR from either the ABAP workbench or Netweaver Developer Studio you do not see your Service Interfaces.

Local development objects are not visible to the outside world. Rather add your model to a software component that resides within the SLD. 

• Create a software component in the SLD.
• Then within the ESB > from the Object menu select > New > Work areas > Software Component > Import from SLD > Display > Select your Software Component.

Please remember that you might have to clear the SLD cache from within the ESB if you do not see your software component.    

11) ESR and SLD configuration templates options are missing in the Netweaver Administrator (Issue valid for SP4)

You do not see the options to execute either the SLD or ESR configuration wizards.

• Refer to this SAP note: 1119841 
• Also verify that the Usage Type for the ESR is available on your system by going to this URL: http://server:port/utl/UsageTypesInfo. There should be a table entry for the ESR.
• If not then proceed to install the ESR (obtained by downloading from Service Market place > Software Download > Download > Support Packages and Patches > Enter by Application Group > Netweaver > SAP Netweaver > SAP Netweaver CE 7.1 > ESR FOR SAP NETWEAVER CE 7.1 > ESR 7.10)
• Once that is done verify that you have the latest LMCFG SCA file deployed, if not proceed to download and deploy the latest LMCFG SCA file from Service Market place as described in the note 1119841. Once this file is deployed the configuration options for the SLD and ESR can be seen within the Configuration Wizard.

12) Enterprise Services Builder startup fails (Issue valid for SP4) 

You get the following error message when trying to load the ESB: Unable to read configuration data (ExchangeProfile/aii.properties)

• Download latest SP4 patches from Service Marketplace. Specifically make sure that you have the latest ESP_FRAMEWORK and ES UDDI SCA files. (Service Market place > Software Download > Download > Support Packages and Patches > Enter by Application Group > Netweaver > SAP Netweaver > SAP Netweaver CE 7.1 > Entry by Component > (Composite Applications & Java Application Server)
• If this is a development server, make sure the CE_Complete_Stack_development_full template is active.  NWA > Configuration Management > Infrastructure > Java System Properties
• You can change the template within the Config tool. File > Change System Template.

13) Importing XI Objects manually into the ESR fails (Issue valid for SP3 & SP4) 

When trying to load XI Objects manually into the ESR using the ESB you see this error: Too many locks

• Refer to note 1004684 to increase the maximum locks database settings.