Network Settings for P6 Compression Server

You can configure the network settings for P6 Compression Server and the database server to function more efficiently in a multi-user setting. P6 Compression Server needs to communicate with P6 Professional clients and the database server concurrently, with as little network impediments as possible. For example, if the P6 Compression Server computer uses only one network interface card (NIC), a potential risk for switch collision could lead to poor performance. To avoid this risk, you can use at least two NICs for P6 Compression Server. One NIC should be used for the data transfer with P6 Professional clients and another NIC for the communication with the database server.

Note: One NIC might be sufficient for smaller deployments or databases.

To avoid unwanted routing, you can configure the NICs you are using for the P6 Professional clients and database on separate subnets. Also, the routing table should not have any entries configured for routes between the two NICs.

The following example shows one possible way to configure the network for P6 Compression Server. All configurations must meet the following two requirements:

The IP address of the second NIC should not be accessible from any other computer in the corporate network of the organization, except the DB server computer. This minimizes traffic on the second NIC and also ensures the fastest possible connection between P6 Compression Server and the database server. To achieve this, Oracle recommends that you use an IP address with a subnet not visible in the corporate network. In the following example, changing the IP address to 10.12.63.XX would make the second NIC visible only for the subnet 63.

Oracle recommends that the DB Server computer use a dedicated NIC for the P6 Compression Server connection. This connection will support the traffic of uncompressed data for all P6 Professional clients. If the expected traffic through this connection is low, then the DB Server computer can use one NIC with IP multiplexing. The routing table of the DB server should not have any entry configured for routes between the two NICs.

Note:

If the DB Server computer uses a dedicated NIC for the P6 Compression Server connection, the applications that need to connect directly to the database might have to use another NIC. To inform these applications about the fact that the parameters of the P6 Compression Server connection to Oracle cannot be used for direct connection, you have to add a new entry in the ADMIN_CONFIG table of the configuration database.

Note: This is only required if your database server is configured to support more than one network interface card (NIC) and uses an IP address that is not public.

To add a new entry in the ADMIN_CONFIG table:

  1. Using SQL*Plus, run the following SQL command on the database server:

    INSERT INTO ADMIN_CONFIG (CONFIG_NAME, CONFIG_TYPE, CONFIG_VALUE) VALUES('CompressionServerPublicConfig', 'CS.ORA', 'IP_ADDRESS:port_no:SID'); COMMIT;

    Where IP_ADDRESS:port_no is the database server’s public NIC IP address and port number, and SID is the SID of the database server.

  2. Run the following SQL command to delete the existing INTERNAL_PLUGINS configuration from the ADMIN_CONFIG TABLE.

    DELETE FROM ADMIN_CONFIG WHERE UPPER(CONFIG_NAME)= 'MYPRIMAVERA.BRE.INTERNAL_PLUGINS'; COMMIT;

    Note: This step is necessary only if the INTERNAL_PLUGINS configuration currently exists in the ADMIN_CONFIG TABLE.



Legal Notices
Copyright © 2005, 2017, Oracle and/or its affiliates. All rights reserved.

Last Published Tuesday, February 21, 2017