Page Comparison

...

1. Navigate to the ESB management console and select Configure -> BAM -> Server Profile menu.
2. If there are no existing profiles, add one using the Add Profile link. If there are existing profiles, you can edit them using the Edit Profile link.
   
3. Enter the profile information in the page that opens. For example,Some of the fields are described below:
   
   
   • Server Credential: admin/admin by default
   • Server Transport: Thrift as the default Protocol
   • 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.
4. Define a set of stream configurations. For example,
   Each 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.
   • Dump header/Dump body, options: If you want to record SOAP header or SOAP body of messages respectively. 
   • Stream Properties: You can extract several types of properties from the message. 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.
5. After Stream Payload and Stream Properties are added/edited, click Update to reflect changes in the specific stream configuration.
6. Once all configurations are made to the BAM Server Profile, click Save.
7. Click the BAM Server Profile link at the top of the page to see the new profiles. Similarly, you can add any number of server profiles and unique stream configurations under one BAM server profile.

Setting the backend server for ESB endpoint

In order to test the functionality of the BAM mediator, you must define a sample WSDL proxy service along with an endpoint service to the WSDL proxy service. Here are the steps to create an endpoint service:

1. Go to <ESB_HOME>/samples/axis2Server/src/SimpleStockQuoteService and build the backend service with Apache Ant (You must have Apache Ant installed).
2. Go to <ESB_HOME>/samples/axis2Server and run the Axis2 server.
   
   
   • In Linux: axis2server.sh
   • In Windows: axis2server.bat
3. Test whether the proxy service WSDL exists in http://localhost:9000/services/SimpleStockQuoteService?wsdl.

Adding a proxy service to WSO2 ESB

These are the steps to create a sample WSDL Proxy Service to test the BAM mediator.

1. Go to ESB management console and select Main→Web Services→Add→Proxy Service from the side panel.
2. Click on WSDL Based Proxy to create a new WSDL based proxy.
3. Fill the form .as follows:
   
   1. Insert a suitable Proxy Service Name (eg: Simple_Stock_Quote_Service_Proxy).
   2. Set http://localhost:9000/services/SimpleStockQuoteService?wsdl as the WSDL URI.
   3. Set SimpleStockQuoteService as the WSDL Service.service
   4. Set SimpleStockQuoteServiceHttpSoap11Endpoint as the WSDL Port.
   Image RemovedImage Added
4. Click Create.
5. Select Click on the newly created proxy's name (here Simple_Stock_Quote_Service_Proxy ) form the shown list to see the Service Dashboard of itin this case) to go to its dashboard.

Adding a BAM Mediator to WSDL Proxy Service

...