Changing the Connection Time Out Setting

If you are unable to deploy an application because of a connection time out error, you may need to increase the time out setting in the BPMA_Server_Config.xml file.

  To change the time out setting in BPMA_Server_Config.xml:

  1. Stop the Performance Management Architect dimension server.

  2. Navigate to the BPMA_Server_Config.xml file in <Middleware Home>\EPMSystem11R1\products\foundation\BPMA\AppServer\DimensionServer\ServerEngine\bin.

  3. Make a back up copy of the BPMA_Server_Config.xml file.

  4. Edit the logging configuration section of the BPMA_Server_Config.xml file so that debug-level messages are logged to the Windows Event Viewer by changing the logging level from INFO to DEBUG:

    5. 

  5. 

    Add the following XML tags under the </Data Access Layer> section of the BPMA_Server_Config.xmlfile:
    

    <ConnectionPooling>
                                       <PoolingEnabled>true</PoolingEnabled>
                                       <Connection Lifetime is the maximum life time (in seconds) of the 
connection. Setting this to 0 disables it.-->
                                       <ConnectionLifetime>0</ConnectionLifetime>
                                       <!--MaximumPoolSize is the maximum number of connections in the 
pool.-->
                                       <MaximumPoolSize>100</MaximumPoolSize>100>
                                       <!--MinimumPoolSize is the minimum number of connections in the 
pool.-->
                                        <MinimumPoolSize>1</MaximumPoolSize>100>
                                        <!--Controls the enlistment behavior and capabilities of a conneciton 
in context of COM+ transactions or System.Transactions.
                                                     This setting must be either "dynamic" or "true".-->
                                        <Enlist>true</Enlist>
                                        <!--The following 5 settings are specific to Oracle database 
Connection Timeout is the maximum time (in seconds) to wait for a free connection from the pool.-->
                                        <ConnectionTimeout>15</ConnectionTimeout>
                                        <!--HA Events enables ODP.NET connection pool to proactively remove 
connections from the pool when an Oracle RAC service, service member, database, or node goes down.  Works with RAC, 
Data Guard, or a single database instance-->
                                         <HAEvents>false</HAEvents>
                                         <!--Load Balancing enables ODP.NET connection pool to balance work 
requests across Oracle RAC instances based on the load balancing advisory and service goal.-->
                                         <LoadBalancing>false</LoadBalancing>
                                         <!--PoolSizeDecrement (Decr Pool Size) is the number of connections 
that are closed when an excessive number of established connections are unused.-->
                                          <PoolSizeDecrement>5</PoolSizeDecrement>
                                          <!--PoolSizeIncrement (Incr Pool Size) is the number of new 
connections to be created when all connections in the pool are in use.-->
                                          <PoolSizeIncrement>1</PoolSizeIncrement>
                                          <!--Validate Connection validates connections coming from the 
pool.-->
                                          <ValidateConnection>false</ValidateConnection>
                                          <!--The following 4 settings are specific to MS SQL Server.-->
                                          <ConnectionReset>true</ConnectionReset>
                                          <LoadBalanceTimeout>0</LoadBalanceTimeout>
                                          <!--The following setting can be used to add any custom setting not 
covered by anything else.-->
                                          <CustomSetting></CustomSetting>
                             </ConnectionPooling>
    6. 

  6. 

    Increase the Connection Time out setting to a higher value (for example 600 minutes, or 10 hours).
    

    7. 

  7. 

    Restart the Performance Management Architect dimension server,
    

    8. 

  8. 

    Open the Windows Event Viewer to ensure that there is an event that includes the entire connection string you created.
    

    9. 

  9. 

    Test to make sure that the connection pool time out setting returns to the default value if you remove the section that you created in step 5 from the BPMA_Server_Config.xml file and restart the Oracle Hyperion EPM Architect dimension server.
    

    10.