Flow of development in the FTP integration system

The following figure shows the flow of development in the FTP integration system. All the items in the figure are operations to be implemented in the development environment:

Figure 8-41 Flow of development in the FTP integration system

[Figure]

Organization of this section: (1) Importing a repository; (2) Defining an FTP adapter; (3) Defining a file operations adapter; (4) Defining a business process; (5) Defining an FTP reception; (6) Packaging and deployment definition of HCSC components; (7) Exporting the repository

(1) Importing a repository

The repository exported in the operating environment is imported into the development environment.

For details on how to import a repository, see "3.2.3 Importing a repository" in "Service Platform Basic Development Guide".

(2) Defining an FTP adapter

Use the Service Adapter Settings window to define an FTP adapter. Define one FTP adapter for each FTP server to be connected to.

For details on defining an FTP adapter, see "3. Defining Adapters" in "Service Platform Reception and Adapter Definition Guide".

(3) Defining a file operations adapter

Use the Service Adapter Settings window to define a file operations adapter. Define one file operations adapter for each operation, such as conversion, replication, and deletion.

For details on defining a file operations adapter, see "3. Defining Adapters" in "Service Platform Reception and Adapter Definition Guide".

(4) Defining a business process

Use the Define Business Process window to define a business process. Define a business process for each file transfer route.

For details on defining a business process, see "5. Defining Business Processes" in "Service Platform Basic Development Guide".

(5) Defining an FTP reception

Use the User-defined Reception Settings window to define an FTP reception. Define one FTP reception for each business process (define multiple FTP receptions as and when required). Note that you cannot map one FTP reception to multiple business processes.

For an overview of defining an FTP reception, see "8.4 FTP reception functionality". For details on defining an FTP reception, see "2.4 Defining FTP reception" in "Service Platform Reception and Adapter Definition Guide".

(6) Packaging and deployment definition of HCSC components

The definition files related to the definitions of the specified HCSC components, and the files provided by the execution environment are together packaged in an EAR file. This EAR file also defines the information for the cluster (or single HCSC server) that deploys the HCSC components (deployment definition).

For details on the packaging and deployment definition, see "7. Packaging HCSC Components and Defining Deployment" in "Service Platform Basic Development Guide".

(7) Exporting the repository

You export the repository that stores the definition files required for deploying the HCSC components. The information exported from the development environment is imported into the operating environment and used.

For details on exporting a repository, see "3.2.2 Exporting repository" in "Service Platform Basic Development Guide".

For details on how to operate an FTP integration system after being imported into the operating environment, see "5.4 HCSC server operations (for FTP integration)" in "Service Platform System Setup and Operation Guide".