Enabling GZIP compression on the HTTPBC or a suggested alternative approach

Question

Hi,
I posted this on the openusb-users group, but I haven't come up with a good solution yet.
Any takers?
Thanks,
Rob
http://openesb-users.794670.n2.nabble.com/gzip-compression-support-in-HTTP-BC-tp5366301.html
Does anybody know whether the HTTP BC shares all of the same features that the Glassfish HTTP listener supports such as gzip compression? If so, where are those parameters specified for the HTTP BC? (Compression of the XML can of course make a tremendous bandwidth savings for the typical XML passed around via SOAP.)
Please see:
http://docs.sun.com/app/docs/doc/820-4338/abhco?a=view
compression - on
Specifies use of HTTP/1.1 GZIP compression to save server bandwidth. Allowed values are:
off – Disables compression.
on – Compresses data.
force – Forces data compression in all cases.
positive integer – Specifies the minimum amount of data required before the output is compressed.
If the content-length is not known, the output is compressed only if compression is set to on or force.
compressableMimeType text/html,text/xml,text/plain
Specifies a comma-separated list of MIME types for which HTTP compression is used.
If there isn't a way to configure the HTTPBC, What would be the best way to enable a gzip compression of the XML for the HTTPBC or JBI framework in general?
My first approach might be to just have a Glassfish HTTP-Listener based WebService delegate to the HTTPBC or more directly to the JBI SE components if possible. Maybe a filter on the HTTPBC to gzip the payload? Are there any plans to refactor HTTPBC to use the Glassfish HTTP Listener code, it appears to have more capability and options?
Rob

Answer 1

I tried it did not work.
Below are the steps which I did:
Test2: Table level compression test
===================================
CREATE TABLE SCOTT.TEST_PMT_TAB_COMP
PMT_ID INTEGER NOT NULL,
PMT_AGCY_NBR CHAR(7 BYTE),
PMT_SBAGCY_NBR CHAR(7 BYTE),
PMT_PAY_DT DATE,
PMT_POL_NBR CHAR(14 BYTE),
PMT_POL_SEQ_NBR CHAR(2 BYTE),
PMT_PRM_INSD_NM VARCHAR2(30 BYTE),
PMT_PAY_TYP_DESC VARCHAR2(20 BYTE),
PMT_PAY_AMT NUMBER(11,2),
PMT_POST_DT DATE
COMPRESS FOR ALL OPERATIONS;
inserting record from the test table:
SQL> insert into SCOTT.TEST_PMT_TAB_COMP select * from SCOTT.TEST_PMT;
5051013 rows created.
SQL> commit;
Commit complete.
SQL> select count(*) from scott.TEST_PMT_TAB_COMP;
COUNT(*)
5051013
Checking size:
SQL> select bytes/1024/1024, segment_name, owner, segment_type, tablespace_name from dba_segments where segment_name='TEST_PMT_TAB_COMP';
BYTES/1024/1024 SEGMENT_NAME OWNER SEGMENT_TYPE TABLESPACE_NAME
776 TEST_PMT_TAB_COMP SCOTT TABLE USERS_DATA01
SQL> select owner, table_name, COMPRESSION, COMPRESS_FOR from dba_tables where table_name='TEST_PMT_TAB_COMP';
OWNER TABLE_NAME COMPRESS COMPRESS_FOR
SCOTT TEST_PMT_TAB_COMP ENABLED OLTP
Now it is occupying more size.