From the Connectivity Map, double-click the outbound File1 Adapter.
The Properties Editor opens to the outbound File Adapter properties.
Modify the 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%d.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 |
|
---|---|
Parameter Settings - Set as directed, otherwise use the default settings. |
|
Directory |
The directory on the system where files are sent. |
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_Inbound_FTPIn_LocalFileOut) and select New ⇒ Deployment Profile.
Enter a name for the Deployment Profile (for this Project, use dpBatch_Inbound_FTPIn_LocalFileOut).
Make sure that the selected Environment is envBatch_Inbound_FTPIn_LocalFileOut.
Click OK.
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.