Setting Up the SOA Manager 
Before you can work with the SOA Manager in a system landscape, you need to configure communication between two ABAP systems based on Web Service Reliable Message (WS-RM).
Prerequisites
Note
To set up the SOA Manager for local access, you do not need to perform any special steps. As soon as you start SOA Manager, you can begin working on your local system.
Procedure
To set up the SOA Manager to work within a system landscape, you first need to set up at least one connection and a user account.
Each system has to be configured separately.
You set up the SOA Manager as follows:
Prepare the connection
Configure the connection
Create a user account
These steps are described in the sections below.
Preparing the Connection
Perform the steps below once in each system.
Perform the basic technical configuration to enable the WS-RM runtime.
More information: Configuring the Web Service Runtime
NoteThis first step applies to runtime only, and does not require SOA Manager.
End of the note.Set up the connection between the SOA Manager and the Services Registry.
These steps are described here:
More information: Setting Up the Connection to the Services Registry
You can now create additional service classifications. Once maintained, the classifications will be published with the service to the Services Registry and the WSDL document.
To create additional service classifications, go to the Technical Administration tab, then choose Global System Settings.
Here, you specify a services identifier.
Specify a local business system.
If the local system is connected to a System Landscape Directory, you can retrieve the Business ID from there. You can also enter the Business ID manually.
NoteThe business system must uniquely identify the local system and client in the entire system landscape.
End of the note.Copy the External Identifier displayed and save it.
You will need both the business system and the external identifier later when you configure the system connection.
Configuring the Connection
You need to perform the following steps once in each system to be connected, each time a new scenario is created.
In the SOA Manager, go to the Technical Administration tab.
Create at least one profile.
More information: Creating and Editing a Configuration Profile
Create a system connection.
Go to the Technical Administration tab and choose System Connections.
An overview of provider systems is displayed.
Choose New.
A wizard is started.
Specify a name for the provider system, and specify a configuration profile.
Choose Next.
Specify the SLD ID, the Business System ID of the connected system and the connection data.
Specify the access configuration data for WSIL (Web Services Inspection Language).
WSIL is used to search the system directly for services.
For ABAP systems, the WSIL URL is as follows: http://<host name>:<http port number>/sap/bc/srt/wsil?sap-client=<client>
Specify the access configuration data for WSDL.
This is to access WSDL documents in the connected system. These WSDL documents will later be retrieved by the local system to automatically create logical ports for the remote services.
Note: This step is only relevant for the consumer system.
Specify at least one business application that is running on the connected system.
A business application is needed to assign a user account to a remote business system or application.
NoteThe external application key is the business system application ID in an ABAP system.
The external application key is maintained in provider system and used in consumer system.
To display the external identifier, start the SOA Manager in that business system and choose Global System Settings.
End of the note.Activate the system connection.
Creating a User Account
Go to the Service Administration tab.
Choose User Account Management.
Create a user account to be used to connect to the remote system.
Choose New and provide the information requested.
Choose Next.
Set the account type to Service User and specify the X 509 SSL Client Certificate and the signature PSE.
Choose Finish.
Assign the user account to the business application in the remote system.
Go to the Account Assignment tab.
Choose New and specify the business application and the service interface and its namespace.
Choose Next.
Specify the user account.
Choose Finish.