2.3 Functions for linking with other products

JP1/AO provides functions for improving the work efficiency of administrators, including email notifications when errors occur, a direct access URL that enables target windows to be displayed directly, and an API that calls JP1/AO functions from external programs.

Taking advantage of existing JP1 resource groups - linking with JP1/Base's authentication function

JP1/AO enables you to use JP1/Base's authentication function to manage JP1/AO's user accounts. If you link your JP1/AO with JP1/Base, there is no need to manage users and user groups in JP1/AO. You can also use the existing JP1 users.

To use JP1/Base to manage users, you use JP1/Base window operations to create JP1 users and to specify JP1 resource group names and permission levels. If you specify JP1 resource group names and permission levels that match the resource group names and permissions in JP1/AO, you can manage those users as JP1/AO users.

Figure 2‒5: Linking with JP1/Base's authentication function

Using Active Directory to manage users and groups - linking with Active Directory

Linking JP1/AO with Active Directory^# allows Active Directory to perform user authentication. In other words, Active Directory users can log in to JP1/AO.

To link JP1/AO with Active Directory, you can select whether to link groups.

If you do not link groups, JP1/AO manages user groups and resources and Active Directory performs user authentication. You need to register the same users in both JP1/AO and Active Directory, but register passwords only in Active Directory.

If you link groups, an Active Directory group that contains a user who logs in to JP1/AO must be registered as a JP1/AO user group. Then, Active Directory performs user authentication. Active Directory manages users in the groups, and JP1/AO manages resources for the groups. Therefore, there is no need to register a user in JP1/AO.

#

This linkage can be used if JP1/AO uses Active Directory as an LDAP directory server.

Figure 2‒6: Linkage with Active Directory (when linking groups)

System monitoring linked with JP1/IM - linking with JP1/IM's event monitoring function

JP1/IM achieves integrated system management by linking JP1-series products, including job management and storage management, and other middleware products, as well as managing the configuration and operation of the overall system.

The following features become available when you link your JP1/AO with JP1/IM:

• JP1 event linkage, which enables you to use JP1/IM to centrally manage the JP1 events issued by JP1/AO

• Monitoring-startup linkage, which enables you to define windows to be displayed in JP1/IM - View and then display the associated JP1/AO windows from JP1 events

• Tool Launcher linkage, which enables you to connect to the JP1/AO windows from JP1/IM - View

Figure 2‒7: Linking with JP1/IM's event monitoring function

Executing services and stopping tasks from JP1/AJS3 - linking with JP1/AJS3

Linking with JP1/AJS3 lets you automatically execute the following commands on the JP1/AO server from the JP1/AJS3 server:

• submittask command (executing services)

• stoptask command (stopping execution of tasks)

Figure 2‒8: Linking with JP1/AJS3

Streamlined error detection - email notification

If the status Abnormal Detection or Failed is detected in a task that is being processed, the event can be reported by email. Because the email that is sent can include the URL of the details window for the failed task, you can reduce the time required to handle the error once the email is received.

Figure 2‒9: Email notification

Improving work efficiency by directly accessing a target window - direct-access URL

JP1/AO provides the direct-access URL function that enables you to go directly to the target window as soon as you have logged in.

When you use the normal window transitions, it takes time to find the target from a list of services and tasks after you log in. By using the direct-access URL, you can display a service execution window, a service setup window, or a task details window immediately after you log in.

Figure 2‒10: Direct-access URL

Calling JP1/AO functions from external programs - API

You can use an API to call JP1/AO functions from an external program. For example, you can run services and stops tasks from an external program without using JP1/AO windows. The API uses the HTTP or HTTPS protocol for communication.

For details, see API in the manual Job Management Partner 1/Automatic Operation GUI, Command, and API Reference.

Figure 2‒11: API

Single sign-on to Hitachi Command Suite products - Link & Launch setting

You can start any Hitachi Command Suite product from a JP1/AO window with a single sign-on. This enables you to enter property values for a service that is running while checking a Hitachi Command Suite product's window. Note that the Hitachi Command Suite products that can be started from JP1/AO must be installed on the same server where JP1/AO is installed.

You can apply the Link & Launch function to the following products:

• Hitachi Device Manager Software

• Hitachi Tuning Manager Software

• Hitachi Global Link Manager Software

• Hitachi Replication Manager Software

• Hitachi Compute Systems Manager Software

Single sign-on to a JP1/IM - NP window - Linking with JP1/IM - NP job contents

You can start a JP1/IM - NP window from a JP1/AO window with a single sign-on. In the Respond dialog box, you can view the JP1/IM - NP job contents (business flow and guide) to check workflow and operation procedures.

Figure 2‒12: Linking with the JP1/IM - NP job contents

To Page Top