The prjBatch_Record Project uses four Adapters, each represented in the Connectivity Map as a node between an External Application and a Service.
The inbound File Adapter properties are set from the Project Explorer’s Connectivity Map.
Double-click the inbound FileIn1 Adapter, located between the FileIn1 External Application and the jcdBatch_Record1 service.
The Properties Editor opens to the inbound File Adapter properties.
Modify the configuration for your system, including the settings in the following table.
Inbound File Adapter Connectivity Map Properties |
|
---|---|
Parameter Settings - Set as directed, otherwise use the default settings |
|
Input File Name |
FileInput.txt |
From the Connectivity Map, modify the outbound FileOut1 Adapter configuration for your system, including the settings in the following table.
Outbound File Adapter Connectivity Map Properties |
|
---|---|
Parameter Settings - Set as directed, otherwise use the default settings |
|
Output File Name |
FileOutput.txt |
From the Services tree, right-click the esFile External System, and select Properties.
The Properties Editor opens to the File Adapter Environment properties.
Modify the File Adapter Environment properties for your system, including the settings in the following table, and click OK.
File Adapter Environment Properties |
|
---|---|
Inbound File⇒Parameter Settings - Set as directed, otherwise use the default settings. |
|
Directory |
An input directory on your system that the inbound File Adapters poll and pick up any specified input files. |
Outbound File Adapter⇒Parameter Settings - Set as directed, otherwise use the default settings. |
|
Directory |
An output directory to which the outbound File Adapter publishes (writes) the output messages. |
The BatchRecord_Create Adapter’s specific properties are set from the Connectivity Map.
Modify the BatchRecordCreate Adapter Connectivity Map properties.
From the Connectivity Map, double-click the Adapter.
The Properties Sheet opens to the Adapter’s Connectivity Map properties.
Modify the configuration for your system, including the settings in the following table.
BatchRecordCreate Adapter Connectivity Map Properties |
|
---|---|
General Settings - Set as directed, otherwise use the default settings |
|
Parse or Create Mode |
Create |
Record - Set as directed, otherwise use the default settings |
|
Delimiter on Last Record |
No |
Record Delimiter |
~ |
Record Type |
Delimited |
From the Connectivity Map, double-click the BatchRecordParse Adapter.
The Properties Editor opens to the Adapter’s Connectivity Map properties.
Modify the configuration for your system, including the settings in the following table.
BatchRecordParse Connectivity Map Properties |
|
---|---|
General Settings - Set as directed, otherwise use the default settings |
|
Parse or Create Mode |
Parse |
Record - Set as directed, otherwise use the default settings |
|
Delimiter on Last Record |
No |
Record Delimiter |
~ |
Record Type |
Delimited |
The BatchRecordCreate and BatchRecordParse Adapters share the same Environment Properties. The default BatchRecord Adapter Environment property settings can be used for this Project, but they must be accepted.
From the Services tree, right-click the esBatchRecord External System, and select Properties.
The Properties Editor opens to the BatchRecord Adapter Environment properties.
Click OK to accept the default settings and close the Properties Editor.
Save the current changes to your Repository.
A Deployment Profile is used to assign Collaborations and message destinations to the Sun Java System Application Server and message server. Deployment Profiles are created using the Deployment Editor.
From the Enterprise Explorer’s Project Explorer, right-click the Project (prjBatch_Record) and select New ⇒ Deployment Profile.
Enter a name for the Deployment Profile (for this sample dpBatch_Record).
Make sure that the selected Environment is envBatch_Record .
Click OK.
Click Automap.
The Project’s components are automatically mapped to their respective system windows.
If any of your Project components did not successfully map to an external system, open each of your Adapter’s configuration properties (Connectivity Map and Environment) and click OK to close and save the current configuration, then click Automap again.
Save the Project.