Showing posts with label An in Depth Look at enterprise SOA. Show all posts
Showing posts with label An in Depth Look at enterprise SOA. Show all posts

Tuesday, September 22, 2009

SOA Manager

You can use the SOA Manager to administer and configure service providers and consumer proxies for a local system.

This graphic is explained in the accompanying text.

Communication Between a Consumer Proxy and a Provider Proxy

Communication between the service consumer and the service is established between the consumer proxy’s logical port the provider proxy’s endpoint. To access a particular service endpoint, a service consumer with a particular runtime configuration sends a call using a logical port.

The logical port of the service consumer contains a reference to the unique address (URL) of the service’s endpoint on the provider system. The logical port also contains the authorization needed to call the service methods.

Note

A logical port can send a call to only one service endpoint. However, a service endpoint can be called through more than one logical port.

End of the note.

Prerequisites

  • The service and proxy definitions that you want to configure are available as development objects in the back-end system.

  • You have Administrator authorization.

    For more information, see: Authorizations

Procedure

To set up the SOA Manager for local access, you do not need to perform any special steps.

To start the SOA Manager, use the transaction code SOAMANAGER:

Note

To work with the central SAP NetWeaver Administrator from within the SOA Manager, you first need to assign a host and a port.

  1. Go to the Technical Configuration tab.

  2. Choose System Global Settings.

    An overview if configuration information is displayed.

  3. Go to the Central WS Administration Access tab.

  4. Choose Edit / Display.

  5. Specify the host of the central NetWeaver Administrator and the HTTP port number used by the NetWeaver Administrator.

  6. Save.

Thursday, December 20, 2007

Consuming Services with ABAP

Continuing in the second week of the In-Depth Look at Enterprise SOA blog series, we will focus today on the ABAP capabilities to discover and create an application from ESR and Registry.

This video starts off with the process to create a Service Consumer object (former called a client proxy) in NetWeaver 7.1. We will then perform the same process in NetWeaver 7.0 so that you can study the differences and improvements that have been made. The main area of differences is in the new tool - SOAMANAGER - you use in NetWeaver 7.1 to create the Logical Port. We will also discuss some of the new capabilities of ABAP 7.1 to work with Asynchronous services and Reliable Messaging. The video will close out with some sample applications that use this Service Consumer object to call the service from within different types of ABAP programs. Special focus will be paid to using Web Dynpro ABAP and its Service Call Wizard.

Consuming Services with ABAP

Service Testing and Registry

In this section we'll show you how you can test our server proxy from within the ABAP workbench as well as testing with the Web Services Navigator. We’ll cover some new 7.10 features of Web Service Navigator tool that my colleague, Vladimir Dinev, had shared with me. We’ll then move on to the Services Registry to show you how to add your own classification to the existing ManageVender service.

TESTING: SEE VOICE RECORDED DEMO

SERVICES REGISTRY: SEE VOICE RECORDED DEMO

Service Implementation in Java

You can generate both client and server proxies in Java for Web Services. Client proxies are for consuming services and server proxies are for provisioning services. In this narrated recording, we will provision a server proxy to provide the business logic entirely in Java on the SAP NetWeaver Composition Environment for the ManageVender service interface (WSDL) that was modeled previously in this blog series. We will add the business logic for two web service operations CreateVendor and SearchVendor.

In the process of provisioning the service, we will use a number of features of Java EE 5, such as EJB 3.0 Session Beans, Java Persistence API (JPA), and the Java Persistence Query Language (JPQL). We will then test our service with the WS Navigator and verify the results in the database with the Open SQL Data Browser.

SEE VOICE RECORDED DEMO