https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/index.html Recent content in 4. Designing and Building Your Operation on JP1 Cloud Service/Operations Integration User's Guide Hugo -- gohugo.io en https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/design_pre/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/design_pre/index.html This section describes the prerequisite knowledge. Section structure 4.1.1 Associations between functions & required knowledge 4.1.2 Precautions when defining YAML files https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/required/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/required/index.html This section describes how to organize tasks. Section structure 4.2.1 Identifying routine/as-needed tasks 4.2.2 User management 4.2.3 Skills required for operation 4.2.4 Organizing handled documents https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/work_design/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/work_design/index.html After organizing the tasks in “Organizing tasks”, consider the scope for those tasks and how to implement them with Ops I. This section describes the detailed design perspectives required to implement the tasks with Ops I, including the data model, workflow, and document storage. (Table) List of task design Item Design items Designing a service catalog ・Catalog Designing a workflow ・Workflow Designing notifications ・Notification ・Notifier Storing documents ・Attachment ・Distribution Users and ACL ・User https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/uidesign/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/uidesign/index.html UI design involves definitions in the UI and Script YAML files. UI YAML files are available for UI versions 1.0 and 1.1 and it is recommended that you use UI version 1.1 when creating a new UI. For details on the UI versions, see “UI version”. For information on the function to define UI URLs (Uipath), see “Defining window URL (Uipath)”. Some scripts are written in JavaScript. For details, see “Script”. https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/tips/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/tips/index.html This section provides other tips on operational design. Section structure 4.5.1 Library 4.5.2 Application 4.5.3 Customizing the ticket window 4.5.4 Customizing the workflow window 4.5.5 Customizing the default YAML files https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/reg_step/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/reg_step/index.html YAML files developed through the operational design described above take effect only after they are registered in GitLab. This chapter describes the procedure for registering developed YAML files in GitLab, following the flow of the development process. Section structure 4.6.1 Process from YAML file code development to actual operation 4.6.2 Uploading YAML files https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/reg_sequence/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/reg_sequence/index.html This section describes a series of steps for registering YAML files and setting up AWX for processing that involves the automation functions. When the example workflow definition used in this section is launched from the service catalog window, the workflow is completed by executing the Playbook that outputs a message to the web browser in the background. The setup procedure is as follows. (Table) Flow of YAML file registration and AWX settings https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/outpost_step/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/outpost_step/index.html The following procedure assumes that the relay server is already configured. For more information on relay server settings, see “Setting a relay server”. When using a relay server, follow Steps ① to ⑥ below. Perform Steps ① to ③ in System Management and Steps ④ to ⑥ in the automation application (AWX). Step ⑦ describes what to specify in the workflow YAML file. Users who perform Steps ① to ③ must be granted the Primitive role “automation_manager”. https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/integration_template/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/integration_template/index.html The linkage templates allow Ops I to be linked with the following products. (Table) Linked products, version, and OS Product name Version OS JP1/AJS3 V11-00 or later Windows JP1/IM With linkage with the JP1/AJS3 job management function, JP1/AJS3 jobs can be executed from Ops I. With linkage with the JP1/IM system management function, JP1/IM event monitoring can be controlled from Ops I. In addition, when an incident occurs in JP1/IM, a ticket is automatically registered in Ops I. https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/awxee_extension/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/awxee_extension/index.html In order to achieve automation using additional modules including the Ansible collections and Python modules, or additional tools including the AWS CLI and OpenTofu, the execution environment provided by Ops I must be extended. A user-extended execution environment is referred to here as a custom execution environment. The execution environment is created and managed by the Git application (GitLab). In addition, the automation is executed by the automation application (AWX). https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/ai_agent/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/ai_agent/index.html By collaborating with your AI agent in Ops I, you can efficiently manage tickets and create or edit Ops I definitions. To collaborate with Ops I, AI agents can use the Ops I MCP server. The MCP server for Ops I is referred to here as the “MCP server”. First, configure the connection settings. Afterward, when a user enters a prompt into the AI agent, the AI agent executes the appropriate tools on the MCP server as needed.