vODA\i2\start_i2ODA.bat (Windows only)

vODA/i2/start_i2ODA.sh (UNIX only)

Notes:

1.Except as otherwise noted, this document uses backslashes (\) as the convention for directory paths. For UNIX installations, substitute slashes (/) for backslashes.

2.All product path names are relative to the directory where the product is installed on your system.

Other installation requirements

vi2 provides the MetadataService adapter to obtain the metadata information from the registry. You need to install this adapter on an instance of the i2 application. Be sure to start the adapter prior to using the MetadataService.

vThe bindings file for the port MetadataService, for example, TDMMetadata.xml, which contains the port, operation, and type information, needs to be in the i2 configuration directory.

vThe Visibroker Object Activation Daemon needs to run on the machine that is running the agent and the one on which Business Object Designer is installed.

Launching i2 ODA

Before you begin: Ensure that the i2 ODA and XML schema ODA are installed on your system.

You can launch i2 ODA in either of the following ways:

vAutomatically—If you registered i2 ODA with the Visibroker Object Activation Daemon (OAD), you do not need to start i2 ODA manually. OAD maintains a list of registered ODA names and listens for requests to start the ODA. When you select the ODA’s name in Business Object Designer, OAD starts the ODA.

For information on registering i2 ODA, see IBM WebSphere System Installation Guide for UNIX or for Windows.

vManually—If you have not registered i2 ODA with the Visibroker Object Activation Daemon, start it by running the appropriate file:

UNIX: start_i2ODA.sh

Windows: start_i2ODA.bat

You have to add the proper path to the start files for CIS-SDK and j2ee.jar Example: The following path information needs to be added to start_i2.bat file:

set I2_CIS_HOME_DIR=C:\i2\CIS\6.0\cis-sdk set J2EE_PATH=C:\J2EE_JAR

Note: These are just examples. You should change the path information depending on your local installation.

You configure and run i2 ODA using Business Object Designer. Business Object Designer locates each ODA by the name specified in the AGENTNAME variable of each script or batch file. The default ODA name for this connector is i2ODA. During installation, if you register the ODA with the Visibroker Object Activation Daemon, the wizard automatically prefixes the host name to the AGENTNAME value to make it unique.

18Adapter for i2 User Guide

Page 27 Page 29
Page 28
Image 28
IBM WebSphere Business Integration Adapter manual Launching i2 ODA, Other installation requirements
Page 27 Page 29

WebSphere Business Integration Adapter specifications

IBM WebSphere Business Integration Adapter is an essential component of IBM's integration solutions, providing organizations with a robust framework to connect various systems, applications, and data sources. This versatile solution is particularly designed to streamline the integration of enterprise applications and enhance their interactions.

One of the main features of the WebSphere Business Integration Adapter is its wide range of pre-built adapters. These adapters facilitate seamless connectivity with diverse applications, such as ERP systems, CRM software, databases, and legacy systems. This wide compatibility ensures that organizations can automate processes and share data effortlessly, reducing the time and overhead typically associated with manual integrations.

Another notable feature of the integration adapter is its support for various messaging protocols, including JMS, MQ, and HTTP. This multi-protocol support enables organizations to easily implement message-driven architectures by facilitating reliable and asynchronous communication between disparate systems. As a result, businesses can achieve greater scalability and responsiveness in their operations.

The technology stack behind IBM WebSphere Business Integration Adapter also incorporates standards-based protocols, such as Web Services (SOAP, REST) and XML messaging. This adherence to industry standards ensures that the adapter can easily integrate with modern cloud-based applications and services, providing organizations with the flexibility to adapt to evolving technological landscapes.

In addition to its core integration capabilities, the WebSphere Business Integration Adapter supports comprehensive monitoring and management features. Administrators can easily track the performance of integration flows, monitor message processing, and manage exceptions through an intuitive dashboard. This visibility enables organizations to proactively address issues before they escalate, ensuring smooth and uninterrupted operations.

Another significant characteristic of the IBM WebSphere Business Integration Adapter is its scalability. Organizations can deploy the adapter in various environments, from on-premise data centers to cloud infrastructures. This flexibility allows businesses to scale their integration solutions as needed, accommodating growing data volumes and increasing transaction demands with ease.

Moreover, the adapter's modular architecture makes it easy to customize and extend. Businesses can enhance existing functionalities or integrate additional capabilities to meet specific requirements, ensuring that their integration solutions remain relevant and effective in an ever-changing business landscape.

In conclusion, the IBM WebSphere Business Integration Adapter is a powerful tool for organizations looking to enhance their system integrations. With its extensive features, support for multiple technologies, and capacity for customization, it positions businesses for success in an increasingly interconnected world. By leveraging this adapter, organizations can achieve greater efficiency, agility, and operational excellence in their integration efforts.
Top Page Image Contents