Macro 4 z/OS

Supermon for Java Modernization Guide

Java and WebApplication DevelopmentMonitor

Supermon for Java is a java and web product by Macro 4. Explore technical details, modernization strategies, and migration paths below.

Product Overview

Supermon for Java provides monitoring for Java applications running on z/OS, including WebSphere Application Server and CICS.

Common operations include using commands like `start_monitoring ` and `stop_monitoring `.

Modernization Strategies

Rehost

Timeline:
6-12 months

Lift-and-shift to cloud infrastructure with minimal code changes. Fast migration with lower risk.

Refactor (Recommended)

Timeline:
18-24 months

Optimize application architecture for cloud while preserving business logic. Best ROI long-term.

Replatform

Timeline:
3-5 years

Complete rewrite to cloud-native architecture with microservices and modern tech stack.

Frequently Asked Questions

General

What does Supermon for Java do?

Supermon for Java monitors Java applications running in environments like WebSphere Application Server and CICS. It provides real-time performance metrics, transaction tracing, and resource usage analysis.

What configuration files are used?

Supermon for Java uses configuration files, often XML-based, to define monitoring parameters, thresholds, and connection details for the target Java applications and environments. The administrative interface allows modification of these parameters.

How does Supermon for Java integrate with other systems?

Supermon for Java supports integration via APIs, often REST-based, to retrieve monitoring data and integrate with other systems. It communicates using protocols like HTTP/HTTPS.

What are the main components of Supermon for Java?

Supermon for Java's architecture includes components such as the data collector, the monitoring server, and the user interface. The data collector gathers metrics from the Java applications, the monitoring server processes and stores the data, and the user interface provides a view of the data.

Technical

What are common operations users perform?

Common operations include starting and stopping monitoring, configuring thresholds, viewing real-time metrics, and generating reports. For example, to start monitoring, the command might be 'start_monitoring '.

What types of APIs does Supermon for Java expose?

Supermon for Java exposes APIs, often RESTful, for data retrieval. An example endpoint pattern might be '/api/v1/metrics/{application_name}'. Integration is typically supported through Java SDKs and standard HTTP clients.

What are the main system components?

The main components include the Agent (data collector), the Server (data processing and storage), and the Console (user interface). The Agent sends data to the Server, which stores it in a database. The Console retrieves data from the Server.

What databases and network ports are used?

Supermon for Java uses a database to store monitoring data. The specific database can vary, but common choices include relational databases like DB2 or Oracle. It requires network ports for communication between components, typically including HTTP/HTTPS ports.

Business Value

What is the business value of Supermon for Java?

Supermon for Java provides real-time visibility into application performance, enabling faster problem resolution and reduced downtime. This leads to improved service levels and customer satisfaction.

How does Supermon for Java help reduce costs?

By identifying performance bottlenecks and resource constraints, Supermon for Java helps optimize application performance and resource utilization, leading to cost savings.

How does Supermon for Java support decision-making?

Supermon for Java's reporting capabilities provide insights into application behavior and trends, enabling data-driven decision-making and proactive problem prevention.

Security

What authentication methods are supported?

Supermon for Java supports authentication methods such as LDAP, and potentially SAML 2.0 for single sign-on. It employs an access control model based on roles, where users are assigned roles with specific permissions.

What encryption is used?

Supermon for Java uses encryption for sensitive data, both in transit (e.g., HTTPS) and at rest (e.g., encrypted database storage).

What audit/logging capabilities exist?

Supermon for Java provides audit logging of user actions and system events, enabling security monitoring and compliance reporting.

Operations

What administrative interfaces are available?

Supermon for Java provides a web-based administrative interface for configuration and management. User management is handled through the administrative interface, with options for creating users, assigning roles, and managing permissions.

What are the main configuration parameters?

Key configuration parameters include connection details for target Java applications, monitoring thresholds, reporting intervals, and security settings.

What monitoring/logging capabilities exist?

Supermon for Java offers monitoring dashboards, real-time alerts, and historical reporting. Logs are typically stored in standard formats and can be integrated with centralized logging systems.

Ready to Start Your Migration?

Download our comprehensive migration guide for Supermon for Java or calculate your ROI.

Calculate ROI