« Compress Series of Editions   |   Deleting Ledger Update History »

Compressing Ledger Line Data by Generation

This manual is in pilot operation.

Overview

Ledger data in the fusion_place database is managed by generation. Each time the ledger data is updated, a new generation is added. As the number of generations increases, the time required for initial loading of the ledger also increases (initial loading occurs only when accessing ledger edition data for the first time after server startup).

This function compresses the ledger line data by generation contained in the specified edition. If initial load times are increasing, you can use this function to speed up the load process. The compressed data is stored separately from the original generation data, so running this process does not delete generation history of the ledger.

Only users with Designer or Administrator privileges can execute this request.

Note: When "Publish Workspace Edition Data" is executed via fusion_place [Manager], compression of ledger line data by generation is automatically performed after "publication" and "Compress Series of Editions".

Also, "Accelerating Initial Loading of Workspace Edition" in fusion_place [Manager] performs this compression for the workspace edition.

How to Write a Request

Below is an example request for "Compressing Ledger Line Data by Generation":

<request type="COMPRESS_LEDGER_LINES" desc="Compress Public Edition Ledger Lines">
  <parameters>
    <parameter name="APPLICATION" value="SAMPLE1"/> (1)
    <parameter name="LEDGER_EDITION" value="PUBLIC"/> (2)
  </parameters>
  <contents> (3)
  </contents>
</request>
1 "Application" parameter
2 "Ledger Edition" parameter
3 Request Content

Parameters

Specify the target application and the target ledger edition.

Parameter Required Key Description

APPLICATION

Yes

None

Specify the label of the target application.

LEDGER_EDITION

Yes

None

Specify the "ledger edition key" of the target ledger edition. Reserved ledger keys are:

PUBLIC : Public Edition
WORKSPACE : Workspace Edition

Request Content

There is no "Request Content."

Response Content

Below is an example response for "Compressing Ledger Line Data by Generation":

<response type="COMPRESS_LEDGER_LINES" desc="Compress Public Edition Ledger Lines">
  <returned-contents> (1)
  </returned-contents>
  <result>
    <code>SUCCESSFUL</code> (2)
    <started-at time-zone="Asia/Tokyo">2015/02/28 09:50:04.227</started-at>
    <ended-at time-zone="Asia/Tokyo">2015/02/28 09:50:07.827</ended-at>
    <messages>
      ... (3)
    </messages>
  </result>
</response>
1 Returned Content
2 Processing Result Code
3 Message

Returned Content

There is no returned content.

Message

If the processing result code is "SUCCESSFUL," nothing is displayed in the message field.

If the processing result code is "FAILED," the message field displays the reason for the failure. No other result codes are used.

Notes

This process does not include "Sweeping Garbage." If data cleanup is required, run the sweeping garbage process separately after this.