Oracle Portal-to-Go Configuration Guide Release 1.0.2.2 A86634-02 |
|  | Library | Service

# Oracle Portal-to-Go

Configuration Guide

Release 1.0.2.2

November 2000

Part No. A86634-02

This document provides instructions for configuring parameters for Portal-to-Go. It describes the parameters that should be modified for the system, the Web server, and Portal-to-Go to achieve the best performance and scalability.

Topics include:

- Portal-to-Go Core

- Kernel Parameters

- TCP Parameters

- Mod_JServ Configuration

- Configuring Web Integration Server and Web Integration Developer

- Oracle 8.1.5 and 8.1.6 Configuration

- JDK

##### Portal-to-Go Core

This section addresses the following topics regarding the Portal-to-Go core:

- Portal-to-Go Core Configuration Parameters

- PAoid

##### Portal-to-Go Core Configuration Parameters

The following is a set of runtime tunable parameters for Portal-to-Go. The parameters apply to both Solaris and Windows NT installations.

Name | Default Value | Description
--- | --- | ---
db.driver | THIN | The JDBC driver uses the core to access the Portal-to-Go repository.
db.connect.minConnections | 5 | Specifies the minimum number of connections for the connection pool.
db.connect.maxConnections | 100 | Specifies the maximum number of connections for the connection pool.
db.connect.incConnections | 1 | Indicates new connections to the connection pool.
db.connect.idleTimeout | 360 | Defines the maximum idle time (in minutes) before the unused connections are closed.
repository.session.check.interval | 1 | Indicates the time interval (in seconds) for the watchdog to find and release unused connections to the connection pool.
transformer.poolsize | 10 | Specifies the number of XML transformers in the pool. The pool size should be around 1.5 times the number of CPUs.

##### PAoid

Use PAoid to refer to a service instead of using PAservicepath. Using PAoid improves the performance. With PAoid, the reference remains the same even if the service has been moved.

For example, as in the following, Approach 2 is faster than Approach 1.

- Approach 1:

      <xsl:attribute

      name="target">

      ___REQUEST_NAME__?PAservicepath=___SERVICE_URL_ENC__&#38;

      PAsection=Detail&#38;

      s2=<xsl:value-of select="symbol">

      </xsl:value-of>

      </xsl:attribute>

- Approach 2:

      <xsl:attribute

      name="target">

      ___REQUEST_NAME__?PAoid=__PAoid__&#38;

      PAsection=Detail&#38;

      s2=<xsl:value-of select="symbol">

      </xsl:value-of>

      </xsl:attribute>

Note: There are two underscores ("_") before and after PAoid. There are three underscores ("_") before REQUEST_NAME and two after it.

##### Kernel Parameters

Note: Kernel parameter modifications apply to Solaris systems only.

It is recommended that you modify the following kernel parameters in the /etc/system file:

Name | Value
--- | ---
priority_paging | 1
rlim_fd_max | 8192
rlim_fd_cur | 2048
lwp_default_stksize | 0x4000
rpcmod:svc_run_stksize | 0x4000
tcp:tcp_conn_hash_size | 262144
sq_max_size | 1600

##### TCP Parameters

The following TCP parameters should be modified through the ndd command:

Name | Value
--- | ---
tcp_rexmit_interval_initial | 3000
tcp_rexmit_interval_min | 3000
tcp_rexmit_interval_max | 10000
tcp_ip_abort_interval | 60000
tcp_ip_abort_cinterval | 60000
tcp_keepalive_interval | 120000
tcp_fin_wait_2_flush_interval | 16000
tcp_conn_req_max_q | 10240
tcp_conn_req_max_q0 | 10240
tcp_xmit_hiwat | 65536
tcp_xmit_lowat | 32768
tcp_recv_hiwat | 65536
tcp_slow_start_initial | 2

##### Mod_JServ Configuration

To adjust the maximum number of socket connections that Mod_ JServ may handle simultaneously, modify the following parameter in the jserv.properties file.

Name | Value
--- | ---
security.maxConnections | 3000

##### Configuring Web Integration Server and Web Integration Developer

This section shows how to start the Web Integration Server. It also describes how to configure the Web Integration Server and Web Integration Developer so that they run using a firewall.

If you are behind a firewall, you need to set proxies for the Web Integration Server and the Web Integration Developer.

Web Integration Server

To set the proxies for the Web Integration Server, follow these steps:

1. For Solaris installations, run the Web Integration Server.

   From the Oracle_Home/panama/WebIntegration/Server/bin directory, type:

   `$ server.sh &`

   For Windows NT installations, the Web Integration Server is installed as a service, and should be started automatically.

2. From a browser, go to the Web Integration Server URL:

   host_name.domain:5555

3. Log in to the Web Integration Server as follows (the default password is manage):

   User name: Administrator

   Password: manage

4. Select Settings. The server settings appear. Click [Edit].

5. Enter the Proxy (HTTP) and the Secure Proxy (HTTPS) settings for your environment.

6. Click [Submit].

7. Click [Logout].

Note: To increase the maximum heap size in the Web Integration Server startup script, add the -mx option.

Web Integration Developer

To set the proxies for the Web Integration Developer, follow these steps:

1. Run the Web Integration Developer from the Windows NT Programs menu. Select Programs, Oracle for Windows NT, Portal-to-Go, and then Web Integration Developer.

2. From the Edit menu, select Preferences and then Configuration.

3. Enter the Proxy (HTTP) and the Secure Proxy (HTTPS) settings that are appropriate for your environment.

4. Click [OK].

##### Oracle 8.1.5 and 8.1.6 Configuration

Add TCP.NODELAY=TRUE in the PROTOCOL.ORA file.

Set the maximum number allowed for database connections appropriately.

##### JDK

Each Java Virtual Machine (JVM) should not support more than 1000 concurrent user sessions.

| Copyright © 2000 Oracle Corporation. All Rights Reserved. |
|  | Library | Service