ABAP MDM Connection Pool

Question

Hi,
I'm trying to write a report that extracts information from MDM. Everytime it's called, it has to establish a new connection to MDM where the hand-shake takes about 20-30 secs.
I was wondering if ABAP MDM Connection Pooling exist.
In Java MDM, you can configure J2EE with connection pool, so that you can reuse a connection rather than re-establishing a new connection on every call.
I've read Thomas Jung's WIKI on "How do you implement a MDM Connection Help Class?", however I cannot reuse this class. The static attribute in the class is not persisted.
Did I do something wrong?
I tried turning it into a shared memory root class, however it complains about an object reference still exist and would not allow me to do "dettach_commit( )".
Don't know any other ways to store the connection handle in memory.
Export/Import, SPA/GPA are not OO friendly.
Cheers
Michael

Answer 1

Hi Andreas,
Thanks for your reply, it is good to confirm my understanding of the ABAP API connection.
For your interest, I have changed part of the connection code to increase the speed of the connection significantly.
Firstly to clarify, the connection from the ABAP stack to MDM is actually quite fast.
Upon the first call, the method CL_MDM_PROVIDER_SP04_PL03->_LOAD_FIELD_INFORMATION is called which reads the META-DATA from MDM for every table and every field. This could normally take 1 minute in our system landscape. I've changed to code to buffer the meta-data.
In a production/stable environment, it is unlikely for the META-DATA to change rapidly. Hence reading this on every connection is a waste of time.
This could be useful only if we are in implementation phase where this changes all the time.
1) In transaction MDMAPIC, I've added the ABAP implementation for MDM Version Support as my own MDM provider class ZSP04_PL03 with provider type ZCL_MDM_PROVIDER_SP04_PL03.
ZCL_MDM_PROVIDER_SP04_PL03 is a copy of CL_MDM_PROVIDER_SP04_PL03.
2) In ZCL_MDM_PROVIDER_SP04_PL03, the method LOADFIELD_INFORMATION is changed to read from buffer first before calling MDM. If the buffer is empty, it will read from MDM and store result into buffer etc.
I'm storing the information in a transparent table at the moment.
I buffer the three class attributes:
- mt_field_meta_data,
- mt_mdm_field_meta_data,
- mt_field_code2id_map.
As MT_FIELD_META_DATA is a complex structure (i.e. tables within table), I had to split it up into many different tables.
I can provide the code if you are interested.
Cheers,
Michael.