What infrastructure is required?

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.

For mainframe products: Does this run in an LPAR?

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.

What APIs and interfaces are supported?

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.

What are the main architectural components?

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.

What is the business value of using TIBCO Object Service Broker?

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.

How does this product help reduce business risk?

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.

Can this product expose mainframe data as services?

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.

What security features are included?

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.

How does this product control access to mainframe data?

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.

What audit logging capabilities exist?

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.

How is TIBCO Object Service Broker typically deployed?

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.

What ongoing operational requirements exist?

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.

What are common implementation challenges?

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.

Share Your Product Experience

Help the community by sharing your experience with mainframe products. Your insights help others make informed decisions.

Share Your Experience

TIBCO Object Service Broker

Name: TIBCO Object Service Broker
Availability: InStock

TIBCO Supported z/OS

Legacy Application/Data Access Application Development

Vendor

TIBCO

Product Overview

TIBCO Object Service Broker is designed to provide a robust and scalable architecture for integrating mainframe systems with distributed environments. NET, JavaBeans, Websphere MQ, and ODBC; and the Management Console, which provides a centralized interface for configuring and monitoring the system. The Broker Server communicates with mainframe systems using protocols such as SNA and TCP/IP.

It supports access to data sources like CICS, IMS, VSAM, and databases like DB2 and Adabas. The Adapter Framework allows applications to interact with the Broker Server using standard APIs and interfaces. The Management Console provides a web-based interface for configuring connections, managing users, and monitoring system performance.

The architecture supports both synchronous and asynchronous communication patterns, allowing for flexible integration scenarios. It can be deployed on-premise or in a hybrid cloud environment. Alternatives include webMethods EntireX, which offers similar mainframe integration capabilities, but TIBCO Object Service Broker provides a more comprehensive set of interfaces and a multi-platform runtime environment.

Frequently Asked Questions

What does TIBCO Object Service Broker do?

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.

Is this a system, application, or tool?

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.

What types of organizations use this?

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.

When should we consider TIBCO Object Service Broker?

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.

What are the alternatives to TIBCO Object Service Broker?

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.

Help Improve This Directory

Notice outdated information? Have insights about this product? Help the mainframe community stay informed with accurate, current data.

Report Issue Suggest Product Share Event

Share Your Product Experience

Help the community by sharing your experience with mainframe products. Your insights help others make informed decisions.

Share Your Experience

Share Your Product Experience

TIBCO Object Service Broker

Product Overview

Frequently Asked Questions

What does TIBCO Object Service Broker do?

Is this a system, application, or tool?

What types of organizations use this?

When should we consider TIBCO Object Service Broker?

What are the alternatives to TIBCO Object Service Broker?

What infrastructure is required?

For mainframe products: Does this run in an LPAR?

What APIs and interfaces are supported?

What are the main architectural components?

What is the business value of using TIBCO Object Service Broker?

How does this product help reduce business risk?

Can this product expose mainframe data as services?

What security features are included?

How does this product control access to mainframe data?

What audit logging capabilities exist?

How is TIBCO Object Service Broker typically deployed?

What ongoing operational requirements exist?

What are common implementation challenges?

Related Products

More from TIBCO

Harbor HFT

Harbor NSM

Managed File Transfer Platform Server

TIBCO ActiveMatrix Businessworks Plugin for CICS

TIBCO Adapter for Files

TIBCO EMS

Similar Products

Ab Initio Business Rules Environment

Access Manager for CICS

Access Manager for IMS

ACCOLADE

Adabas SQL Gateway

ADF II

Help Improve This Directory

Share Your Product Experience