TIBCO Object Service Broker Modernization Guide

TIBCO Object Service Broker provides a programming environment and runtime that allows applications to run across multiple platforms, including mainframes, Windows, and UNIX systems. It facilitates access to various data sources like CICS, IMS, VSAM, and databases such as DB2 and Adabas. The product essentially acts as middleware, enabling interoperability between different systems and technologies.

TIBCO Object Service Broker is middleware. It provides a bridge between different platforms and data sources, allowing applications to interact with systems that would otherwise be isolated. It includes a programming environment and runtime for developing applications that can run across multiple platforms.

Organizations that rely on a mix of mainframe and distributed systems, and need to integrate data and applications across these environments, are good candidates for TIBCO Object Service Broker. This includes enterprises in industries like banking, finance, insurance, and government, where legacy systems are prevalent.

A company should consider TIBCO Object Service Broker when they need to integrate mainframe applications and data with newer, distributed systems. This is particularly relevant when modernizing applications, exposing mainframe data as services, or building new applications that need to interact with legacy systems.

Alternatives to TIBCO Object Service Broker include products like webMethods EntireX and other integration platforms that provide mainframe connectivity. Other options involve direct API access using tools like MVS Direct API or specialized integration solutions.

TIBCO Object Service Broker runs on IBM z/OS, Microsoft Windows, and UNIX platforms. On z/OS, it typically runs in an LPAR and interacts with subsystems like CICS and IMS. It requires access to data sources such as VSAM, DB2, CA Datacom/DB, and Adabas.

On z/OS, TIBCO Object Service Broker runs in an LPAR. It is z/OS dependent and may require specific subsystems like CICS or IMS to be active, depending on the data sources being accessed.

TIBCO Object Service Broker provides interfaces such as JCA, .NET, JavaBeans, Websphere MQ, and ODBC. It can expose APIs for accessing mainframe data and applications, allowing integration with other systems and technologies.

The architecture includes components that handle communication with mainframe systems (CICS, IMS), data access (DB2, VSAM), and integration with other platforms (Windows, UNIX). These components communicate using protocols appropriate to the specific environment, such as SNA for mainframe communication and TCP/IP for distributed systems.

TIBCO Object Service Broker enables organizations to integrate mainframe applications and data with modern systems, extending the life and value of legacy assets. It allows businesses to expose mainframe functionality as services, participate in enterprise-wide workflows, and build new applications that leverage existing mainframe investments.

By integrating mainframe systems with other platforms, TIBCO Object Service Broker helps reduce the risk associated with monolithic mainframe applications. It enables a more agile and flexible IT environment, allowing organizations to respond more quickly to changing business needs.

TIBCO Object Service Broker can be used to expose mainframe data and applications as services, making them accessible to a wider range of users and applications. This allows organizations to leverage their mainframe investments in new and innovative ways.

Security features include authentication mechanisms to verify user identities and access control models to restrict access to sensitive data and functions. Encryption is used to protect data in transit and at rest. Audit logging provides a record of user activity for security monitoring and compliance purposes.

TIBCO Object Service Broker controls access to mainframe datasets and applications based on user roles and permissions. This ensures that only authorized users can access sensitive information and perform critical functions.

Audit logging capabilities track user activity, including data access, application usage, and administrative actions. These logs can be used to monitor security, detect potential threats, and comply with regulatory requirements.

Deployment typically involves installing the software on the appropriate platforms (z/OS, Windows, UNIX) and configuring it to connect to the required data sources and systems. This may require expertise in mainframe technologies, networking, and security.

Ongoing operational requirements include monitoring system performance, managing user access, and performing regular maintenance tasks. This may require specialized skills in mainframe operations, security administration, and network management.

Implementation challenges may include configuring network connectivity between different platforms, ensuring data security and integrity, and resolving compatibility issues between different systems. Thorough planning and testing are essential for a successful implementation.