Details of Modification
The default value of the data disk name during application to use an L-Platform has been changed.
For V3.1.2 (T009379LP-05/T009378WP-06)
When making an application for L-Platform usage, the default values for disk names of data disks defined in L-Platform templates are automatically set as "DISK+serial number".
The serial number is a sequential number, starting from 0.
For V3.2.0
The default values for disk names when making an application for L-Platform usage are the values (*) set in the L-Platform template.
* Note: In L-Platform templates, the setting is "DISK+serial number". The serial number is a sequential number, starting from 1.
Effect
The default value of the data disk name during application to use an L-Platform is changed.
Corrective Action
No action is required.
Details of Modification
Setup and unsetup of the manager has been removed.
Setup of the manager is performed during installation. In addition, unsetup of the manager is performed during uninstallation.
Corrective Action
When there are descriptions of setup and unsetup in the setup guide of a system that has been created by a customer, it is necessary to revise the setup guide.
Details of Modification
The window displayed during upgrade installation from Cloud Edition manager has been changed to an interactive style that uses the command prompt.
Corrective Action
To perform upgrade installation, follow the instructions displayed by the installer. Do not exit the command prompt until installation is complete.
When there are descriptions of upgrade installation in the setup guide of a system that has been created by a customer, it is necessary to revise the setup guide.
Details of Modification
Installation of the dashboard development environment used for dashboard customization is no longer necessary. Dashboard customization is now available using the operation management console of Interstage Business Process Manager Analytics accessible via the network.
Effect
Use of the dashboard development environment is no longer possible.
Corrective Action
No action is required.
Details of Modification
The methods of starting, stopping, and confirming the agent (Cloud Edition Dashboard Function) have changed.
For V3.1.2 (T009379LP-05/T009378WP-06)
Windows
Starting the Agent (Cloud Edition Dashboard Function)
Open [Services] from [Administrative Tools] on the Control Panel and then start the "Systemwalker SQC DCM" service.
Stopping the Agent (Cloud Edition Dashboard Function)
Open [Services] from [Administrative Tools] on the Control Panel and then stop the "Systemwalker SQC DCM" service.
Confirming the Agent (Cloud Edition Dashboard Function)
Open [Services] from [Administrative Tools] on the Control Panel and then check the status of the "Systemwalker SQC DCM" service.
Linux
Starting the Agent (Cloud Edition Dashboard Function)
# /etc/rc2.d/S99ssqcdcm start <RETURN> |
Stopping the Agent (Cloud Edition Dashboard Function)
# /etc/rc2.d/K00ssqcdcm stop <RETURN> |
Confirming the Agent (Cloud Edition Dashboard Function)
# /etc/rc2.d/K00ssqcdcm <RETURN> |
For V3.2.0
Windows
Starting the Agent (Cloud Edition Dashboard Function)
Open [Services] from [Administrative Tools] on the Control Panel and then start the "ServerView Resource Orchestrator SQC DCM" service.
Stopping the Agent (Cloud Edition Dashboard Function)
Open [Services] from [Administrative Tools] on the Control Panel and then stop the "ServerView Resource Orchestrator SQC DCM" service.
Confirming the Agent (Cloud Edition Dashboard Function)
Open [Services] from [Administrative Tools] on the Control Panel and then check the status of the "ServerView Resource Orchestrator SQC DCM" service.
Linux
Starting the Agent (Cloud Edition Dashboard Function)
# /etc/rc2.d/S99FJSVctdsb-sqcdcm start <RETURN> |
Stopping the Agent (Cloud Edition Dashboard Function)
# /etc/rc2.d/K00FJSVctdsb-sqcdcm stop <RETURN> |
Confirming the Agent (Cloud Edition Dashboard Function)
# /etc/rc2.d/ K00FJSVctdsb-sqcdcm <RETURN> |
Corrective Action
No action is required.
Details of Modification
The message contents and error numbers output when the following errors have occurred during VDI coordination have changed.
When connection to the Active Directory failed
When a user not existing in the Active Directory is specified as the VDI user
When a group name not existing in the Active Directory is specified using the group qualification definition file
When the NetBIOS domain of the VDI user is not valid
For V3.1.2 (T009379LP-05/T009378WP-06)
When the above error conditions are met, the following messages and error numbers are output.
The dialog message displayed when subscribing to an L-Platform
The specified VDI user is invalid.
Check the VDI user setting.
Error message
FJSVrcx:ERROR:67390:creating VM guest failed. detail=(validate_user:failed to query Active Directory,vmerrno=861,ip={IP address})
For V3.2.0
The following error message and error number is output for each cause of detected Active Directory errors.
When connection to the Active Directory failed
The dialog message displayed when subscribing to an L-Platform
When registering the deployment, an error occurred.
Tenant ID: [Tenant ID]
Error code: VSYS10096
Please contact your system administrator.
Error message
FJSVrcx:ERROR:67390:creating VM guest failed. detail=(validate_user:failed to query Active Directory,vmerrno=861,ip={IP address})
When a user not existing in the Active Directory is specified as the VDI user
The dialog message displayed when subscribing to an L-Platform
One or more specified VDI user name is not valid.
Please check VDI user names.
Error message
FJSVrcx:ERROR:67390:creating VM guest failed. detail=(validate_user:invalid user name,vmerrno=873,ip={IP address})
When a group name not existing in the Active Directory is specified using the group qualification definition file
The dialog message displayed when subscribing to an L-Platform
When registering the deployment, an error occurred.
Tenant ID: [Tenant ID]
Error code: VSYS10096
Please contact your system administrator.
Error message
FJSVrcx:ERROR:67390:creating VM guest failed. detail=(validate_user:invalid group name,vmerrno=874,ip={IP address})
When the NetBIOS domain of the VDI user is not valid
The dialog message displayed when subscribing to an L-Platform
The NetBIOS Domain of one or more VDI users is not valid.
Please check the NetBIOS Domain.
Error message
FJSVrcx:ERROR:67390:creating VM guest failed. detail=(validate_user:invalid domain name,vmerrno=875,ip={IP address})
Corrective Action
When monitoring the corresponding messages output by Resource Orchestrator using other monitoring software, it is necessary to change the monitored messages. When the messages before modification are described in the operation guide of a system created by a customer, it is necessary to revise the operation guide.
Details of Modification
The display location of the Route Search box in the Utility Panel has been changed.
For V3.1.2 (T009379LP-05/T009378WP-06)
The Route Search box is displayed in the route information box in the Utility Panel.
For V3.2.0
The Route Search box is displayed in the Filter box when the [Custom View] tab of the Utility Panel is selected.
It is displayed only when "Route" is checked in the filter setting window.
Corrective Action
No action is required.
Details of Modification
The window displayed during route searches has been changed.
For V3.1.2 (T009379LP-05/T009378WP-06)
During route search, "Route filter..." is displayed in the upper part of the network view.
In addition, the [Cancel] button is also displayed in the upper part of the network view. Clicking the [Cancel] button cancels the route search settings.
While the route search is being performed, the [Clear] button in the route search box is disabled and cannot be clicked.
For V3.2.0
During route searches, neither "Route filter..." nor the [Cancel] button are displayed in the upper part of the network view.
Route search settings can be canceled by clicking the [Clear] button in the route search box or closing the route search box.
Corrective Action
No action is required.
Details of Modification
The "Only error and the warning links are displayed." checkbox has been deleted.
For V3.1.2 (T009379LP-05/T009378WP-06)
The "Only error and the warning links are displayed." checkbox is displayed on the toolbar.
For V3.2.0
The "Only error and the warning links are displayed." checkbox is not displayed on the toolbar.
The similar display is possible by selecting "error/warning" for the filter condition when "Link Status" (*1) is selected in the Filter box.
*1: This is displayed in the filter box when the [Custom View] tab is selected in the Utility Panel. This is displayed only when "Link Status" is checked when setting the filter items.
Corrective Action
No action is required.
Details of Modification
Functions operable from the control box and their display locations have been changed.
For V3.1.2 (T009379LP-05/T009378WP-06)
The control box is displayed in the Utility Panel. In the control box, the following items are displayed:
The magnification slider
The [Display initialization] button
[Move] Button
For V3.2.0
The control box is no longer available. The functions that were displayed in the control box are now in the following locations:
The magnification slider and the [Display initialization] button
They are now located at the bottom right of the network view window.
[Move] Button
It has been deleted.
Corrective Action
No action is required.
Details of Modification
The following paths have been changed.
V3.2.0 | V3.1.2 (T009379LP-05/T009378WP-06) |
|---|---|
Installation_folder\CMDB | Installation_folder\SWRBAM\CMDB |
Installation_folder\IAPS\ahs\servers\RCXCT-ext | Installation_folder\IAPS\F3FMihs\servers\FJapache |
Installation_folder\IJEE\nodes\localhost-domain1\CTSV_IBPMMServer | Installation_folder\J2EE\ijserver\IBPMMServer\apps\ibpmm.war |
Installation_folder\IJEE\domain1\applications\ibpmm |
V3.2.0 | V3.1.2 (T009379LP-05/T009378WP-06) |
|---|---|
/opt/FJSVctdsb-cmdb/CMDB/FJSVcmdbm | /opt/FJSVcmdbm |
/var/opt/FJSVCctmg-isas/ahs/servers/RCXCT-ext | /var/opt/FJSVihs/servers/FJapache |
/opt/FJSVctmg-ibpm | /opt/FJSVibpm |
/var/opt/FJSVctmg-isas/fjje6/nodes/localhost-domain1/CTSV_IBPMMServer/applications/ibpmm | /var/opt/FJSVj2ee/deployment/ijserver/IBPMMServer/apps/ibpmm.war |
/var/opt/FJSVctmg-isas/fjje6/domains/domain1/applications/ibpmm |
Corrective Action
Commands and file operations that use the paths to be changed should only be performed after the paths have been changed.
Details of Modification
Due to changes in port numbers, the following ports are now also used.
2511
2512
13200
13201
41320
23851 - 23878
The following port number is now used for communication with the admin client when performing a fresh installation of Resource Orchestrator.
3502
The following port number is still used when performing an upgrade installation of Resource Orchestrator. A strengthened check is used to ensure that it is not allocated for use by another service in the "services" file.
80
Corrective Action
When performing a fresh installation, change the settings of your firewall to enable port number 3502 to be used for communication with the admin client.
Before installing Resource Orchestrator, check the other used port numbers using the configuration requirements check tool, and change any other port numbers if necessary.
When performing an upgrade installation, check that port number 80 is not listed in the "services" file. If it is listed, perform the following operation before starting the upgrade installation.
Disable any services in the "services" file that use port 80.
Details of Modification
To enable operation of other products that use the same functions of services on the same server, the following service names have been changed.
V3.2.0 | V3.1.2 (T009379LP-05/T009378WP-06) |
|---|---|
ServerView Resource Orchestrator Service Catalog Manager DB Service (IBPMF) | Systemwalker Runbook Automation DB Service |
ServerView Resource Orchestrator BPM Analytics eRule Engine | Interstage BPM Analytics eRule Engine |
ServerView Resource Orchestrator SQC DCM | Systemwalker SQC DCM |
SVRORHTTPServer(RCXCF-API) | Interstage HTTP Server(RCXCF-API) |
SVRORHTTPServer(RCXCF-VSYS) | Interstage HTTP Server(RCXCF-VSYS) |
SVRORHTTPServer(RCXCT-acnt) | Interstage HTTP Server(RCXCT-acnt) |
SVRORHTTPServer(RCXCT-ext) | Interstage HTTP Server(RCXCT-ext) |
SVRORHTTPServer(RCXCT-ext2) | Interstage HTTP Server(RCXCT-ext2) |
SVRORHTTPServer(RCXCT-int) | Interstage HTTP Server(RCXCT-int) |
V3.2.0 | V3.1.2 (T009379LP-05/T009378WP-06) |
|---|---|
FJSVctdsb-sqcdcm | sqcdcm |
Corrective Action
No action is required.
In order to deal with a vulnerability of the manager, in comparison with V3.1.2, the time taken to start and stop the manager is longer.
It is dependent on the CPU performance of the server used for the admin server, but compared to V3.1.2 the time taken can be from 50 - 100% longer.
Corrective Action
When performing maintenance on the manager after it has been configured, confirm the time take to start and stop the manager, and then design the time to use for maintenance operations.
The time taken to start and stop the manager is affected by the CPU performance. Therefore, you are advised to secure CPU performance for the admin server in line with the following formula.
The value of CP clock rate * Number of sockets * CPU core count is over 8 GHz |
Details of Modification
Due to addition of a function in V3.2.0, the memory capacity necessary for operation of the manager has changed.
For V3.1.2 (T009379LP-05/T009378WP-06)
[Windows Manager]
6656 MB
[Linux Manager]
10,752 MB
For V3.2.0
[Windows Manager]
12,000 MB
[Linux Manager]
16,000 MB
Corrective Action
When the OS is Windows or Linux (for Intel64), add memory.
When the OS is Linux (for x86), as the maximum physical memory that the basic software can recognize is less than 16,000 MB, configure the system using Linux (for Intel64).
Linux (for x86) indicates the following OSs.
Red Hat(R) Enterprise Linux(R) 5.3 (for x86)
Red Hat(R) Enterprise Linux(R) 5.4 (for x86)
Red Hat(R) Enterprise Linux(R) 5.5 (for x86)
Red Hat(R) Enterprise Linux(R) 5.6 (for x86)
Red Hat(R) Enterprise Linux(R) 5.7 (for x86)
Red Hat(R) Enterprise Linux(R) 5.8 (for x86)
Red Hat(R) Enterprise Linux(R) 5.9 (for x86)
Red Hat(R) Enterprise Linux(R) 5.10 (for x86)
Red Hat(R) Enterprise Linux(R) 5.11 (for x86)
Red Hat(R) Enterprise Linux(R) 6.2 (for x86)
Red Hat(R) Enterprise Linux(R) 6.3 (for x86)
Red Hat(R) Enterprise Linux(R) 6.4 (for x86)
Red Hat(R) Enterprise Linux(R) 6.5 (for x86)
Linux (for Intel64) indicates the following OSs.
Red Hat(R) Enterprise Linux(R) 5.3 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.4 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.5 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.6 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.7 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.8 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.9 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.10 (for Intel64)
Red Hat(R) Enterprise Linux(R) 5.11 (for Intel64)
Red Hat(R) Enterprise Linux(R) 6.2 (for Intel64)
Red Hat(R) Enterprise Linux(R) 6.3 (for Intel64)
Red Hat(R) Enterprise Linux(R) 6.4 (for Intel64)
Red Hat(R) Enterprise Linux(R) 6.5 (for Intel64)
