This section describes how to operate Symfoware Server.
There are two methods of managing Symfoware Server operations - select one that suits your purposes:
The Operation Guide describes the operating method using WebAdmin, and the equivalent operating method using the server commands.
Simple operation management using a web-based GUI tool (WebAdmin)
Suitable when using frequently used basic settings and operations for operation management.
This method allows you to perform simple daily tasks such as starting the system before beginning business, and stopping the system when business is over, using an intuitive operation.
Usage is started by using WebAdmin to create the instance.
By using an external scheduler and the pgx_dmpall command, periodic backups can be performed, which can then be used in recovery using WebAdmin.
Note
Do not use a server command other than pgx_dmpall or a server application. Operation modes that use server commands and server applications cannot be used in conjunction with WebAdmin. If used, WebAdmin will not be able to manage the instances correctly.
Refer to Reference and the PostgreSQL Documentation for information on server commands and server applications.
An instance that was created using WebAdmin can be set up to operate database multiplexing, however once the setup is complete, it will no longer be possible to select that instance from the WebAdmin management window. Refer to the Cluster Operation Guide for information on how to perform database multiplexing operations.
Advanced operation management using server commands
When operating in a system that is automated by operation management middleware (Systemwalker Centric Manager, for example), this method allows you to use more detailed settings and operations and perform higher level operation management.
An overview of the operating method using the GUI, and its relationship with the operating method using the server commands, are shown below.
Refer to the Operation Guide for details.
Operation | Operation with the GUI | Operation with commands | |
|---|---|---|---|
Setup | Creating an instance | WebAdmin is used. | The configuration file is edited directly using the initdb command. |
Changing the configuration files | WebAdmin is used. | The configuration file is edited directly. | |
Activating and stopping an instance | WebAdmin is used. | The pg_ctl command is used. | |
Creating a database | This is defined using pgAdmin of the GUI tool, or using the psql command or the application after specifying the DDL statement. | ||
Backing up the database | WebAdmin, or the pgx_dmpall command, is used. | It is recommended that the pgx_dmpall command be used. Recovery to the latest database can be performed. | |
Database recovery | WebAdmin is used. | To use the backup that was performed using the pgx_dmpall command, the pgx_rcvall command is used. | |
Monitoring | Database errors | The status in the WebAdmin window can be checked. (*1) | The messages that are output to the database server log are monitored (*1) |
Disk space | The status in the WebAdmin window can be checked. A warning will be displayed if the free space falls below 20%. (*1) | This is monitored using the df command of the operating system, for example. (*1) | |
Connection status | This can be checked using pgAdmin of the GUI tool, or referencing pg_stat_activity of the standard statistics view from psql or the application. | ||
*1: This can be used together with system log monitoring using operations management middleware (Systemwalker Centric Manager, for example).
See
Refer to "Periodic Operations" and "Actions when an Error Occurs" in the Operation Guide for information on monitoring and database recovery.
