Top
Symfoware Server V12.1.0 Operation Guide
FUJITSU Software

7.3.3 Changing PL/extJava

This section explains how to change PL/extJava.

7.3.3.1 Adding or Deleting Server Instances (Java VM)

This section explains how to add or delete a server instance (Java VM).

A server instance (Java VM) is a single Java VM. Up to 64 Java applications can be executed simultaneously on a single server instance (Java VM).

The number of Java applications that can be executed simultaneously can be extended by adding server instances (Java VM). To decrease the number of Java applications that are executed simultaneously, delete the server instances (Java VM) that were added.

  1. Stop the instance

    Refer to "2.1 Starting and Stopping an Instance" for information on how to stop the instance.

    Refer to "8.11 Actions in Response to Failure to Stop an Instance" if the instance fails to stop.

  2. Change the database cluster configuration

    Change the maximum number of simultaneous instance connections (max_connections).

    Refer to "7.2.3.1 Configuring Database Clusters" for information on how to change the number of simultaneous connections.

  3. Add or delete the server instance (Java VM)

    Add or delete the server instance (Java VM) using the add-instance subcommand or the delete-instance subcommand of the pgx_jadmin command.

    Example

    Add a server instance (Java VM)

    > pgx_jadmin add-instance --dbname db01 --instanceport 26801,26802

    Delete a server instance (Java VM)

    > pgx_jadmin delete-instance --dbname db01

    See

    Refer to "pgx_jadmin" in the Reference for information on the add-instance and delete-instance subcommands.

  4. Start the instance again

    Refer to "2.1 Starting and Stopping an Instance" for information on how to start the instance.

    Refer to "8.10 Actions in Response to Instance Startup Failure" if the instance fails to start.

7.3.3.2 Changing the Database Connection Information

This section explains how to change database connection information.

  1. Stop the instance

    Refer to "2.1 Starting and Stopping an Instance" for information on how to stop the instance.

    Refer to "8.11 Actions in Response to Failure to Stop an Instance" if the instance fails to stop.

  2. Change the database connection information

    Use the modify-container-db subcommand of the pgx_jadmin command to change the database connection information.

    You can change the following database connection information:

    • Instance port number

    • User name used for database connection

    • User password used for database connection

    Example

    If changing the name of the user connecting to the database to "user02"

    > pgx_jadmin modify-container-db --dbname db01 --dbuser user02

    See

    Refer to "pgx_jadmin" in the Reference for information on the modify-container-db subcommand.

  3. Start the instance again

    After changing the instance connection information, start the instance.

    Refer to "2.1 Starting and Stopping an Instance" for information on how to start the instance.

    Refer to "8.10 Actions in Response to Instance Startup Failure" if the instance fails to start.

7.3.3.3 Changing Port Numbers

This section explains how to change the domain management port numbers, or the port numbers for managing a server instance (Java VM).

Changing the domain management port numbers

  1. Stop the instance

    Refer to "2.1 Starting and Stopping an Instance" for information on how to stop the instance.

    Refer to "8.11 Actions in Response to Failure to Stop an Instance" if the instance fails to stop.

  2. Check the port numbers before they are changed

    Use the list-domain subcommand of the pgx_jadmin command to check the port numbers before they are changed.

    Example

    > pgx_jadmin list-domain

    See

    Refer to "pgx_jadmin" in the Reference for information on the list-domain subcommand.

  3. Change the domain management port numbers

    Use the modify-domain-port subcommand of the pgx_jadmin command to change the port numbers.

    Example

    If changing the domain management port numbers to "26600,26601,26602"

    > pgx_jadmin modify-domain-port --domainport 26600,26601,26602

    See

    Refer to "pgx_jadmin" in the Reference for information on the modify-domain-port subcommand.

  4. Check the port numbers after changing them

    Use the list-domain subcommand of the pgx_jadmin command to check that the port numbers were changed.

  5. Start the instance again

    Refer to "2.1 Starting and Stopping an Instance" for information on how to start the instance.

    Refer to "8.10 Actions in Response to Instance Startup Failure" if the instance fails to start.

Changing the server instance (Java VM) management port numbers

  1. Stop the instance

    Refer to "2.1 Starting and Stopping an Instance" for information on how to stop the instance.

    Refer to "8.11 Actions in Response to Failure to Stop an Instance" if the instance fails to stop.

  2. Check the port numbers before they are changed

    Use the list-container subcommand of the pgx_jadmin command to check the port numbers before they are changed.

    Example

    > pgx_jadmin list-container --dbname db1

    See

    Refer to "pgx_jadmin" in the Reference for information on the list-container subcommand.

  3. Change the server instance (Java VM) management port numbers

    Use the modify-instance-port subcommand of the pgx_jadmin command to change the port numbers.

    Example

    To change the server instance (Java VM) management port numbers to "26701,26702"

    > pgx_jadmin modify-instance-port --instance db1-1 --instanceport 26701,26702

    See

    Refer to "pgx_jadmin" in the Reference for information on the modify-instance-port subcommand.

  4. Check the port numbers after changing them

    Use the list-container subcommand of the pgx_jadmin command to check that the port numbers were changed.

  5. Start the instance again

    Refer to "2.1 Starting and Stopping an Instance" for information on how to start the instance.

    Refer to "8.10 Actions in Response to Instance Startup Failure" if the instance fails to start.