What infrastructure is required?

IWS/WebAdmin runs on a Windows platform and connects to an IBM Workload Scheduler instance running on z/OS. It requires network connectivity between the Windows machine and the z/OS system. The IWS instance must be properly configured and accessible via the network.

Does this run in an LPAR?

IWS/WebAdmin is a Windows application that communicates with IBM Workload Scheduler on z/OS. It enhances the existing IWS installation by providing a GUI. It does not replace IWS but rather provides an alternative interface for managing it.

What protocols does it use for communication?

IWS/WebAdmin typically communicates with the IBM Workload Scheduler via TCP/IP. The specific ports used for communication need to be configured in both IWS/WebAdmin and the IWS instance on z/OS. The communication protocol is proprietary to IBM Workload Scheduler.

What are the most common operations users perform?

IWS/WebAdmin provides a graphical interface for managing IWS objects such as jobs, job streams, calendars, and resources. Users can define, schedule, monitor, and control these objects through the GUI, which simplifies the overall workload management process.

What is the business value of using IWS/WebAdmin?

IWS/WebAdmin enhances the business value of IBM Workload Scheduler by providing a more accessible and user-friendly interface. This can lead to improved efficiency, reduced training costs, and faster response times for workload management tasks. It also reduces the reliance on specialized mainframe skills for basic IWS operations.

How does IWS/WebAdmin improve user productivity?

By providing a Windows-based GUI, IWS/WebAdmin can reduce the learning curve for new IWS users. This can lead to faster onboarding and improved productivity. The GUI also simplifies complex tasks, making them more accessible to a wider range of users.

Can IWS/WebAdmin help reduce operational costs?

IWS/WebAdmin can help reduce operational costs by streamlining workload management tasks and reducing the need for specialized mainframe skills. The GUI simplifies monitoring and control, allowing operators to quickly identify and resolve issues. This can lead to improved service levels and reduced downtime.

How does IWS/WebAdmin handle security?

IWS/WebAdmin leverages the security features of IBM Workload Scheduler on z/OS. User authentication and authorization are typically handled by IWS, and IWS/WebAdmin integrates with these mechanisms. Access control is based on the roles and permissions defined within IWS.

What authentication methods are supported?

IWS/WebAdmin typically supports authentication methods configured within IBM Workload Scheduler, which may include RACF, ACF2, or Top Secret. The specific methods supported depend on the IWS configuration on z/OS.

What access control model is used?

IWS/WebAdmin uses the access control model defined within IBM Workload Scheduler. This is typically a role-based access control (RBAC) model, where users are assigned roles with specific permissions to access and manage IWS objects.

What are the ongoing operational requirements?

Ongoing operational requirements for IWS/WebAdmin include monitoring the application's availability and performance, ensuring network connectivity to the IWS instance on z/OS, and managing user access. Regular maintenance and updates of the Windows operating system and IWS/WebAdmin software are also necessary.

What monitoring/logging capabilities exist?

IWS/WebAdmin provides logging capabilities that can be used to monitor user activity and troubleshoot issues. These logs can be configured to capture various events, such as user logins, object modifications, and error messages. The logs can be analyzed to identify potential security threats or performance bottlenecks.

What are common implementation challenges?

Common implementation challenges for IWS/WebAdmin include ensuring proper network connectivity between the Windows machine and the z/OS system, configuring the IWS instance to allow access from IWS/WebAdmin, and managing user authentication and authorization. Compatibility issues between different versions of IWS/WebAdmin and IWS can also arise.

Share Your Product Experience

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

Share Your Experience

IWS/WebAdmin

HORIZONT Active z/OS

Legacy Application/Data Access Batch Automation

Vendor

HORIZONT

Product Overview

IWS/WebAdmin provides a Windows-based GUI for managing IBM Workload Scheduler (IWS) on z/OS. It simplifies the interaction with IWS by offering a visual interface for job scheduling, monitoring, and control. The architecture consists of a Windows client that communicates with the IWS instance on z/OS via TCP/IP.

The main components include the GUI client, the communication layer, and the IWS server. The GUI client provides the user interface for managing IWS objects. The communication layer handles the exchange of data between the client and the server.

The IWS server is the core component of IBM Workload Scheduler, responsible for managing and executing batch jobs. IWS/WebAdmin leverages the security features of IWS, including authentication and authorization mechanisms. It supports role-based access control (RBAC), allowing administrators to define granular permissions for users.

The application provides logging capabilities for monitoring user activity and troubleshooting issues. Alternatives include the Dynamic Workload Console (DWC), but IWS/WebAdmin offers a focused and streamlined approach.

Frequently Asked Questions

What does IWS/WebAdmin do?

IWS/WebAdmin provides a Windows-based graphical user interface for managing and interacting with IBM Workload Scheduler (IWS) on z/OS. It simplifies job scheduling, monitoring, and control by offering a user-friendly alternative to command-line interfaces. The product enhances the accessibility and efficiency of workload management for IWS users.

Is this a system, application, or tool?

IWS/WebAdmin is an application that enhances an existing system (IBM Workload Scheduler). It provides a graphical interface to simplify the management and monitoring of batch jobs and automated processes managed by IWS. It is not a standalone system but rather a tool that extends the functionality of IWS.

What types of organizations use this?

Organizations that rely on IBM Workload Scheduler for their batch processing and job scheduling on z/OS are the primary users of IWS/WebAdmin. These organizations typically include enterprises in industries such as finance, banking, insurance, and retail, where efficient and reliable workload management is critical.

When should we consider IWS/WebAdmin?

A company should consider using IWS/WebAdmin when they want to provide their IWS operators and administrators with a more intuitive and user-friendly interface. It is particularly useful when the existing command-line interface is proving to be cumbersome or inefficient, or when training new users on IWS.

What are the alternatives to IWS/WebAdmin?

Alternatives to IWS/WebAdmin include other GUI-based interfaces for IBM Workload Scheduler, such as the Dynamic Workload Console (DWC), or using the command-line interface directly. Other workload automation solutions might also be considered, depending on the specific requirements and environment.

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

Are You a Vendor? Claim Your Listing

Take control of your product listings. Add verified information, showcase updates, and unlock a Claimed Vendor badge across the directory.

Claim Your Listing Now

Share Your Product Experience

IWS/WebAdmin

Product Overview

Frequently Asked Questions

What does IWS/WebAdmin do?

Is this a system, application, or tool?

What types of organizations use this?

When should we consider IWS/WebAdmin?

What are the alternatives to IWS/WebAdmin?

What infrastructure is required?

Does this run in an LPAR?

What protocols does it use for communication?

What are the most common operations users perform?

What is the business value of using IWS/WebAdmin?

How does IWS/WebAdmin improve user productivity?

Can IWS/WebAdmin help reduce operational costs?

How does IWS/WebAdmin handle security?

What authentication methods are supported?

What access control model is used?

What are the ongoing operational requirements?

What monitoring/logging capabilities exist?

What are common implementation challenges?

Related Products

More from HORIZONT

DSN/Change

IWS/Audit

IWS/BatchAD

IWS/BatchCP

IWS/Graph

ProcMan

Similar Products

_beta access monitor

$avers

ABARS/Assist

ACC

ACO SolutionPac

Adabas SQL Gateway

Help Improve This Directory

Are You a Vendor? Claim Your Listing