BPM Admin Guide

TROUBLESHOOTING

This section discusses BPM admin troubleshooting for Maconomy.

This is the start of your concept.

Determine BPM Version and Solution

The internal version number, the external version number, and the solution appear in universes and documents of a BPM release. In universes, the version numbers and solution are stated as custom properties of the data foundations (DFX files). In documents, they are stated in variables.

The format of internal version numbers is:

<version>.<sub-version>.<service pack>.<fix pack>

For example: 17.0.102.0

You cannot log in to BusinessObjects in the Portal using Internet Explorer (ID). The Login screen is displayed, but nothing happens when you try to log in (you stay on the same page). Instead, you can log in directly in infoview.

The reports are embedded into the Maconomy Portal using IFrame. IE gives a lower level of trust to IFRAME pages (IE calls this "third-party" content). If the page inside the IFRAME does not have a Privacy Policy, its cookies are blocked. This is indicated by the eye icon in the status bar. When you click this icon, it lists the blocked URLs. The cookies are used to store the BusinessObjects session. Because the session cannot be saved, the user cannot log in.

To resolve the login problem, follow these steps:

  1. Create a folder named w3cin [Business Objects]\Tomcat55\webapps\
  2. Create a file called p3p.xml in the same folder with the following code:

    <META>
       <POLICY-REFERENCES>
          <POLICY-REF about="/w3c/policy.xml">
              <INCLUDE>/</INCLUDE>
              <COOKIE-INCLUDE/>
          </POLICY-REF>
       </POLICY-REFERENCES>
    </META>
Note: This procedure does not work when you use an IP instead of a server name in the OpenDocument link.

GC Overhead Limit Error on ETL Running Pentaho 9.3

When running ETL jobs or transformations involving large amounts of data via Spoon on a system running Pentaho 9.3, memory is gradually consumed until it hits the limit. It then displays an error message stating the GC overhead limit was exceeded, for example:

ERROR (version 9.3.0.0-428, build 9.3.0.0-428 from 2022-04-12 04.56.25 by buildguy) :
UnexpectedError:
ERROR (version 9.3.0.0-428, build 9.3.0.0-428 from 2022-04-12 04.56.25 by buildguy) :
java.lang.OutOfMemoryError: GC overhead limit exceeded
at org.pentaho.di.trans.steps.dimensionlookup.DimensionLookup.lookupValues
(DimensionLookup.java:338)
at org.pentaho.di.trans.steps.dimensionlookup.DimensionLookup.processRow
(DimensionLookup.java:232)
at org.pentaho.di.trans.step.RunThread.run(RunThread.java:62)
at java.lang.Thread.run(Unknown Source)

As a workaround, you must disable the Gather Performance Metrics option.

Note: This issue does not affect jobs or transformations executed via Kitchen.

To resolve this issue:

  1. On the repository, start Spoon.
  2. Log in as admin/admin.
  3. Open the Full Load or Create job.
  4. In the Run Options dialog box, ensure Gather Performance Metrics is deselected.
  5. Run the job (F9).