IBM Support

What technology/algorithm does Sterling Application (Platform, Foundation) use for XML Compression?

Question & Answer


Question

What technology/algorithm does Sterling Application (Platform, Foundation) use for XML Compression?

Answer

1.    In the platform, for handling XMLs in the Configurator, Sterling uses ZIP format for compression by invoking 'ZipOutputStream.class' of java.util.zip.

Below sample code snippet can be used for reference:

protected void serializeDocument (YFCDocument doc, HttpServletResponse resp, boolean compressData) throws IOException {
if (!compressData) {
                  doc.serialize(resp.getOutputStream());
      } else {
                  resp.setHeader("YFC-IsCompressed","true");
                  ZipOutputStream out = new ZipOutputStream(resp.getOutputStream());
                  ZipEntry entry = new ZipEntry("YFCData.xml");
                  out.putNextEntry(entry);
                  doc.serialize(out);
                  out.closeEntry();
                  out.flush();
                  out.close();
      }  

2.     While configuring JMS or any other queues in the service definition framework, whenever one check the 'Needs Compression' flag, the application creates a BytesMessage object using session.createBytesMessage instead of normal text message to put in JMS.
For more information on the BytesMessage, please refer to (http://java.sun.com/products/jms/javadoc-102a/index.html).
There is no explicit compression done by Sterling other than above here.
 
3.     From XML compressions in RCP (Rich Client Platform) please refer the article, NFX5007. RCP uses GZIP compression technique.

[{"Product":{"code":"SS6PEW","label":"IBM Sterling Order Management"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"Mapping and Translation","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Historical Number

FAQ3197

Document Information

Modified date:
16 June 2018

UID

swg21519054

Page Feedback