...
To create an ESB Config Project, click on Create New Project link. 
Give a name to the ESB Config Project and click Finish. 
Now you will see that the created ESB Project is set in the Save endpoint in field. 
Now you will see that the endpoint has been created inside the ESB Project that you have created. Once you double click on the MainFrameEP node, you will see that the Properties view gets focused. You need to update the URI field with the correct JMS URI that appears in the App Server after deploying the two mock services.
Save the configuration and now we are done with the address endpoint.
...
Right-click on the ESB Configuration Project, then select New ->Proxy Service. Choose the second radio button Import Proxy Service and click Next. Browse to $DOWNLOAD_HOME/banking-sample/esb/synapse-configs/default/proxy-services and select AccountServiceProxy.xml and click Finish. 
Make sure the correct endpoint is being referenced. In the Properties window below, select the row with the Endpoint on it, then click on the button on the far right containing ellipsis (…).
In the Resource Key Editor that pops up, select click workspace.
Expand Carbon Application Endpoints and ESB Configuration Project , then select MainframeEP .
...
1. Create an "address endpoint" for the CardService on the ESB
In the same manner , that you create the MainFrameEP, create the cardServiceEP. Resource file for cardServiceEP can be found at $DOWNLOAD_HOME/banking-sample/esb/synapse-configs/default/endpoints 
Once the endpoint has been created, make sure that the correct URI has been specified.
2. Create a service on the ESB that will act as a proxy to the Cards system
...
Give the name as CardService and select Custom Proxy from Proxy Service Type and click Finish. 
Now you will find a basic template for a custom proxy has been created in the workspace. Next we have to configure it according to our scenario.
Once the CardService has been opened in Design view, you will see that there are three basic sections in the proxy service; InSequence, OutSequence and FaultSequence (red rectangle).
...
Select Import from file system and click Next. 
Click Browse and browse for the transform.xslt file at $DOWNLOAD_HOME/banking-sample/esb/cardService.
Set Registry path to deploy as /_system/config/transform. Note that this is the same path we set when creating CardService. 
With WSO2 Developer Studio, we create all the Registry Resources in a project type called Registry Resources Project. If your workspace has already created Registry Resources Projects, you can point one of them to save your registry resource.
If you do not have created Registry Resources Project, you will have to create a Registry Resource Project in order to create the Registry Resource. To create a Registry Resource Project, click on the link Create New Project.... 
Give the necessary information for the Registry Resource Project and click Finish. 
Now you can see that the created Registry Resources Project is set in the Save resource in field. Once you fill all the information, click Finish. 
Now you will see that the new Registry Resources Project has been created in the workspace.
We have successfully completed the two proxy services for the mock services.
...
You will see that the new BPEL Workflow has been created in the workspace. 
Note that this is just a template BPEL. We need to create the process file according to our scenario. If you are familiar with BPEL, you can use the graphical editor to drag and drop necessary elements from the palette.
For this scenario, you can find already developed BPEL file and other WSDL files from $DOWNLOAD_HOME/banking-sample/bps/AccountOpeningProcess.
Copy all the files from that location and paste in to AccountOpeningProcess project. 
Now we have successfully completed all the parts that we need to try the scenario.
Deploy the SOA Integration Solution
...
Open the pom.xml under Banking Sample. If it is already opened, you will have to refresh the file in order to view all the artifacts in the design view. 
Select all the artifacts by clicking the Select All button. Now we want to change the server role of the Registry Resource from Governance Registry to Enterprise Service Bus since we need to deploy the XSLT file in to local registry of the WSO2 ESB. 
Now we are ready to create the CAR file from the BankingSample C-App project.
To create the CAR file, click on the Create Archive button at the right hand corner of the design view of the pom.xml. You can achieve the same option by right click -clicking on the BankingSample C-App project and select selecting Export Composite Application Project.
Specify the location you want to save the CAR file. Now you will see that the BankingSample.car file has been created in the given location and you can deploy this CAR file in to WSO2 Servers.
Testing the Working Solution
...
Once you click this link, you will be prompted to select the CAR file you have saved to your file system. Upload it, then watch the console for messages that the CAR file has been deployed and the appropriate services have also been deployed. 
You will find the following artifacts in different servers once you deploy the CAR file to all the servers. The application BankingSample should be listed in all the servers as well.
| Server | Deployed Artifacts |
| WSO2 App Server | MainframePojoService, CardAxis2Service |
| WSO2 ESB | MainFrameEP, cardServiceEP, AccountServiceProxy, CardService, transform.xslt |
| WSO2 DSS | CustomerDS |
| WSO2 BPS | AccountOpeningProcess |
...