Any iSeries™ server application that was written to use Distributed Data Management (DDM) can use OptiConnect. This is true for existing applications as well as new applications. Many applications that use an iSeries server database can transparently use DDM without changes to the application. OptiConnect uses the same mechanism as traditional DDM, where the DDM file controls access to a database. Applications that access a database by using OptiConnect DDM can also use traditional APPC DDM to access another database at the same time.
There are two ways to route data requests through OptiConnect. The first is the Fastpath OptiConnect method and involves specifying a special keyword in the DDM file. The second method involves setting up Extended Function Path OptiConnect. If you are using the Fastpath method, OptiConnect agent jobs start in the OptiConnect Connection Manager and run in the QSOC subsystem. These jobs follow the OptiConnect job naming convention. Fastpath OptiConnect is the faster means of communication due to shorter code path, but two-phase commit protocols are not supported.
If the Extended Function Path method is used, OptiConnect agent jobs are started by the advanced program-to-program communications (APPC) attach manager and run in QCMN subsystem. The agent job names follow the standard DDM naming conventions for communication jobs. Two-phase commit protocols are supported.
The following information discusses the various ways you can configure OptiConnect: