### Exporting and Testing a Split-Join

You can export and test a Split-Join on an ALSB server provided that it is associated with a transport typed business service. Exporting and testing a Split-Join can include the following tasks:

- Creating a Transport Typed Business Service
- Exporting the Split-Join Files
- Testing the Split-Join in the Test Console

#### Creating a Transport Typed Business Service

A Split-Join is used by a particular transport typed business service. If you do not have an appropriate business service, you must create one before you can export or test your Split-Join. There are two ways to create a business service:

1. Create the business service manually in WorkSpace Studio or the ALSB console.
2. Generate the business service automatically from the Split-Join (.flow) menu:

1. Right click on the Split-Join (.flow) file in the Project Explorer to open the Split-Join menu.
2. Select AquaLogic Service Bus.
3. Select Generate Business Service.
4. Name and save the new service in a project.

After you create the business service, you can export the Split-Join provided that it has no errors.

Note: | It is a helpful practice to place the associated business service in the same ALSB project as the Split-Join. It can also be useful to give the business service the same name as the Split-Join so that they are easily correlated.

#### Exporting the Split-Join Files

Split-Joins without errors can be exported to an ALSB server.

Note: | Errors appear in the Problems view of the Split-Join editor. If you try to export a Split-Join with errors, the export fails.

There are three ways to export a Split-Join:

1. Export from the Business Service Menu
2. Auto-export
3. Manual export

##### Exporting from the Business Service Menu

It is possible to export a Split-Join directly from the Business Service menu. However, because exporting by this method automatically launches the ALSB Test Console, it is useful if you want to both export and test. Exporting from the Business Service menu involves the following steps:

1. In the Project Explorer, right click on the Business Service (.biz file) to be exported/tested.
2. Select Run as.
3. Select Run on server. The Run on Server Dialog opens.
4. Select an existing server or define a new one and go to the next step.
5. In the Add and Remove Projects window, the ALSB project containing the business service and any other dependent files have been pre-selected for configuration/export. They can not be removed because the business service can not be tested without its dependent files. The entire Split-Join will therefore be exported.
6. Select Finish, and the ALSB Test Console will launch. You can now test the business service.

##### Auto-export

A Split-Join can be auto-exported to an ALSB server. If you use this method, you must manually launch the ALSB console in order to test the exported files. Auto-exporting involves the following steps:

1. Select File > Export.
2. Select AquaLogic Service Bus.
3. Select Resources to ALSB Server. This will export the resources to the ALSB server, but it will not launch the ALSB Test Console. You must launch the Test Console manually within the ALSB console application.

##### Manual export

A Split-Join can be manually exported to an ALSB server. If you use this method, you must manually launch the ALSB console to test the exported files. Manually exporting involves the following steps:

1. Select File > Export.
2. Select AquaLogic Service Bus.
3. Select Resources as Configuration JAR and go to the next step.
4. In the ALSB Configuration JAR Export window, configure the following options:

1. Select the ALSB Configuration file containing the files to be exported.
2. Set the Export Level to Project or Resource depending upon whether you wish to export entire projects or individual files. The selection available in the tree below will change based upon the Export Level.
3. Select the projects and/or resources to be exported in the configuration JAR.
4. Select Include Dependencies if you want to export any file dependencies associated with the selected files.
5. Browse to a destination for the exported JAR file.
6. Click Finish to export the JAR file.

5. Import the JAR file via the ALSB console.

Note: | A quick way to access the ALSB console from the IDE is to select Launch ALSB Administration Console from the server menu. (Right-click the appropriate server in the Servers view.)

#### Testing the Split-Join in the Test Console

You can test a Split-Join by executing the business service that uses it in the ALSB Test Console. This can either be done within the Split-Join editor or by exporting the Split-Join to an ALSB server. To test the Split-Join within the IDE, you need to export the files using the menu for the business service that uses the Split-Join.

##### Exporting from the Business Service Menu

You can export and test a Split-Join directly from the Business Service menu. If you use this method, the export happens in the background while the ALSB Test Console launches. Exporting from the Business Service menu involves the following steps:

1. In the Project Explorer, right click on the Business Service (.biz file) to be exported/tested.
2. Select Run as.
3. Select Run on server. The Run on Server Dialog appears.
4. Select an existing server or define a new one and go to the next step.
5. In the Add and Remove Projects window, the ALSB project containing the business service and any other dependent files have been pre-selected for configuration/export. The dependent files cannot be removed because the business service cannot be tested without its dependent files.

Click Finish, and the ALSB Test Console will launch. You can now test the business service.

Note: | Although only the ALSB Test Console is displayed at this point, the entire Split-Join has been exported to the ALSB server.