Testing a Process with AEX

Objective

After completing this lesson, you will be able to test the procurement process with AEX

Process Deployment Overview

Process Development Phases

In general, process development involves the following phases:

  • Process creation

  • Process building

  • Process deployment

  • Process execution

  • Process monitoring

In this unit you will perform the final steps before building and deploying the process. After that, you will start and monitor the process.

Consumer Side Configuration

During import to the Business Process Model and Notation (BPMN) process, all imported service Interfaces must be assigned to a service reference. Any number of service references can be created. A service reference summarizes all the service interfaces that call the same Application Server for Java (AS Java) server as a Web service consumer.

The figure shows the places in the system, where the different types of protocols are maintained.

The following two types of protocols are used for messages:

  • SOAP message protocol.

  • XI message protocol 3.0.

In the AS Java server, each service reference is assigned to exactly one target system by the SOAP (WS) message protocol.

The procedure for configuring system connections is as follows:

  1. The target system must first be configured in SAP NetWeaver by choosing Technical ConfigurationSystem Connections.

  2. The technical connection data such as URL, user, and time out is maintained. Additionally, a communication profile is assigned. In the example, it is the profile SAP_DEFAULT_PROFILE.

  3. Communication profiles are created and configured in the Connections Profile tab. This tab describes the profile's transport security and the various authentication options. It is not necessary to configure service references with the XI message protocol 3.0.

The procedure for configuring application communications is as follows:

  1. In the SAP NetWeaver Administrator, under SOAApplication and Scenario Communication, choose the communication application according to the product you have installed and now want to configure.

  2. The service interfaces that are used with WS-consumer clients appear in the lower half of the screen.

  3. The defined service references appear in the Consumed Service Groups tab. Provider systems are assigned here.

Provider Side Configuration

During deployment, the defined message triggers in the process are installed as callable Web services. In order for these message triggers to be accessible to endpoints, they must be assigned to communication profiles.

Communication applications are chosen in the NetWeaver Administrator under SOAApplication and Scenario Communication according to the product you installed and now want to configure.

All service Interfaces, which are configured as a trigger in the BPMN process, can be found in the Provided Services tab. Those service interfaces, which are using the WS as connectivity, are assigned a communication profile.

Communication profiles are created under SOATechnical ConfigurationSystem Connections. This data is found in the WSDL. The figure, System Connections Data in the WSDL File, shows an example of the WSDL for the trigger GetFromTrigger.

The figure shows a WSDL file and the system connections in it.

Process Initialization

BPMN processes are always initiated by a WS-call at the endpoint of start message events. The start message event acts as a Web service provider.

Methods for Starting the Web Service

  • On the Process Repository in SAP NetWeaver Administrator

  • Using the Web Service Navigator as a WS client

  • Over any WS client

Start of a Process by the Process Repository

The start procedure in the Process Repository contains the following steps:

Step 1

The Process Repository is accessed through the SAP NetWeaver Administrator under ConfigurationProcesses and TasksProcess Repository. From there you can filter the results by software components:

Step 2

The different versions of the selected software component appear in the middle of the screen.

Step 3

The Processes and Tasks tab displays the BPMN processes that can be chosen. Choose the Start Process button to start the previously selected software component:

Step 4

Choosing the Start Process button opens a new window. From here you can see the URL of the Web Service Definition Language (WSDL) of the start message event trigger.

Step 5

Here the message type appears as an editable table. In this case the message type is empty.

Step 6

The process is started by choosing the Start Process button:

Step 7
Choose the Details link to open the View started processes link.
Step 8
To view a list of started processes, choose the View Started Processes link.
Step 9
The Process Instances monitor shows the pre-selected process ID of the newly started process.

Log in to track your progress & complete quizzes