What infrastructure is required?

NJE/IP Bridge typically runs on z/OS, z/VSE, or z/TPF systems. It requires a TCP/IP stack to be configured and active on the mainframe. It may also require configuration of NJE parameters to ensure proper communication with other nodes.

For mainframe products: Does this run in an LPAR?

For mainframe products, NJE/IP Bridge typically runs in an LPAR. It is dependent on the z/OS or z/VSE operating system and requires the JES subsystem to be active. It may also require specific TCP/IP configurations within the LPAR.

Does this extend/enhance another product?

NJE/IP Bridge extends the capabilities of JES by enabling NJE communication over TCP/IP. It requires JES to be configured and active, as it relies on JES for job and file management. It does not replace JES but rather enhances its communication capabilities.

What are the main system components?

The main system components include the NJE/IP Bridge server, configuration files, and TCP/IP stack. The server listens for incoming connections and manages NJE traffic over TCP/IP. Configuration files define the NJE node parameters and TCP/IP settings.

What is the business value of using NJE/IP Bridge?

NJE/IP Bridge enables organizations to modernize their mainframe communication infrastructure, reduce costs associated with SNA networks, and improve integration between mainframe and distributed systems. This can lead to increased efficiency and agility in business processes.

What would happen if an organization did NOT use this product?

Without NJE/IP Bridge, organizations would be limited to using SNA networks for NJE communication, which can be costly and less flexible. They would also face challenges in integrating mainframe systems with modern TCP/IP-based networks, potentially hindering business innovation.

What business problem does it solve?

NJE/IP Bridge helps solve the problem of integrating mainframe systems with modern TCP/IP networks. It allows organizations to leverage their existing mainframe investments while taking advantage of the benefits of TCP/IP, such as lower costs and increased flexibility.

What specific authentication methods are supported?

NJE/IP Bridge supports various authentication methods, including basic authentication and potentially integration with external security systems such as RACF or ACF2. The specific authentication methods depend on the configuration and integration with existing security infrastructure.

What access control model is used?

The access control model used by NJE/IP Bridge depends on the underlying security system in place. It can leverage RACF, ACF2, or other security systems to control access to NJE resources. The access control is typically based on user IDs and group memberships.

What encryption is used and where?

NJE/IP Bridge uses encryption to protect NJE traffic transmitted over TCP/IP networks. The specific encryption algorithms used depend on the configuration and security requirements. Encryption is typically applied to the data stream to prevent eavesdropping.

What audit/logging capabilities exist?

NJE/IP Bridge provides audit and logging capabilities to track NJE traffic and security events. The logs can be used to monitor system activity, detect security breaches, and ensure compliance with regulatory requirements. The logs typically include information about user access, file transfers, and job submissions.

How is this product typically deployed?

NJE/IP Bridge is typically deployed on-premise, running on mainframe systems within the organization's data center. It requires technical expertise to configure and maintain the software, including knowledge of mainframe systems, TCP/IP networking, and security protocols.

What ongoing operational requirements exist?

Ongoing operational requirements include monitoring the NJE/IP Bridge server, maintaining configuration files, and ensuring the security of the system. This may require dedicated staff with expertise in mainframe systems, TCP/IP networking, and security administration.

What are common implementation challenges?

Common implementation challenges include configuring the TCP/IP stack on the mainframe, ensuring proper NJE routing, and integrating with existing security systems. It may also be challenging to troubleshoot network connectivity issues between the mainframe and distributed systems.

What administrative interfaces are available?

Administrative interfaces for NJE/IP Bridge typically include a command-line interface (CLI) and configuration files. The CLI is used to manage the server, configure NJE parameters, and monitor system activity. Configuration files define the NJE node parameters and TCP/IP settings.

Share Your Product Experience

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

Share Your Experience

NJE/IP Bridge

Name: NJE/IP Bridge
Availability: InStock

Barnard Software Active z/OS zVSE/VSEn

Networks and Communication File Transfer

Vendor

Barnard Software

Product Overview

NJE/IP Bridge provides JES NJE file and job transfers over TCP/IP for z/OS, z/VSE, and z/TPF systems, enabling communication between mainframes and UNIX systems like Linux and AIX. It solves the problem of integrating mainframe systems with modern TCP/IP networks, reducing reliance on SNA. Without it, organizations are limited to SNA.

The architecture includes the NJE/IP Bridge server, configuration files, and TCP/IP stack. The server listens for connections and manages NJE traffic. Configuration files define NJE node parameters and TCP/IP settings.

The product typically runs in an LPAR on z/OS or z/VSE and requires the JES subsystem. It extends JES by enabling NJE communication over TCP/IP. Common operations involve configuring the server, defining NJE routes, and monitoring traffic.

Alternatives include IBM Connect:Direct and CA XCOM Data Transport. Security features include authentication methods like basic authentication and integration with RACF or ACF2. Encryption protects NJE traffic over TCP/IP.

Audit and logging capabilities track NJE traffic and security events.

Frequently Asked Questions

What does NJE/IP Bridge do?

NJE/IP Bridge facilitates the transfer of JES NJE files and jobs over TCP/IP networks. It enables communication between mainframe systems (z/OS, z/VSE, z/TPF) and UNIX-like systems (Linux, AIX) using the NJE protocol over IP.

Is this a system, application, or tool?

NJE/IP Bridge is middleware that bridges the NJE protocol with TCP/IP networks. It allows systems that traditionally communicate via SNA/NJE to communicate over TCP/IP, enabling integration with modern network infrastructures.

What types of organizations use this?

Organizations that rely on mainframe systems for core business processes and need to integrate these systems with TCP/IP-based networks use NJE/IP Bridge. This includes enterprises in banking, finance, insurance, and government sectors.

When should we consider NJE/IP Bridge?

A company should consider NJE/IP Bridge when it needs to modernize its mainframe communication infrastructure, integrate mainframe systems with distributed systems, or reduce reliance on SNA networks. It is also useful when needing to transfer jobs and files between mainframes and UNIX-like systems.

What are the alternatives to NJE/IP Bridge?

Alternatives to NJE/IP Bridge include other NJE over IP solutions and products that provide similar file and job transfer capabilities. Some competitors include solutions from IBM and other vendors specializing in mainframe connectivity.

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

NJE/IP Bridge

Product Overview

Frequently Asked Questions

What does NJE/IP Bridge do?

Is this a system, application, or tool?

What types of organizations use this?

When should we consider NJE/IP Bridge?

What are the alternatives to NJE/IP Bridge?

What infrastructure is required?

For mainframe products: Does this run in an LPAR?

Does this extend/enhance another product?

What are the main system components?

What is the business value of using NJE/IP Bridge?

What would happen if an organization did NOT use this product?

What business problem does it solve?

What specific authentication methods are supported?

What access control model is used?

What encryption is used and where?

What audit/logging capabilities exist?

How is this product typically deployed?

What ongoing operational requirements exist?

What are common implementation challenges?

What administrative interfaces are available?

Related Products

More from Barnard Software

Similar Products

Help Improve This Directory

Share Your Product Experience