You migrate an Adaptive Web Service (AWS) model to support Service Group configuration in the following two scenarios:
· An existing model that uses Logical Destination.
· A model that you create in the current version using the No Service Group Configuration option.
The AWS model maps to a Service Reference ID that belongs to a Service Group. Apart from Service Group, each model also has an authentication profile, which is currently defaulted to No Authentication. The Service Reference ID is provided as a model setting and can be viewed in the properties view of the respective model. Another model setting related to Service Group is the applicationName, which is the name of the Web Dynpro (WD) project.
WD explorer displays the Service Groups and authentication profiles. In the WD explorer and the project explorer view, the user can edit these entities. For more information, refer Viewing and Creating Service Groups in Web Dynpro Explorer.
Service Group configuration simplifies and reduces the configuration efforts needed for a composite or application. In addition, it also provides a common configuration UI to unify various configuration steps carried out by different toolsets.
More information: Creating Service Groups.
The administrator of the J2EE engine must configure these service groups at the J2EE engine where WD application is deployed to point to a valid provider system.
More information: Configuring Groups of Web Service Clients.
You have created the WD model by importing the necessary AWS model.
More information: Importing Adaptive Web Service Models.
1. In NWDS WD perspective, choose the required model.
2. Right-click and choose Enable Service Group Configuration.
If a Service Group already exists, then you can reuse that Service Group. Apart from Service Group, each model also has an authentication profile, which is currently defaulted to No Authentication. The Service Reference ID is provided as a model setting and can be viewed in the properties view of the respective model. Another model setting related to Service Group is the applicationName, which is the name of the WD project.
WD explorer does not display the Service Groups and authentication profiles. In the project explorer view the user can edit these entities.
3. On the Enable Service Group Configuration dialog box, choose Yes.
If the Execution destination name exists, the Service Group name is created with the same name as the default execution destination name (if the user has entered the default execution destination name).
If no logical destination is selected during the import, the system defaults to a self generated Service Group name.
If you have migrated to Service Group Configuration then
Create a Service Group for the Model. The administrator of the J2EE engine must configure the Service Group at the J2EE engine where WD application is deployed to point to a valid provider system.
More information: Configuring Groups of Web Service Clients.