Name: OV/RerRouter
Availability: InStock

Question 1

What is the primary function of OV/RerRouter?

Accepted Answer

OV/RerRouter facilitates the rerouting of email messages within an OfficeVision MVS environment. It allows administrators to define rules for redirecting messages based on various criteria, such as sender, recipient, or content. This ensures efficient email delivery and management within the z/OS system.

Question 2

What criteria can be used to define email rerouting rules?

Accepted Answer

OV/RerRouter supports rerouting email based on sender, recipient, and message content. Administrators can configure rules using a combination of these criteria to precisely control email flow. This flexibility allows for complex routing scenarios to meet specific organizational needs.

Question 3

How does OV/RerRouter integrate with the OfficeVision MVS environment?

Accepted Answer

The product integrates with OfficeVision MVS and the underlying z/OS system. It utilizes configuration files to store rerouting rules and interacts with the email system to intercept and redirect messages. This integration ensures seamless operation within the existing infrastructure.

Question 4

What administrative interfaces are available for managing OV/RerRouter?

Accepted Answer

OV/RerRouter provides a command-line interface (CLI) for administration. Administrators can use specific commands to manage rerouting rules, monitor email flow, and perform system maintenance. The CLI offers direct control over the product's functionality.

Question 5

What are some common commands and their syntax?

Accepted Answer

Common commands include ADDROUTE, DELETEROUTE, LISTROUTE, and START/STOP. The syntax for ADDROUTE is typically: ADDROUTE SENDER(user@domain) RECIPIENT(newuser@newdomain). Configuration files are used to store routing rules, and these are typically text-based files that can be edited using a z/OS editor.

Question 6

What types of APIs does OV/RerRouter expose?

Accepted Answer

The product does not expose REST or SOAP APIs. Communication relies on native z/OS interfaces and file-based configurations. Integration is typically achieved through JCL and system utilities available on the z/OS platform.

Question 7

What are the main system components and how do they communicate?

Accepted Answer

The main components include the Rerouting Engine, Rule Manager, and Logging Service. The Rerouting Engine intercepts and redirects email, the Rule Manager processes routing rules, and the Logging Service records system events. These components communicate through internal z/OS mechanisms.

Question 8

What databases or storage mechanisms are used, and what are the network requirements?

Accepted Answer

OV/RerRouter uses configuration files stored on z/OS datasets. These files contain the routing rules and system settings. There are no specific port requirements, as the product operates within the z/OS environment using internal communication mechanisms.

Question 9

What is the business value of using OV/RerRouter?

Accepted Answer

OV/RerRouter streamlines email management within OfficeVision MVS environments, ensuring efficient message delivery and compliance with organizational policies. It reduces manual intervention and minimizes the risk of email delivery failures. The product's automation capabilities improve operational efficiency.

Question 10

How does OV/RerRouter improve operational efficiency and reduce costs?

Accepted Answer

By automating email rerouting, OV/RerRouter reduces the workload on IT staff, allowing them to focus on other critical tasks. The product's ability to handle complex routing scenarios minimizes the need for manual intervention, saving time and resources. This leads to improved productivity.

Question 11

How does OV/RerRouter support compliance and governance?

Accepted Answer

OV/RerRouter helps organizations maintain compliance by ensuring that email messages are routed according to established policies. It provides a reliable mechanism for enforcing routing rules, which is essential for regulatory requirements and internal governance. This enhances compliance efforts.

Question 12

How does OV/RerRouter support business agility?

Accepted Answer

The product's ability to handle complex routing scenarios allows organizations to adapt quickly to changing business needs. It provides the flexibility to modify routing rules as required, ensuring that email communication remains effective. This adaptability supports business agility.

Question 13

What authentication methods are supported?

Accepted Answer

OV/RerRouter does not support specific authentication methods. Access to the product is controlled through z/OS security mechanisms, such as RACF or similar security products. These systems manage user authentication and authorization.

Question 14

What access control model is used?

Accepted Answer

Access control is managed through the z/OS security system, such as RACF. This allows administrators to define user permissions and restrict access to specific functions and resources. The security model is based on the underlying z/OS security infrastructure.

Question 15

What encryption is used and where?

Accepted Answer

The product does not provide built-in encryption. Security relies on the underlying z/OS security features and any encryption implemented at the network or email server level. Data is protected by the security measures of the z/OS environment.

Question 16

What audit/logging capabilities exist?

Accepted Answer

OV/RerRouter integrates with z/OS logging facilities, providing audit trails of system events and administrative actions. These logs can be used to monitor system activity and identify potential security issues. The logging capabilities are integrated with the z/OS audit mechanisms.

Question 17

What administrative interfaces are available?

Accepted Answer

The primary administrative interface is the command-line interface (CLI). Administrators use specific commands to manage routing rules, start and stop the rerouting engine, and monitor system status. The CLI provides direct control over the product's functions.

Question 18

How is user management handled?

Accepted Answer

User management is handled through the z/OS security system, such as RACF. Administrators define user access and permissions within the z/OS environment. The product leverages the existing user management infrastructure of the operating system.

Question 19

What are the main configuration parameters?

Accepted Answer

Main configuration parameters include routing rules, sender and recipient addresses, and system settings. These parameters are stored in configuration files that can be modified using a z/OS editor. The configuration files control the product's behavior.

Question 20

What monitoring/logging capabilities exist?

Accepted Answer

OV/RerRouter provides logging capabilities through integration with z/OS logging facilities. Administrators can monitor system events, errors, and administrative actions. These logs are essential for troubleshooting and performance monitoring.

Are You a Vendor? Claim Your Listing

OV/RerRouter

Product Overview

Frequently Asked Questions