Appendix C Using WebAdmin After an Upgrade

The following steps are required if performing an upgrade installation in an environment in which WebAdmin is used.

Check the service name

When starting WebAdmin for the first time after an upgrade, the service name of the instance created in WebAdmin is changed to the post-upgrade version. Therefore, if you have a job that is using the service name, you need to change the service name to the post-upgrade version.

Example)

If the instance name "inst1" with the user name "symfo" was created in the Symfoware Server V12.0.0 Standard Edition 64-bit version, and the product is upgraded to V12.1.0:

[Service name of the instance created in WebAdmin]

Before upgrade: symfo_1200_SE_64_symfo_inst1

After upgrade: symfo_1210_SE_64_symfo_inst1

Change the settings information

1. Change the parameter file "postgresql.conf"

Change the following parameters in the "postgresql.conf" parameter file.

Change the "version" portion in the same manner as for the service name.

log_directory
core_directory
event_source

Example)

If the instance name "inst1" with the user name "symfo" was created in the Symfoware Server V12.0.0 Standard Edition 64-bit version, and the product is upgraded to V12.1.0:

[log_directory] [core_directory]

Before modification: C:\\Users\\symfo\\AppData\\Local\\Fujitsu\\symfo_1200_SE_64\\inst1\\log

After modification: C:\\Users\\symfo\\AppData\\Local\\Fujitsu\\symfo_1210_SE_64\\inst1\\log

[event_source]

Before modification: symfo_1200_SE_64_symfo_inst1

After modification: symfo_1210_SE_64_symfo_inst1

2. Change the services file instance name

Change the instance name of the services file.

Example)

If the instance name "inst1" with the user name "symfo" was created using the port number "26500" in the Symfoware Server V12.0.0 Standard Edition 64-bit version, and the product is upgraded to V12.1.0:

Directory for storing the services file: %SystemRoot%\system32\drivers\etc\services

Before modification: symfo_1200_SE_64_symfo_inst1 26500/tcp

After modification: symfo_1210_SE_64_symfo_inst1 26500/tcp

Creating directories for resource deployment

If the directory specified in "log_directory" and "core_directory" does not exist, create it.

Additionally, the directory access privileges must satisfy the following requirements:

The directory owner is the operating system user account that will become the instance administrator
There are permissions to write to the directory
The directory is empty

Note

If operations management middleware (for example, Systemwalker Centric Manager) is used to monitor instance ID information for the service name or server log, modify the operations management middleware settings together with these changes. If multiple methods were specified for the same table combination, the method specified last will be effective.