Common Infrastructure Services Modernization Guide

Common Infrastructure Services (CIS) provides foundational routines and services leveraged by other Broadcom products. It offers a centralized set of functions that promote code reuse and consistency across different software solutions. CIS simplifies development and maintenance by providing common building blocks.

CIS is best described as a framework or set of middleware components. It is not a standalone application or complete system, but rather a collection of utilities and services designed to be integrated into other software products. It provides a common foundation for various applications.

Organizations that utilize multiple Broadcom products on z/VM or z/VSE operating systems are the most likely to benefit from CIS. These organizations often require consistent and reliable supporting services across their software landscape. CIS helps streamline operations and reduces redundancy.

A company should consider using CIS when they are deploying multiple Broadcom products that rely on its services. This ensures consistency and simplifies management. CIS is particularly valuable when integrating different Broadcom solutions within a single environment.

Alternatives to CIS depend on the specific services it provides within a given Broadcom product. In some cases, organizations might use custom-built routines or rely on operating system-provided utilities. However, these alternatives may not offer the same level of integration and consistency across Broadcom products.

CIS runs on z/VM and z/VSE operating systems. It is not z/OS dependent but operates within the environments provided by z/VM and z/VSE. Specific subsystems may be required depending on the Broadcom products that utilize CIS.

CIS is not a standalone product; it extends and enhances other Broadcom products. It provides supporting services that these products rely on. Therefore, the specific Broadcom products that depend on CIS must be present for it to function.

The specific components of CIS vary depending on the Broadcom product utilizing it. Common components might include data access routines, communication protocols, and utility functions. These components communicate through internal APIs and shared memory.

CIS does not typically expose external APIs directly. Instead, it provides internal APIs for use by other Broadcom products. The communication protocols used depend on the specific services being offered and the requirements of the consuming product.

CIS solves the business problem of inconsistent supporting services across different Broadcom products. Without CIS, each product might implement its own routines, leading to redundancy and increased maintenance costs. CIS promotes efficiency and reduces complexity.

If an organization did not use CIS, they would likely face increased development and maintenance costs due to duplicated efforts. Integrating different Broadcom products might also be more complex. CIS ensures a more streamlined and cost-effective approach.

The business value of CIS lies in its ability to reduce redundancy, simplify integration, and lower maintenance costs. By providing a common set of supporting services, CIS enables organizations to focus on their core business objectives rather than dealing with technical inconsistencies.

Security aspects of CIS depend on the specific services it provides and the Broadcom products that utilize it. Authentication methods and access control models are typically implemented within the consuming products, leveraging CIS for supporting functions.

CIS itself might not implement specific encryption algorithms directly. However, it may provide routines that other Broadcom products can use to implement encryption. The specific encryption methods used depend on the requirements of the consuming product.

Auditing and logging capabilities within CIS depend on the specific services being offered. Typically, the Broadcom products that utilize CIS are responsible for implementing their own auditing and logging mechanisms, potentially leveraging CIS for supporting functions.

Deployment of CIS is typically tied to the deployment of the Broadcom products that depend on it. It is usually deployed on-premise within the z/VM or z/VSE environments. The implementation process is often integrated with the installation of the consuming products.

The level of technical expertise required to implement CIS depends on the complexity of the Broadcom products that utilize it. Generally, a system programmer or someone familiar with z/VM or z/VSE environments is needed. Familiarity with Broadcom product installation procedures is also beneficial.

Ongoing operational requirements for CIS include monitoring the health of the z/VM or z/VSE environments and ensuring that the Broadcom products that depend on it are functioning correctly. Regular maintenance and updates may be required for both CIS and the consuming products.