cancel
Showing results for 
Search instead for 
Did you mean: 

Question regarding Connection Pool mode in Universe connection settings (UDT)?

Former Member
0 Kudos

Hi,

In the Connection settings of a Universe we have 3 connection modes

1. Disconnect after each transaction

2. Keep the connection active for (time is set in Pool timeout)

3. Keep the connection active for whole session (local mode)

I understand that connection is to the Database (or datasource)

now if I say Disconnect after each transaction, what should be considered as a transaction over here and how does it reconnect after disconnecting?

when the mode is set to Keep the connection active for (time is set in Pool timeout is 10 minutes) what happens during this mode. After 10 minutes how does it reconnect?

and when the mode is set to Keep the connection active for whole session (local mode), what should be considered as a session?

Thanks

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member4998
Active Contributor
0 Kudos

Hi..

Please find the below

Connection Pool Mode is set to disconnect after each transaction.

  • Disconnecting after each transaction also impacts key end-user workflows such as working with hierarchical list of values.
  • The connection life-time can have a significant impact when working with SAP NetWeaver BW.

Keep the connection active for (time is set in Pool timeout is 10 minutes)

  • To minimize the risk of metadata cache being desynchronized with SAP BEx Query updates, you can change the Pool timeout from 10 minutes to 1 minute.

Keep the connection active for whole session (local mode),

  • Connection life-time can also impact updating existing universes with changes in the BEx Query.
  • This is because the OLAP BAPI interface builds a metadata cache on the client side every time a connection to SAP NetWeaver BW is established. This cache is only emptied when the connection closes