5.3 Actions required when upgrading Ops I version

The following tasks need to be performed in conjunction with the Ops I upgrade.

(Table) Tasks required when upgrading Ops I

Item Conditions requiring action
Preserving the customized ticket function When upgrading from v2.5 to v2.7, or from v2.7 to later versions
Changing the ticket notification function When upgrading from v2.5 to v2.7 or later
  • If you want to change the notification function from the notification function using the mail server set in v2.5 to the notification function in Ops I
Updating the AWX execution environment When upgrading from v2.5 to v2.7 or later


[Changing the ticket notification function]

Ops I provides the following ticket notification functions.

  • Ops I notification function: Supported in Ops I version 2.7 and later
  • Notification function using mail server: Supported in Ops I version 2.0 and later

For details, see “Ticket notification function”.

The following actions are required when upgrading Ops I.

(Table) Ticket notification tasks to be performed when introducing or upgrading Ops I

Ops I version Action
When upgrading from v2.5 to v2.7 If notification settings are not configured in v2.5, the Ops I notification function will be set automatically. If you have configured the notification function using a mail server in v2.5, those settings will remain unchanged. Additional tasks are required only if you wish to change the notification settings.

For details on setting the notification method, see “Use Cases > Use cases for notifications and email-based ticket creation” in the “JP1 Cloud Service/Operations Integration User’s Guide (ITSM Operation Manual)”.

Section structure

5.3.1 Preserving the customized ticket function
5.3.2 Updating the AWX execution environment