Page Comparison

...

The following sections explain You can only how to use the existing BAM Mediator configuration when editing a mediation sequence. These steps are explicitly described for , using a sample in the following sectionsscenario.

• Configure BAM Server Profiles and Streams
• Set the Backend Server for ESB Endpoint
• Add a proxy service to WSO2 ESB
• Add a BAM Mediator to WSDL Proxy Service
• Send Messages To the ESB

...

Configuring BAM server profiles and streams

Anchor
Configure BAM Server Profiles and Streams Configure BAM Server Profiles and Streams

Before adding a BAM mediator to a mediator sequence, you must update the BAM mediator configurations should be updated as below. Configuration information are basically is considered as a set of BAM server profiles, which contains contain transport and credential data required to connect to the BAM server. In each BAM server profile, you must define one or many Event Stream configurations should be definedevent stream configurations. Streams contain Thrift API event - stream - related information like Stream Name, Stream Version etc. and the data to be extracted from the configuration context of the mediation sequence. 1. The steps below explain this.

1. Navigate to the ESB management console and select

...

1. Configure -> BAM -> Server Profile

...

1. menu.

...

1. If there are no existing

...

1. profiles, add one using the

...

1. Add Profile

...

1. link.

...

1. If there are

...

1. existing profiles, you can edit them using the

...

1. Edit Profile

...

1. link.

...

1. 
   Image Added
2. Enter the profile information

...

1. in the

...

Image Removed

...

1. page that opens. For example,Image AddedSome of the fields are described below:
   
   
   • Server Credential: admin/admin by default

...

1. • Server Transport: Thrift as the default Protocol

...

1. • Enable Load Balancer: Enable if want to load balance with Thrift from the client side to several hosts. Then enter comma separated connection URLs of hosts as URL Set. e.g.: tcp://10.200.3.218:7611, tcp://10.100.3.97:7611. refer more details on using load balancing publishing in this page.
   • Enable Security: If message confidentiality is required from ESB server to BAM server, select this option.
   • IP Address: IP of the BAM server's Thrift server. By default, it is the IP address of the localhost.
   • Receiver Port:  If security is not enabled, this option will have to be given. Enter 7611 by default, which is the Thrift server port.
   • Authentication Port: Port number is 100 times greater than the Receiver Port, if the latter exists. Default Authentication Port number is 7711.
   • Test Server button: Using this, availability of the BAM server can be tested for the given IP Address and the Authentication Port.

...

1. Define a set of

...

1. stream configurations. For example,
   Image AddedEach stream must have the following defined:
   
   
   • Name: Stream Name can be any string with alpha-numeric characters.
   • Version: Stream Version distinguishes different streams with the same Stream Name. Default version should be 1.0.0.
   • Nickname: This is a user-preferred nick name to the Stream Name in alpha-numeric characters.
   • Description: A description about the particular stream defined by Stream Name/Stream Version pair. Description should also consist of alpha-numeric characters.

...

1. • Dump header

...

1. • /Dump body,

...

1. • options: If you want to record SOAP header or SOAP body of messages respectively.

...

1. •  
   • Stream Properties

...

1. • : You can extract several types of properties from the message.

...

1. • Properties are divided into two as Value and Expression.
     
     • Value: A constant alpha-numeric string value entered to Value field is set as the property.
     • Expression: The given expression in Value field is considered as an expression and executed on the message to get the property. XPath properties and functions available in ESB are valid in the expression. (Note : At the moment, there is no way to add namespaces to xpath expressions which is to be completed in future. It is given in JIRA https://wso2.org/jira/browse/BAM-539 . As a workaround, you can use Property Mediator in ESB, to get the xpath and add it to the message context as a property which can then be captured from the BAM mediator using the get-property expression.)
     • Type drop down list: The required type to be converted in which the property should be sent via Thrift
      
   At the time you define the mediator definition, you can select a stream from the ones you define here.

...

1. After "Stream Payload" and "Stream Properties" are added/edited, click the "Update" icon to reflect changes in the specific Stream Configuration. Next, click the "Add" icon to add the new Stream Property to the properties list. The "Cancel" button ignores the updated Stream Properties data.

7. After the changes are properly made to the BAM Server Profile, click on "Save" button to save all the configuration data to the secondary storage.

...