IBM TRIRIGA Application Platform

Version 3.2

Administrator Console
User Guide

© Copyright IBM Corporation 2011.

Note
Before using this information and the product it supports, read the information in “Notices” on page
40.

This edition applies to version 3, release 2, modification 0 of IBM® TRIRIGA® Application Platform and
to all subsequent releases and modifications until otherwise indicated in new editions.

© Copyright International Business Machines Corporation 2011. All rights reserved.

US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule
Contract with IBM Corp.
 Contents

ABOUT THIS GUIDE ................................................................................1

Conventions ..................................................................................................................................................................................... 1

Intended Audience .......................................................................................................................................................................... 1

Prerequisites .................................................................................................................................................................................... 1

Support ............................................................................................................................................................................................ 1

1. USING THE ADMINISTRATOR CONSOLE .................................................2

Logging In ....................................................................................................................................................................................... 2

IBM TRIRIGA System Administration ........................................................................................................................................ 2

Admin Summary ............................................................................................................................................................................. 2

Admin User Manager ..................................................................................................................................................................... 3

Agent Manager................................................................................................................................................................................ 3

Build Number .................................................................................................................................................................................. 6

Cache Manager ............................................................................................................................................................................... 6

Cleanup Agent Manager ................................................................................................................................................................ 8

Database Manager .......................................................................................................................................................................... 8

Database Query Tool ...................................................................................................................................................................... 9

DataConnect .................................................................................................................................................................................. 11

Error Logs ..................................................................................................................................................................................... 12

Java Manager ................................................................................................................................................................................ 12

Language Manager ....................................................................................................................................................................... 13

License Manager ........................................................................................................................................................................... 13

Managed Processes ....................................................................................................................................................................... 13

Metadata Analysis ........................................................................................................................................................................ 14

Performance Monitor ................................................................................................................................................................... 15
Performance Monitoring Section................................................................................................................................................ 15
Key Metrics Section ................................................................................................................................................................... 16

Platform Logging .......................................................................................................................................................................... 16

Scheduler Manager ....................................................................................................................................................................... 17

System Manager............................................................................................................................................................................ 18

Threads Manager.......................................................................................................................................................................... 18

Users Manager .............................................................................................................................................................................. 19

Workflow Agent Manager ........................................................................................................................................................... 19

Workflow Events .......................................................................................................................................................................... 20

Workflows Executing ................................................................................................................................................................... 21

Support & Report ......................................................................................................................................................................... 22

2. SERVER.LOG ERROR MESSAGES ........................................................ 23

INDEX .............................................................................................. 38
About This Guide
IBM TRIRIGA solutions are built on the IBM TRIRIGA Application Platform, a multi-tiered Web platform
that provides users with unparalleled flexibility, accessibility, and scalability. This platform uses a
highly scalable J2EE architecture, a data model that allows you to extend and enhance IBM TRIRIGA
products or, if properly licensed, create modules that integrate with the pre-defined logic and
processes into a feature rich, workflow-driven intelligent business system.

The IBM TRIRIGA Administrator Console is your tool for analyzing and optimizing the system health.

This user guide describes the procedures for operating and administering the IBM TRIRIGA system
through the Administrator Console.

Conventions
This document uses the following conventions:

 Note – A Note provides important information that you should know in addition to the standard
details.

 Tip – A Tip adds insightful information that may help you use the system better.

 Attention – An Attention note highlights an action that may result in damage to your system or an
unforeseen loss of data.

Intended Audience
This guide is for Application Administrators and others tasked with administering the IBM TRIRIGA
system.

Prerequisites
This guide assumes the reader understands the IBM TRIRIGA Application Platform and their company
business practices.

Support
IBM Software Support provides assistance with product defects, answering FAQs, and performing
rediscovery. View the IBM Software Support site at www.ibm.com/support.

© Copyright IBM Corporation 2011. 1

1. Using the Administrator Console
Analyzing and optimizing the system health are primary functions for a system administrator. IBM
TRIRIGA developed the Administrator Console in order to facilitate these tasks. The IBM TRIRIGA
Administrator Console categorizes data into segments in order to help a system administrator find
information and make changes to it quickly and effectively. Basically, the Administrator Console is a
centralized location for viewing and editing system settings in order to optimize system health.


Note – If the system is configured to use Resource References to access the configuration files
instead of adding the Config directory to the application Classpath, you cannot edit any
configuration files through the Administrator Console.

Many of the settings in the Administrator Console are tied to IBM TRIRIGA properties. The properties
files are described in “Properties Files” in the IBM TRIRIGA Application Platform 3 Installation and
Implementation Guide.

Logging In
The Administrator Console can be accessed by opening a Web browser and typing the following value
into the address field: http://<hostname:port>/[context path/]html/en/default/admin.
For <hostname:port>, enter the value appropriate for your environment. Everything in the URL after
that value is the same for all users.

To login, enter the administrator Login and Password and click Login.

An administrator can sign in to the main application and then the IBM TRIRIGA Administrator Console at
the same time when using a browser with tabs. An administrator must first sign in to the main
application, then access the Administrator Console URL, at which time the administrator automatically
is allowed into the Administrator Console if they have permissions. If they do not, they are prompted
for a login. When an administrator signs out of either the Administrator Console or the main
application, they will be signed out of both.

IBM TRIRIGA System Administration

Upon a successful login, you see the IBM TRIRIGA System Administration page. The left panel shows the
list of objects that can be managed from the Administrator Console. The right panel contains
information about the managed object selected in the left panel.

The System Status in the upper left panel above the Managed Objects list shows a quick message
indicating the overall status of the system. When the system detects an error, the word Error: appears
in red along with a short summary of the problem.

Admin Summary
The Admin Main panel, on the right, shows a general summary of the system, a high-level overview of
the system configuration. The data is read-only and is displayed upon entering the Administrator
Console or by selecting Admin Summary in the Managed Objects panel, to the left.

© Copyright IBM Corporation 2011. 2

Admin User Manager
The Admin User Manager option, on the left panel, displays all users in the system who are part of the
Admin Group and their access rights to the Administrator Console. There are three access options: No
Access, Read-Only Access, and Full Access. If you want to change a user access, click the check box to
the left of the user name, click the radio button to the right of their name that corresponds to the
required new access, and click Update Console User.

Agent Manager
The Agent Manager is where process agents are managed and configured. The IBM TRIRIGA Application
Platform uses agents to do background processing. There are several different types of background
processes, so a number of different agents exist, each doing one type of processing. For example,
there is one agent to do data cleanup, one to execute asynchronous workflows based on events, and
one to calculate extended formulas for records. An agent is configured to automatically start as long as
it was running when the server went down.

Tip – The Extended Formula Agent recognizes Query field filters for fields in Live Link sections.

 When a record is added or removed from the referenced Live Link section, the Extended Formula
that uses that query will be recalculated. You must clear the Extended Formula Cache from the
Administrator Console after upgrading is complete.

The Extended Formula Agent recognizes Query field filters for fields in Live Link sections. When a
record is added or removed from the referenced Live Link section, the Extended Formula that uses that
query will be recalculated. You must clear the Extended Formula Cache from the Administrator Console
after upgrading is complete.

With the exception of the Workflow Agent and the Data Import Agent, agents are not designed to have
multiple instances running against the IBM TRIRIGA database. The Workflow Agent and the Data Import
Agent are called multi-instance agents. All other agents are called single-instance agents. System
problems can occur if more than one instance of single-instance agents is allowed to run
simultaneously.

The Agent Manager identifies which agents are currently running across all servers in the installation,
including information about on what server they are running. This manager configures agent startup for
all servers in the installation, consolidating agent management. It provides the ability to request any
running agent to stop regardless of the server on which it is running and to request that an agent starts
on a specific server. It prevents additional instances of a single-instance agent from starting if an
instance is already active.

The Agent Manager also displays a list of currently active servers along with which agents are not
allowed to run on each server.

The columns in the top section of the Agent Manager are as follows:

Column Description

Agent Lists each process agent in IBM TRIRIGA.

© Copyright IBM Corporation 2011. 3

 Column Description

Status Shows the status of the agent. The following values may appear in
the Status column:

 Start Requested
 Starting
 Running
 Stop Requested
 Stopping
 Stopped
 Not Running
 Start Failed

It is unlikely that you will see a Start Requested, Starting, Stop

Requested, or Stopping value because these states are usually very
brief.

Action An action you can take on that agent in its current status. Actions
include Stop, Start, and Cancel.

Running On Lists the host name of the server on which the agent is running.

Start On Enter the host name of the server on which you want to start an
agent. Multi-instance agents have Add and/or Remove actions next
to the text box. The Add action adds another line used to configure
or start another instance of the agent.

The columns in the Active Servers section are as follows:

Column Description

Host The host name of the server.

Address The IP address of the server.

Agents Not Allowed Agents listed in the AGENTS_NOT_ALLOWED property in the server
TRIRIGAWEB.properties file.

Agent startup configuration is kept in the IBM TRIRIGA database in the Agent Startup table
(AGENT_STARTUP). When a request to start an agent is made, the system adds an entry to the Agent
Registry table (AGENT_REGISTRY), and when an agent stops, the system updates its state in the
registry. The Agent Registry includes the startup ID, the type of agent, its ID, the host name of the
server the agent is running on, the time it was started, the heartbeat time, and the agent state. The
Agent Registry is available to all servers in the installation and is the source of the current activity
information displayed in the Agent Manager managed object.

© Copyright IBM Corporation 2011. 4

Whenever the status of an agent changes, the system writes an INFO entry to the server log with
information about the state transition. For example:

INFO [com.tririga.platform.agent.AgentManager](http-0.0.0.0-8001-3) Start requested for

CleanupAgent on server337.

INFO [com.tririga.platform.agent.BaseAgentThread](CleanupAgent) CleanupAgent on server337 is now

running.

INFO [com.tririga.platform.agent.AgentManager](http-0.0.0.0-8001-3) Stop requested for

CleanupAgent on server337.

INFO [com.tririga.platform.agent.BaseAgentThread](AgentHeartbeatThread) CleanupAgent on

server337 is now stopped.

The AGENTS_NOT_ALLOWED property in a server TRIRIGAWEB.properties file identifies agents that

may not be started on that server. The Agent Manager will not allow a user to start an agent listed in
AGENTS_NOT_ALLOWED for a server to be configured to start on that server. Should a user try to start
an agent on the AGENTS_NOT_ALLOWED list, the system writes an INFO message to the server log and
does not start the agent.

The configuration of what servers each agent should start on and if an agent should never be allowed
to start on a server is kept in the Agent Startup table in the IBM TRIRIGA database. The Agent Startup
table includes the agent type, the host name, and the configuration. The Agent Startup table is the
source of the TRIRIGAWEB.properties information displayed in the Agent Manager.

When a server starts, it checks the Agent Startup table to see which agents it should start. It updates
the agent configuration based on the agent names in the AGENTS_NOT_ALLOWED property. When a
single-instance agent starts, it checks to see if another instance of the same agent is already running.
If so, the agent is not started, a warning is logged that shows the name of the server on which the
current instance is running, and the agent adds an Agent Startup Table entry that indicates it was
requested to start but failed.

The Agent Manager uses the Agent Registry and the agent configuration to display agent status,
allowing it to accurately list all of the agents currently running, configured to run, or that failed to
start. For multi-instance agents, it lists all of the servers on which the agent is running and includes an
Add action and/or a Remove action for each one.

A request to start an agent can be issued to any server by entering the server name in the field in the
Start On column and clicking Start in the Action column. Use the server name listed in the Host column
of the Active Servers section. Using the IP address or a server name not listed in the Active Servers
section does not start the agent.

Clicking the Start action in the Action column when the Start On field does not contain a value causes
the system to use the server on which you are signed into the Administrator Console.

Putting <ANY> in the field in the Start On column and clicking Start in the Action column tells the
system to start that agent on the next available server. The Agent Manager attempts to start the agent
unless the agent is configured to not start on the server or it is a single-instance agent and another
server has already started it.

© Copyright IBM Corporation 2011. 5

A request to stop an agent can be issued to any server by clicking Stop in the Action column.

Clicking Start or Stop automatically saves the Start On configuration for that row in the database. Any
time you want to save the configuration as it is currently displayed for all rows, click Save, which
updates the database.

Refresh updates the values displayed in the Agent Manager. Use this to view the latest status.

The Add action shows in the Start On column for multi-instance agents. Use it to add another line to
configure or start another instance.

To configure multiple instances of multi-instance agents:

To Configure Multiple Instances of Multi-Instance Agents

1. Click next to the server name.

2. The system adds a new row with a status of New Entry. Enter the server name to be
started.

3. Click Save. The server changes the status of the new row to Not Running.

4. Notice the Add and Remove actions.

You can configure another server by repeating these steps.

Build Number
The System Build Information panel appears when you select Build Number on the left panel, and
displays the number of the IBM TRIRIGA application build, the client information, and the platform
version. This number is generated during the build process. Additionally, the database holds the
current build number. This build number changes in both the EAR file and the database whenever a
platform upgrade is performed.

Cache Manager
The IBM TRIRIGA Application Server stores data values normally stored in the database in cache
memory on the application server. These values do not change often. When they do change, in a
development setting for example, use the Cache Manager to retrieve the new values from the
database. Click a link in the Flush a Cache column on the right panel to flush that cache and move the
new value to memory (this procedure clears the BIRT cache as well).

Link Description

State Data Refreshes all State Family instances, loading the data from the
STATE_TRANSITION table. This should be used if state transitions are
not updated when making changes in the Data Modeler or Form
Builder.

© Copyright IBM Corporation 2011. 6

 Link Description

Security Scope Refreshes changes made to any Geography, Organization, or Groups

within Groups. It will first refresh the Hierarchy Table cache, from
IBS_SPEC_STRUCTURE. It will then clear the Form (GUI) Security
Cache after changes; and finally it will clear the Hierarchical
Security Cache.

Workflows For Agent Refreshes the workflow templates for the local Synchronous and
Asynchronous workflows.

UOM Data Refreshes any new UOM, edits to existing ones, or even if you
deleted any Measure.

Portal Logo Refreshes the dimension data for the portal logo.

Query Cache Refreshes the values in cache from the REP_TEMPLATE tables.

Object Metadata Cache Refreshes the Object Metadata Cache, where data is stored as
defined in the Data Modeler.

Extended Formula Cache Refreshes the Extended Formula Cache.

Password Type Cache Refreshes the Password Type Cache.

Hierarchy tree Data Refreshes the Hierarchy Cache by clearing all trees in the hierarchy
cache. However, it does not rebuild the hierarchies.

Hierarchy Tree Data – with Rebuilds the cache and also rebuilds IBS_SPEC_TREE. The
rebuild IBS_SPEC_TREE table stores records of type Location, Geography,
and Organization. Click Hierarchy Tree Data – with rebuild if you
suspect IBS_SPEC_TREE is out of sync. If the Location, Geography,
and/or Organization trees are large, the refresh and rebuild could
take some time.

All Caches (Global) Clears all caches across all active servers. This does not include a full
hierarchy rebuild. This is an asynchronous event that is queued and
may take some time to process on each server.

Custom ClassLoader Data Clears all existing ClassLoader instances that have been previously
loaded. In Production Mode, this is the only way to refresh a
ClassLoader object that has already been deployed. When the cache
is cleared, the next time a ClassLoader object is requested, it will
pull the latest data from the database.

© Copyright IBM Corporation 2011. 7

Cleanup Agent Manager
Set the parameters in the Cleanup Schedule and Cleanup Commands sections so the system performs
cleanup activities according to the best practices of your company. The Cleanup Commands analyze
and help maintain the database.

As part of the Cleanup Agent normal processes, it refreshes hierarchy caches for Geography, Location,
and Organization across all servers that are active when the Cleanup Agent runs.

You cannot delete a Cleanup Command that is used in a Cleanup Schedule. Delete the Cleanup
Schedule first, then the Cleanup Command.

 Attention – Cleanup Commands are different for systems using Oracle and for systems using
Microsoft SQL Server systems.

Database Manager
The Database Manager displays database settings and features to clean the database.

The Database Summary section displays general data pool information.

 Clicking View displays the same data in read-only fields.

 Clicking Edit displays the summary data in editable fields where the database information can
be changed.
 Clicking Test checks the connection string, user, and password.

The Database Environment section displays the actual time on the database and on the server and the
database character set.

The Database Admin Tasks section displays the following cleanup tools:

 Click Analyze or Rebuild Indexes to clean up the schema index.

 Click Cleanup WF to remove workflow instances that are older than one day and not required
by the system.
 Click Cleanup BO to remove record data that was deleted more than 12 hours ago.
 Click Cleanup Scheduled Events to remove scheduled events. The system deletes stale
recurrence records (recurrences where the event or scheduled event may not exist), scheduled
event records where the associated event has been removed, and events that have no more
scheduled events.
 Click Cleanup Commands and Analyze to run the cleanup analyze scripts and to clean the
schema index. Performance may slow while this runs.
 Click Reprocess published drawings to republish drawings in the system.
 Click Cleanup All Tasks to start and run all cleanup tasks.

 Note – Scheduling Agent must be stopped before running all cleanup tasks.

© Copyright IBM Corporation 2011. 8

The Database Space section displays disk space in use and available disk space on the database, or
error messages if the Database Manager cannot read from one or more of the selected tables.

Database Query Tool

You can use the Database Query Tool to run SQL SELECT statements against the database. This can help
isolate issues. With this tool you can run, add, save, modify, execute, import, and export queries.

 Attention – Using long running SQL scripts can cause unusual load on the database and may time out
on the client side.

The following table describes how to save, modify, execute, import, and export queries:

Action Description

Run a query Either:

Type a SQL SELECT statement in the SQL Query text box and click
Run Query.

 Tip – Use this method for an ad hoc query.

– or -

Click the name of the query in the SQL Script Name column and click
Run Query.

Add a new query Click Add New Query. A new field and action appear below the blue
action tabs. Enter the query name in the new Script Name field, a
description in the SQL Description text box, and the SQL script in the
SQL Query text box. Click Save Query.

Save the query in the SQL Click Add New Query. A new field and action appear below the blue
Query text box action tabs. Enter the query name in the new Script Name field and
a description in the SQL Description text box. Click Save Query.

 Tip – Use this method to save an ad hoc query.

Create a new query that is a Select the query from SQL Script Name column and make the
modification of an existing changes in the SQL Query text box. Click Add New Query. Enter the
query query name in Script Name and a description in the SQL Description
text box. Click Save Query.

Modify a query Select the query from the SQL Script Name column and make the
changes in the SQL Query text box. Click Save Query.

© Copyright IBM Corporation 2011. 9

 Action Description

Delete a query Select the query from the SQL Script Name column. Click Delete
Query.

Import queries Click Import Queries. Click Browse to find the file and click Upload.
The file to be uploaded must be an .xml file or have an identical
structure.

If the name of the SQL script to be uploaded is already in use, the

system appends [n] to the name, where n is the next increment. For
example, if test and test[1] already exist, the import of another
file named test would be named test[2].

The imported .xml file should contain a query section for each query
to be imported. The following shows the structure from a sample
import:
<?xml version="1.0" encoding="UTF-8"?>
<!--=================================================-->
<!-- TRIRIGA DB Query Tool Import -->
<!-- Created on 11/27/2007 11:18:54-->
<!--=================================================-->
<QueryHelpers>
<Query>
<NAME><![CDATA[ListUserTables]]></NAME>
<DESCRIPTION><![CDATA[list the tables in the db for
this user]]></DESCRIPTION>
<SCRIPT><![CDATA[select distinct table_name from
information_schema.tables]]></SCRIPT>
</Query>
</QueryHelpers>

© Copyright IBM Corporation 2011. 10

 Action Description

Export queries Click Export Queries. Enter the file name to be exported. Click
Export. Follow the File Download script to open or save the file.

The exported .xml file contains a query section for each query in the
list. The following shows the structure from a sample export:
<?xml version="1.0" encoding="UTF-8"?>
<!--=================================================-->
<!-- TRIRIGA DB Query Tool Export -->
<!-- Created on 11/27/2007 06:50:22-->
<!--=================================================-->
<QueryHelpers>
<Query>
<NAME><![CDATA[getTableList]]></NAME>
<DESCRIPTION><![CDATA[get the list of tables in the
db for this user]]></DESCRIPTION>
<SCRIPT><![CDATA[select distinct table_name from
information_schema.tables]]></SCRIPT>
<STATUS><![CDATA[Active]]></STATUS>
<CREATED_BY><![CDATA[221931]]></CREATED_BY>

<CREATED_DATE><![CDATA[1196074892546]]></CREATED_DATE>
<UDPATED_BY><![CDATA[null]]></UDPATED_BY>

<UPDATED_DATE><![CDATA[1196168232890]]></UPDATED_DATE>

<LAST_EXECUTED_BY><![CDATA[221931]]></LAST_EXECUTED_BY>

<LAST_EXECUTED_DATE><![CDATA[1196074941093]]></LAST_EXECU
TED_DATE>
</Query>
</QueryHelpers>

DataConnect
The DataConnect Manager shows all business objects with staging tables and all DataConnect Jobs.

Clicking the Business Objects with Staging Tables hyperlink displays the business objects in the system
that have a staging table. These business objects can be used in a DataConnect workflow task to move
data or update data from an external source. To see the fields for a business object that are part of
the staging table, select the check box next to the name and click Expand Data. The Fields column
then shows the IBM TRIRIGA name for the field, a hyphen, and the database name for the field. If the
field is a key field used for Upsert, the field name has an asterisk. DataConnect smart section keys
display the section name followed by the field name. Field definitions are useful for identifying the
corresponding staging table fields for inbound data.

Clicking the DataConnect Jobs hyperlink lists DataConnect jobs. The actions available are Ready Job,
Fail Job, Delete Job, Retry Job, and Force Clean Up.

 Ready Job moves a New job and the staging tables for the job to Ready state. The system acts
upon the job during the next DataConnect Agent cycle. Only jobs in the New state can be made
Ready for Processing.

© Copyright IBM Corporation 2011. 11

  Fail Job moves a Waiting or Processing job to Failed state. This action should be used only
when a workflow has completed but for some reason the job is stuck and did not complete.
 Delete Job removes both the job and the staging table entries for the job. Delete Job only acts
on jobs that are in New, Failed, Completed, Obsolete, or Ready state. The system ignores a
Delete Job action on jobs in the Processing state.
 Retry Job puts a Failed job and the staging tables for the job back into Ready state. The
system ignores a Retry action on jobs in other states.
 Force Clean Up deletes Obsolete and Completed jobs older than the number of days set in
DC_HISTORY_RETENTION_DAYS in TRIRIGAWEB.properties.

The data automatically updates based on the amount of time (in seconds) that you enter in the
Refresh Every _____ Seconds box. If you change the value, click Apply.

Error Logs
The Error Logs managed object displays a summary of errors that occurred in the system in a log
format. It shows database errors and major exceptions.

The Logs section lists the system logs. Click a hyperlinked name to download that particular log.
Administrators can roll log files. Click the icon, Roll All Log Files Now, or Roll. The system renames
the current log file with the current date and time and begins entering new messages in a fresh file.

The Process Error Log section displays database errors only. This section is read-only but gives detailed
data about the errors. Each error is displayed in line item format. For more information click Full
Process Error Log.

The Last 20 Major Exceptions section displays major exceptions in line item format. Each line item
contains a link that opens the exception and to give greater detail. To see more exceptions, click Full
Error Log.

The Last 5 lines from the error log section shows the most recent entries in the error log. To see more,
click Full Error Log.

Java Manager
The Java Manager gives general information regarding Java-related functions and systems working
within IBM TRIRIGA.

The Java Manager contains additional features that enable you to clean up the system and to view
more information. Clicking Force Garbage Collection cleans up any unused Java products from the
system. Clicking <Number> Properties displays the internal Java system properties that are used
within Java.

 Attention – Use caution when making changes to Java options.

© Copyright IBM Corporation 2011. 12

Language Manager
Use the Language Manager to set a locale for each language defined in the List Manager in IBM TRIRIGA.
Once a locale is set, it can be accessed through the User and UserSessionHelper interfaces using the
getLocale() method. Use this locale to translate third-party components such as yes/no or OK/cancel
dialogs. Dates can be translated by passing the locale to the DateFormat object along with the desired
datePattern.

The value in the System language column must be in LL_CC format, where LL is from the Language
two-letter code list and CC is from the Country two-letter code list, for example, en_US. To set the
values in the system, click Save.

License Manager
The License Manager gives another view of user licenses provided for applications within the system.
Select a radio button in the Products panel to see the names of individuals in the system with People
records and licenses authorizing them to use that product. Clicking the person name does not open
their corresponding People record.

Click Add Users to add individual users to a product or click Delete Users to remove the selected users
from a product. The Delete Users action prompts for confirmation before deleting a user. Additions and
deletions performed here also update the application.

Managed Processes
The Managed Processes provides the ability to stop a process that is consuming too much memory. It
currently checks only reporting processes based on BIRT, and uses the same memory threshold that is
configured in TRIRIGAWEB.properties.

When this threshold is met by a reporting process, the system tries to stop the process. The threshold
is periodically checked by polling the system during the execution. The frequency that the memory is
checked is also configurable in TRIRIGAWEB.properties.

This Managed Processes can help identify poor performing reports. When a report is stopped due to
lack of memory, details about the report will be logged. Note that just because a report fails does not
mean it is a poor performing report. It may have just been run when the system was low on resources.
However, if a report shows up in the log many times, it is very likely performance improvements can be
made to the report.

The Managed Processes page in the Admin Console shows all the reporting processes (based on BIRT)
currently running on the application server, and from which the admin console is accessed (it does not
show any reports being executed on a different process server). From this page you can also attempt to
stop the reporting process. This can be useful if a report has been executing for a long period of time
and you would like it to stop.

© Copyright IBM Corporation 2011. 13

Metadata Analysis
The Metadata Analysis panel contains tools used to assist in performing system-wide analysis on the
form, query, and workflow metadata in a system. Results of each analysis process are written to the
respective log file in the installation log folder (for example,
C:\Tririga\log\systemTest_com.tririga.platform.testGuiRendererTest.log). These
processes also may generate indirect WARN messages in the server.log. Review the WARN messages
in the server.log.

To initiate a process in the Metadata Analysis panel, click Start. If the process supports interruption,
click Stop to stop it. If the process does not support interruption, an In Progress status message
displays instead of a Stop button.

The Reports section contains reporting tools. None of the tools in the Reports section make changes to
the system. They perform the specified activity and write results to the appropriate log(s). All reports
support interruption and can be stopped before they complete.

 When the Render every tab on every GUI in the system tool runs, …
 When the Run all queries in the system tool runs, …
 When the Load all published workflow templates tool runs, …
 When the Generate BO Publish DDL for all Business Objects in the system tool runs, the system
writes the file systemTest_com.tririga.platform.test.BoPublishTest.log to the
IBM TRIRIGA log folder. The file contains the DDL that would be generated if every business
object in the system were to be republished.
 When the Generate BO Publish DDL for all Module views in the system tool runs, the system
writes the file systemTest_com.tririga.platform.test.ModuleViewGeneratorTest
.log to the IBM TRIRIGA log folder. The file contains the DDL that would be generated if
every module in the system were to be republished.
 Instantiate and execute every Crystal Report in the system runs all Crystal reports and logs any
errors that occur in the process. A “Corrupt report” error indicates that a report or form
references a Crystal Report that exists in the Document Management system but is missing its
backing business object instance. This could be resolved by re-uploading the report and re-
linking the form and report to that document.

The Cleanup Processes section contains processes that make safe modifications to fix corrupted
metadata. Even though the modifications are safe and should not adversely impact prior system
behavior, review the output of any Cleanup Process so you know what was impacted. The Workflow
template cleanup process and its output are discussed in detail in the IBM TRIRIGA Application
Platform 3 Installation and Implementation Guide in “Appendix A - Reviewing the WorkflowCleanup.log
File”.

 Note – The Workflow template cleanup process does not support interruption; once it is initiated, it
must run to completion.

© Copyright IBM Corporation 2011. 14

Performance Monitor
The Performance Monitor enables system administrators to monitor the occurrences of various tasks,
test the speed of the network, monitor a single value in the system, view the HTTP headers, and view
cache statistics.

Performance Monitoring Section

Click a link to go into that specific monitor.

Instrumentation (System Methods Timing)

The Instrumentation managed object shows an overview of performance counters, displaying the
number of occurrences of various tasks. Reset All resets all task counts to 0. Reset resets the count for
that specific task to 0. The data automatically updates based on the amount of time (in seconds) that
you enter in the Refresh Every _____ Seconds box. If you change the value, click Set.

VM Stat

VM Stat shows you the system performance in a specific virtual machine. The statistics include
processes running, memory, swaps, input and output information, and system and CPU performance.

You can also determine the refresh time in minutes and the number of rows to be included in the
statistics report.

 Attention – There is no VM stat for non-Linux servers. This option is available for IBM TRIRIGA
application servers running on Linux only.

Network Speed Throughput From Server to your PC

The Network Speed Throughput managed object tests the network speed from the server to the current
user desktop.

When you click Network Speed Throughput, you can see your throughput in kilobytes, and then
average comparison with other network structures.

Monitor a single value

Use Monitor a single value to interface with third-party monitoring and alerting tools. The monitor
provides you with a list of third-party monitoring tools, which you can click as hyperlinks on screen.
Special instructions on how to use those are also provided as a help grid on screen.

When you click one of the hyperlinked items, the system displays the count for that item.

View Headers and Request Parameters

Use View Headers and Request Parameters to troubleshoot Single Sign-On installations or view custom
HTTP headers a Web server may have injected.

© Copyright IBM Corporation 2011. 15

Cache Monitor

The Cache Monitor provides EHCache Statistics, which displays the number of elements, cache hits,
cache misses, and average get time for the caches in the system. The data automatically updates
based on the amount of time (in seconds) that you enter in the Refresh Every _____ Seconds box. If
you change the value, click Set.

Key Metrics Section

The Key Metrics section displays performance metrics for the server. The metrics are: Java use of CPU
(%), Java Memory (Used/Free/Total), Workflow Queue Count, Workflow Throughput per 1 minute,
Extended Formula Queue Count, Logged in User Count, and Cache Info
(Hits/ObjectCount/Misses/Ratio). Click Record to Log to save the current metrics to a log file for
future analysis. This log file is named systemmetrics.log.

Platform Logging
Platform Logging enables real-time debug-level logging for platform features. When you select an
option and click Apply, debug-level logging starts immediately. When you clear an option and click
Apply, debug-level logging stops immediately. Any changes made in this configuration file are in
memory. The system reverts to the log4j.xml configuration settings when the server is restarted.

Administrators can roll log files. Click the icon or select one of the Roll actions. The system renames
the current log file with the current date and time and begins entering new messages in a fresh file.

If you enable the Extended Formula Startup option after the system is already started, you can cause
the system to reload and log the startup information. Select the Cache Manager managed object and
click Extended Formula Cache, which refreshes that cache.

You can add your own custom logging categories. Add them in the CustomLogCategories.xml
configuration file located in the IBM TRIRIGA installation config folder. A typical path is
C:\Tririga\config\CustomLogCategories.xml.

An example of a customized CustomLogCategories.xml follows along with what the platform

logging area might look like after the changes.

© Copyright IBM Corporation 2011. 16

 Sample Customization in CustomLogCategories.xml

Platform Logging Using Sample Customization in the CustomLogCategories.xml Shown Above

The most common server.log error messages can be found in “server.log Error Messages” in this
guide.

Scheduler Manager
Scheduler Manager managed objects allow you to reset the number of future Scheduled Event records
created for events with no end date. The default values in the Scheduler Manager are specified as
follows:

 Daily: 100
 Weekly: 100

© Copyright IBM Corporation 2011. 17

  Monthly: 50
 Yearly: 10

You can change these values so that the number of recurrences matches the requirements of your
company. When you are satisfied with the values you specified, click Save.

System Manager
The System Manager provides access to the system properties files, contains a tool for encrypting
values to be used in the properties files, and shows detailed information about the operating system.

Data in the Property Files section can be viewed and/or edited. Click View to see a property file. Click
Edit to update the selected property file.

Selecting Lock System in the Lock System section disables any further sign ins. Administrators can lock
the IBM TRIRIGA system so object migrations and/or object publishing can be performed without other
users in the system. You must have administrators already logged into the system before locking the
system.

Use the Username and Password Encryption section if you want to encrypt the user names and
passwords for accessing external Brava! and Reserve servers. Enter the Value to be encrypted and click
Encrypt. Copy the Result and paste into the appropriate value in the properties files.

Data about the system is read-only.

 Note – If you change a property file, you must restart the Application Server.

Threads Manager
From this manager, the number of threads that are launched for this Application Server can be
controlled. The Maximum Threads column sets the number of threads that the agent cannot exceed.
The Count column displays the current number of threads given to an agent. The Count column is auto-
populated from the Database Manager.

 Note – A single thread requires one connection to the database.

Attention – Setting Maximum Threads to a large value can drastically slow performance of the
system. As a general rule, the Maximum Threads value for any agent should not be more than 2-3


times the core CPU count on the database.

For example, if the database has 2 Dual Core Xeon CPUs, the core CPU count is 4. In this example,
set Maximum Threads to no more than 8-12, but not for all agents. The WFAgent should be set that
high, while the other agents should be kept low, around 2-3 threads per agent.

Two options are available for making changes to the current settings:

© Copyright IBM Corporation 2011. 18

  To save the change and retain it to memory, make the change and click Set and Save.
 To save the change but not retain it to memory, make the change and click Set Only.

Users Manager
The Users Manager displays users currently signed in to IBM TRIRIGA. It also displays other data that is
taken specifically from the People record for that individual as well as showing the IP address of the
user sign in server.

To sign out a user or broadcast a message to a user, click the check box to the left of the user name
and click the desired action in the Users section bar. To display the product licenses provided to a user,
click on Licensed Products then click the user name on the left of the popup window.

The Users Manager shows multiple concurrent logins of users and their IP addresses. This helps identify
users before performing an administrative log off.

Workflow Agent Manager

The Workflow Agent Settings panel allows a member of the Admin Group to designate specific IBM
TRIRIGA application users for a workflow agent. The agent picks up and processes workflow events
published by its designated users. The same user can be designated to multiple workflow agents. The
system gives priority to users that have an agent configured for them.

When an agent is configured for specific users, it picks up valid user events in the following order:

Sequence of Valid User Events

5. If the agent is configured exclusively for one or more users, it picks up valid events for
those users only.

6. If the agent is configured for users non-exclusively, it picks up valid events for those users.
When there is not any such event, it picks up valid events for other users that do not have
a dedicated running agent.

7. If an agent is not configured for specific users, it picks up valid events for any user that is
not on the user list of any other agent.

Valid events are events that satisfy the following conditions:

 The event currently is not being processed.

 No other event is being processed for the same record.
 The event is not for a user that already has the maximum number of events being processed by
this agent (as configured in the WF_AGENT_MAX_ACTIVE_PER_USER property in
TRIRIGAWEB.properties).

Initially, the User List is empty. To add users, click Add Users. The system displays the existing users.
Select the check boxes of the users to be added and click OK. The name of each selected user shows in
the User List. Once users are designated to an agent, the agent only processes events that are
published by its designated users or by users not assigned to any other agent.

© Copyright IBM Corporation 2011. 19

Once there are users in the User List, the Restrict to User List action appears on the User List section
bar. Clicking this action prevents the agent from processing events posted by users not assigned to this
agent. The agent is exclusive to the assigned users.

Clicking the Do Not Restrict to User List action removes the restriction on the agent and the agent
processes events that are not only owned by its users but also owned by users that are not assigned to
any agent.

To remove a user from the User List, select the check box to the left of the user name and click Delete
Users. If all users are deleted, the system displays No user has been added. The agent picks up any
available events.

If the system has multiple workflow agents, the Settings for other Agents section shows a read-only list
of agents not running on the current Application Server.

The Run Workflows Triggered By Scheduled Events As property allows workflows that are triggered by
scheduled events to run with a user in the system so that any custom IBM TRIRIGA Connector for
Business Applications tasks can use that user to authenticate. The default value is Default User. To
enable this property, change to a specific user by selecting the user from the drop-down list and
clicking Save.

The Workflow Instance Recording property provides global control of workflow instance recording. The
drop-down list contains the same values as the WF_INSTANCE_SAVE property in the
TRIRIGAWEB.properties file plus an additional value to restore from TRIRIGAWEB.properties.
The setting takes effect when you click Save. It takes effect on the server from which the
Administrator Console is being accessed; it does not apply across servers. It stays in effect until
changed or the server is restarted. When the server is restarted, the setting reverts to what is set in
the WF_INSTANCE_SAVE property in TRIRIGAWEB.properties. The Workflow Instance Recording
can be set to the following options:

 Never
 As configured in the workflow
 As configured in the workflow (in production mode)
 Always
 Restore from TRIRIGAWEB.properties

Workflow Events
The Workflow Events manager displays data relating to workflow events. Click a link in the Show
Workflow Event Queue Statistics section and the result is displayed in the Workflow Events section.

Link Description

Total Events for a User The pending events for each user.

Types of Events Event types and the number of workflow events pending for each.

Types of Events for each For each user, displays the user, workflow event type, and the
User quantity pending.

© Copyright IBM Corporation 2011. 20

 Link Description

Oldest Event in Queue The event type and when it was put in the queue.

Currently Executing Events For each user, displays the user, workflow event type, and the
quantity pending.

The data automatically updates based on the amount of time (in seconds) that you enter in the
Refresh Every _____ Seconds box. If you change the value, click Apply.

Workflows Executing
The Workflows Executing Manager displays the workflows on the server accessed by the Administrator
Console, listing those suspended and those currently executing. In addition, the suspended list shows
suspended workflows system wide. This information enables an administrator to monitor workflow
execution.

To restart (resume) or delete a suspended workflow, click the check box to the left of the Instance and
click the Resume or Delete action on the Suspended Instances section bar. Once a workflow instance is
resumed, the instance appears in the list in the Running Instances section.

To stop (abort) or suspend a running workflow, click the check box to the left of the Instance and click
the Stop or Suspend action on the Running Instances section bar. When a workflow instance is
suspended, the instance appears in the list in the Suspended Instances section.

Not all workflows can be suspended. For example, a workflow within a DataConnect task is not
suspendable. Before attempting to suspend a workflow, look at the Suspendable column, which
indicates whether the workflow can be suspended. When suspending a called workflow, the system
suspends that workflow and any parent workflows; this is required in order to allow the workflow to be
resumed.

The information displayed for each workflow is:

Column Description

Instance The local instance ID of the running workflow.

PID The Persisted ID of the running workflow. This only has a value if the
workflow instance is saved for some reason.

User The user for which the workflow is executing.

Name The name of the workflow.

ID The workflow (definition) ID and version.

Module The module the workflow is for.

Object The Business Object the workflow is for.

© Copyright IBM Corporation 2011. 21

 Column Description

Action The ‘Action’ or ‘Event’ that caused the workflow to execute.

Children True if this workflow currently has child workflows executing.

Child Of The ID (local instance ID) of the workflow this workflow is a child of
(being executed from) or ‘None’ if this is a top-level workflow.

Total Time The amount of time in milliseconds this workflow instance has been
executing.

Time / Avg The amount of time this instance has been running compared to the
average time instances of this type have taken.

Current Step The type of the step that is currently executing and the label if it
has one.

PC Process Count, the number of times this step has been executed.

Suspendable Indicates whether the workflow can be suspended.

ASYNC Indicates whether the workflow is asynchronous.

To update the list based on what is currently executing on the server, click Refresh.

To stop a workflow, click the check box to the left of Instance, click Stop, and confirm your selection.

If you click OK, it sends a Stop (Abort) request to the server. If the workflow is still running, (it could
have finished already), it stops after completing the step that is currently executing. Therefore, if you
request that a workflow that is calling another workflow be stopped, it will wait until the called
workflow completes before stopping. Once stopped, the status of the workflow instance changes to
Aborted.

Support & Report

The Support & Report Manager facilitates access to IBM online Service Request support system or to
support over the phone by clicking the IBM Support in your country link and finding your customer
support number.

You can also click the tsupport@us.ibm.com email and send your enquiries directly to IBM support
staff.

© Copyright IBM Corporation 2011. 22

2. server.log Error Messages
The server.log file can be read by breaking the text down into segments.

2008-10-07 09:44:40,478 ERROR [STDERR](http-0.0.0.0-8001-25)

java.sql.BatchUpdateException: ORA-12899: value too large
for column "TRIRIGA"."T_TRITEST"."TRINAMETX" (actual: 765,
maximum: 700)

Date and Time

Log Type: ERROR, WARN, INFO, DEBUG
Area of System
Thread
Exception Header
Exception Text

server.log Segments

There are four log types you may see in the server.log file: An error, a warning, information only
messages, or debug messages. You can configure the level of information you see in this log by using
log4j for your server. See the Platform Logging section for information about dynamically enabling
real-time debug logging.

 Note – Because of the large volume of information you may encounter in a log, do not set logging to
debug level.

The segments described above may be followed by a Java stack trace. These lines in the server.log
file begin with at com.tririga…. The stack trace can, for the most part, be ignored by the users of
this document.

The following table includes information about many common items seen in the server.log. For each
entry, the first column shows the log type and exception header, the second contains a description of
the cause and a suggestion of how the exception may be resolved, and the third gives an example. The
examples do not include the dates or threads of the error logs because they vary based on the
operation executed when the exception was logged, but the text is color coded with the legend shown
above for each other segment.

Log Type: Details

Exception Header
(WFA:3340769 - 2289501 Resolution Area:
Associate:26451634)
Issue: This information can be included in any error.
Suggested Action: Decode the error snippet.
As seen in the Example:
(WFA: user_id – bo_id Action: wf_event_id):

USERID: 3340769 (user_credentials > user_id)

BO ID: 2289501 (ibs_spec > spec_id)
Event: On Associate
Event ID: 26451634 (wf_event > event_id)

© Copyright IBM Corporation 2011. 23

 Log Type: Details
Exception Header

To locate the info in the db:

select * from user_credentials where

user_id=3340769;
select * from ibs_spec where spec_id=2289501;
select * from wf_event where event_id=26451634;

If no rows are returned, try:

select * from wf_event_history where
event_id=26451634;
Example
(WFA:3340769 - 2289501 Associate:26451634)
DataConnect Errors See the Possible Errors section in the DataConnect chapter in
Application Building for the IBM TRIRIGA Application Platform
3: Data Management.
ERROR Resolution Area: Data Modeler
com.tririga.platform.metadata.Met Issue: A state is found in the metadata that has been removed
adataNotFoundException: No state from the system.
named '$$$' exists on this
Business Object: Suggested Action: In the Data Modeler, review the Business
Object in question. Revise and republish the Business Object to
synchronize the metadata.
As seen in the Example: In the Business Object
sqaTestBusinessObject in the module Test Module, the
state new is invalid.
Example
ERROR [com.tririga.design.web.process.smartrecord.SmartSectionActions]
com.tririga.platform.metadata.MetadataNotFoundException: No state named 'new' exists on
this Business Object:
BoImpl[name=cstTestBusinessObject,id=10003454,module=ModuleImpl[name=Test Module,id=21218]]
ERROR Resolution Area: User Training
Invalid Object Id specified for Issue: User clicked inside a window before the Java finished
dispatch. Object Id was null. loading.
Suggested Action: Users need to wait for the Java to load before
clicking inside a window.
Example
ERROR
[com.tririga.web.process.ProcessRouter]
Invalid Object Id specified for dispatch. Object Id was null.
ERROR DurationException: Years Resolution Area: Data Modeler
cannot be negative.
Issue: When the end date is subtracted from the start date in a
duration formula, either the end date is before the start date,
or the end date is null.
Suggested Action: Find the duration formula and look for the
start date and end date values.
Example
ERROR
[com.tririga.architecture.util.Duration]

© Copyright IBM Corporation 2011. 24

 Log Type: Details
Exception Header
EXCEPTION com.tririga.architecture.util.DurationException: Years cannot be negative.

INFO - Resolution Area: HTTP Protocol

[com.tririga.web.filter.Authentic
ationFilter] Issue: Some user process has caused an issue with IBM TRIRIGA
HTTP security, such as going directly to a link when no user has
logged in or navigating to a link when a session is expired.
Causes could include timeout or more than one person logging
in with that user account.
Suggested Action: Log back into the IBM TRIRIGA application
and try going through the steps that were being followed
before this error.
As seen in the Example: A request was made for
templateScriptsCached.jsp through some process but
somehow the user session expired and that page was no longer
accessible.
Example
INFO
[com.tririga.web.filter.AuthenticationFilter]
(http-0.0.0.0-8001-2) Error in AuthenticationFilter: requestURL
(/html/en/default/js/templateScriptsCached.jsp) is not part of the excluded filters,
userId is less than one, HttpRequestHeader=[host=localhost:8001, user-
agent=Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.8) Gecko/2009032609
Firefox/3.0.8, accept=*/*, accept-language=en-us,en;q=0.5, accept-
encoding=gzip,deflate, accept-charset=ISO-8859-1,utf-8;q=0.7,*;q=0.7, keep-alive=300,
connection=keep-alive,
referer=http://localhost:8001/html/en/default/common/sessionExpirationGeneral.jsp,
cookie=JSESSIONID=yWl4MJ9suRDqAFS7PLANFw**, ]

INFO (WFA:3340769 - 5712774 Resolution Area: Workflow Builder

cstProvisionalBooking:27648718)
No hit in cache for Workflow Issue: A workflow was retired but is still being called.
Template ID: 14313328. In order Suggested Action: Find workflow using ID in metaschema
to get the cache current, restart (select * from wf_lookup where wf_template_id='#####’;),
your app server. revise workflow, publish the workflow.
As seen in the Example: The Workflow Template ID indicates
which workflow is being called.
Example
INFO
[com.tririga.architecture.cache.WFCache]
(WFA:3340769 - 5712774 cstProvisionalBooking:27648718) No hit in cache for Workflow
Template ID: 14313328. In order to get the cache current, restart your app server.

java.sql.SQLException: Closed Resolution Area: Tririga-ds.xml

Connection
Issue: Oracle dropped connection.
Suggested Action: Add the element to the right to each data
source in the tririga-ds.xml.
As seen in the Example: Workflow ID 10328588 version 3, task
Modify Records, has an invalid section map for the section
Team Members into the Capital Project Business Object in the

© Copyright IBM Corporation 2011. 25

 Log Type: Details
Exception Header
Project Module.
Example
ERROR:
java.sql.SQLException: Closed Connection

To correct the connection closed issue, add the element below to each of the data sources in the tririga-ds.xml located
in the "...\jboss-4.0.0\server\all\deploy\" directory. This change should be a made to all four data sources listed in the
tririga-ds.xml file.

Oracle:
<check-valid-connection-sql>select 1 from dual</check-valid-connection-sql>

SQL Server:
<check-valid-connection-sql>select 1</check-valid-connection-sql>

You also need to make sure you have a value greater than 0 set for the <min-pool-
size>; for example, <min-pool-size>10</min-pool-size>

WARN Resolution Area: Data Modeler

A dependency of this field could
not be found: Issue: A formula on a Business Object is malformed.
Suggested Action: Identify the Business Object and Field,
update the formula in Data Modeler, and re-publish the
Business Object.
As seen in the Example: The formula for the field
triContractPaymentsNU, on Business Object
triRealEstateContract, in Module triContract will not
evaluate.
Example
WARN
[com.tririga.platform.metadata.domain.BoImpl]
A dependency of this field could not be found:
BoFieldImpl[name=triContractPaymentsNU,id=2373,Section=BoSectionImpl[name=RecordInformatio
n,id=BoSectionId[categoryId=1,subCategoryId=8],Business
Object=BoImpl[name=triRealEstateContract,id=10002490,module=ModuleImpl[name=triContract,id
=21]]]][MID-3164363956]
WARN Resolution Area: Data Modeler
Applying default formula. Could
not parse formula for field: Issue: A formula on a Business Object is malformed.
Suggested Action: Identify the Business Object and Field,
update the formula in Data Modeler, and re-publish the
Business Object.
As seen in the Example: The formula for the field
triFasbPVofRentNU, on Business Object
triRealEstateContract, in Module triContract will not
evaluate.
Example
WARN
[com.tririga.platform.metadata.domain.BoFieldImpl]
Applying default formula. Could not parse formula for field:
BoFieldImpl[name=triFasbPVofRentNU,id=2375,Section=BoSectionImpl[name=RecordInformation,id
=BoSectionId[categoryId=1,subCategoryId=8],Business
Object=BoImpl[name=triRealEstateContract,id=10002490,module=ModuleImpl[name=triContract,id

© Copyright IBM Corporation 2011. 26

 Log Type: Details
Exception Header
=21]]]][MID-2514886854]
WARN Resolution Area: Workflow Builder
Call workflow task encountered Issue: A workflow is called where the workflow does not exist
error. or is not currently published.
Suggested Action: Review the calling workflow and see if the
step is still necessary, or find out why the called workflow is
missing. Make sure the called workflow is currently published.
Revise and republish the necessary workflow(s).
Example
Call workflow task encountered error. Task: TaskStep:
Call Workflow(38) WFTID=19118076.14 TSID=205820
Label='Call a Subflow' EventAction='',
Calling WF: ID: 19118075 Version: published,
Exception:
com.tririga.platform.workflow.template.exception.WFTemplateLoadingException:
Problem loading Workflow Template for ID: 19118075 Version: published.
...
Caused by:
com.tririga.platform.workflow.template.exception.WFTemplateNotFoundException:
Workflow template not found in lookup table for ID: 19118075
...
Caused by: org.springframework.dao.EmptyResultDataAccessException:
Incorrect result size: expected 1, actual 0

WARN Resolution Area: Workflow Builder

CANNOT REVERSE PREVIOUS Issue: An application is attempting to use the financial
TRANSACTIONS: This financial transaction functionality to reverse previous financial
transaction, 13119972, is not transactions, and a Financial Reference Object is not
associated to an object so no associated to the record to find previous transactions to
previous transactions can be reverse.
reversed.
Suggested Action: Review the process and ensure that at the
time the financial transaction is being processed it has a
Financial Reference Object.
As seen in the Example: The financial transaction record
13119972 does not have a Financial Reference Object.
Example
WARN
[com.tririga.platform.finance.service.FinanceServiceImpl]
(WFA-2.5:1837189 - 13119943 De-Associate:14821223 IE=14821223) CANNOT REVERSE PREVIOUS
TRANSACTIONS: This financial transaction, 13119972, is not associated to an object so no
previous transactions can be reversed.

WARN Resolution Area: Data Modeler

Could not evaluate formula for
Issue: A formula on a Business Object is malformed.
field so leaving field value as
is. Caused by: Could not evaluate Suggested Action: Identify the Business Object and Field,
formula for field: update the formula in Data Modeler, and re-publish the
Business Object.

© Copyright IBM Corporation 2011. 27

 Log Type: Details
Exception Header
As seen in the Example: The formula for the field
triContractPaymentsNU, on Business Object
triRealEstateContract, in Module triContract will not
evaluate because one of the fields used as a variable
(triFaBusDiscountRateNU) does not exist.
Example
WARN [com.tririga.platform.smartobject.domain.field.AbstractSmartObjectField]
Could not evaluate formula for field so leaving field value as is. Caused by: Could not
evaluate formula for field:
BoFieldImpl[name=triContractPaymentsNU,id=2373,Section=BoSectionImpl[name=RecordInformatio
n,id=BoSectionId[categoryId=1,subCategoryId=8],Business
Object=BoImpl[name=triRealEstateContract,id=10002490,module=ModuleImpl[name=triContract,id
=21]]]] for formula: ExtendedFormula[Formula String=(A+B)/(1+C/100)] Caused by: Requested
field does not exist on Business Object. Section: RecordInformation Field:
triFaBusDiscountRateNU[MID-3605630256]

WARN Resolution Area: Report Manager

Could not parse parameter in Issue: An extended formula is trying to use a query to resolve a
formula: parameter, but the query or field in the query could not be
found.
Suggested Action: Add the query and/or the field to the query.
As seen in the Example: An extended formula is attempting to
use query triInvoiceLineItem - Advanced Formula - triPaid -
Associated to Current Record, field triNewInvTotalNU.
Example
WARN [com.tririga.platform.smartobject.util.formula.ExtendedFormulaParser]
Could not parse parameter in formula:
ExtendedFormulaDefnImpl[Formula=b,Parms={b=ExtendedFormulaParmDefnImpl[Name=b,Value=[
QUERY][{triCostItem}{triInvoiceLineItem}{triInvoiceLineItem - Advanced Formula -
triPaid - Associated to Current Record
}][{RecordInformation}{triNewInvTotalNU}]]}][MID-2164297393]

WARN Resolution Area: Workflow Builder

Error evaluating condition Issue: Switch conditions cannot be loaded because they are
expression - returning FALSE. invalid.
Suggested Action: Revise the workflow, review the conditions
and update them. Republish the Workflow.
As seen in the Example: The workflow cstBidDocument -
onChange - Update UOM has an invalid Switch condition.
Example
WARN [com.tririga.platform.workflow.runtime.condition.Condition]
Error evaluating condition expression - returning FALSE.
Condition[ID=55383,Expr='substring (p0 , 10 , 10 ) == "A" || substring (p1 , 10 , 10
) == "H" || substring (p2 , 10 , 10 ) == "G" || substring (p3 , 10 , 10 ) ==
"L"',Parameters=[p0 = , p1 = , p2 = , p3 = ]]. Workflow Info:
WFTemplateImpl.WFTemplateRO[ID=18749944,Version=2,Name=cstBidDocument - onChange -
Update UOM], TaskStep:
WFTaskStepImpl.WFTaskStepRO[135720,,Switch,14,WFTemplateImpl.WFTemplateRO[ID=18749944
,Version=2,Name=cstBidDocument - onChange - Update UOM]][MID-739830450]

WARN Resolution Area: Data Modeler/Form Builder

Error getting field for SO - Issue: Cannot load fields for a Business Object because the

© Copyright IBM Corporation 2011. 28

 Log Type: Details
Exception Header
field not found. field metadata does not exist. A Business Object has a field
defined for it, but that field does not exist in the system.
Suggested Action: Remove the field from the Business Object.
Review all mappings/Forms for that Business Object. Revise
and republish the necessary objects.
As seen in the Example: The Business Object
triCommunicationRecord has a field cstMatchedSAMTX that
is invalid.
Example
WARN [com.tririga.design.smartobject.dataaccess.SmartObjectAttributeDAOAnsi]
Error getting field for SO - field not found. Section='RecordInformation'
Field='cstMatchedSAMTX' From SO ID='4895427' name='null' BO
name='triCommunicationRecord' id=10004546, Module id=20820 [MID-3333779126]

WARN Resolution Area: Currency Conversion

Error in Conversion from >$$$< to Issue: Currency conversion is being performed where the
>$$$< . Using conversion rate of conversion is not defined.
1.
Suggested Action: Set up the conversion rates for the
currencies in question.
As seen in the Example: A record is being saved for Business
Object triStandardContract in Module triContract. The
field triCommitmentOriginalRollupFR is attempting to save
a value that requires a currency conversion from US Dollars to
Canadian Dollars and there is not a conversion for the appropriate
time period in the system.
Example
WARN
Error in Conversion from >US Dollars< to >Canada Dollars< . Using conversion rate of
1.
For field: FinancialRollupField[Name: triCommitmentOriginalRollupFR,Raw Value: 0,
Type: BoFieldImpl[name=triCommitmentOriginalRollupFR,id=1165,

Section=BoSectionImpl[name=RecordInformation,id=BoSectionId[categoryId=1,subCategoryId=8],
Business Object=BoLazyLoadingProxy[name=triStandardContract,id=10002384,
module=ModuleImpl[name=triContract,id=21]]]]]
WARN Resolution Area: Data Modeler / Form Builder
Error processing GUI Metadata Issue: Form field does not exist for a Form mapping or a Form
mapping. mapping references a field on a Business Object that does not
exist.
Suggested Action: To remove the field from the Form mapping,
Revise and republish the Form. If there are multiple Forms for
a Business Object, review the workflow and ensure the
business process is being followed for the proper Forms.
As seen in the Example: The Workflow cstTicket -
Synchronous - OnChange Type, during Task Do Not
Require Steps to Reproduce, is failing to update the Form
when it is executing against Form HelpDeskTicket because the
field Steps to Reproduce does not exist on that Form.
Example
WARN [com.tririga.platform.workflow.template.guimetamap.GUIFieldMap]

© Copyright IBM Corporation 2011. 29

 Log Type: Details
Exception Header
Error processing GUI Metadata mapping. WFTaskStepImpl.WFTaskStepRO[137224,Do Not Require
Steps to Reproduce,Modify
Metadata,23,WFTemplateImpl.WFTemplateRO[ID=14565895,Version=5,Name=cstTicket - Synchronous
- OnChange Type]].
MapEntryBase[mapId=137224,wfTemplateId=14565895,wfTemplateVersion=5,guiTabName=NewGeneral,
guiSectionName=General,guiFieldName=Steps to
Reproduce,propertyValue=false,taskMapData=<null>,initialized=true]. Caused by:
com.tririga.platform.metadata.MetadataException: No field id found with name: Steps to
Reproduce. Section: General Tab: NewGeneral GUI Name: HelpDeskTicket[MID-1004518520]

WARN Resolution Area: Data Modeler

Failed to obtain a list of Issue: The Report Manager has the capability to run Metric
triMetricCategory from Reports, but the application does not include the Business
application metadata repository. Objects required to support the functionality.
This error indicates the platform
version is ahead of the Suggested Action: At the time you would like to implement IBM
application version. The system TRIRIGA Workplace Performance Management, upgrade the
is expecting the new metadata application to 9.6 or higher. If you are not using IBM TRIRIGA
structure that does not exist in WORKPLACE PERFORMANCE MANAGEMENT, this warning can be
the current application version. ignored.
As seen in the Example: N/A
Example
WARN [html.en.default.reportTemplate.reportTemplateDesc]
Failed to obtain a list of triMetricCategory from application metadata repository. This
error indicates the platform version is ahead of the application version. The system is
expecting the new metadata structure that does not exist in the current application
version.[MID-2565267038]
WARN Resolution Area: Form Builder
Gui field has a different field Issue: A Form has a field that no longer exists.
type than backing bo. Using field
type of BO. Suggested Action: Identify the Forms for the Business Object
that use the Field listed, revise the Form, remove the Field in
Form Builder from the tree view of the Form layout, re-add the
Field to the Form and publish the Form.
As seen in the Example: The field Note, on Business Object
triBSIFailureImpactA, is identified as a Text field in a Form
but another field type in the Data Modeler.
Example
ARN [com.tririga.platform.error.ErrorHandler]
Gui field has a different field type than backing bo. Using field type of BO.
BO=[name =triBSIFailureImpactA, id=10003740] FieldType=[BoField=Note,
GuiFieldType=Text][MID-4251286743]
WARN Resolution Area: Workflow Builder
Mapping into the target field is Issue: A field is being mapped into a live link section. Only the
not allowed because the field is
section mapping is considered for a live link section.
within a Live Link section.
Suggested Action: Revise the workflow, open the task, open
the workflow map, clear the field map for the live link section,
and save workflow map. Publish the workflow.
As seen in the Example: Workflow ID 10014934 version 17 has
an invalid section map to the Business Object Line Item
Summary History for the section RecordedBy.
Example

© Copyright IBM Corporation 2011. 30

 Log Type: Details
Exception Header
WARN [com.tririga.platform.workflow.template.sofieldmap.MapEntry]
Mapping into the target field is not allowed because the field is within a Live Link
section. The mapping is being discarded.MEFieldToField[MapEntry Field-to-
Field,Type=10,SrcField=1037,TgtField=1037,Map=SOFieldMapImpl.SOFieldMapRO[ID=1968,WFTempla
te=10014934.17]]. TARGET:
BoFieldImpl[name=StateProv,id=1037,Section=BoSectionImpl[name=RecordedBy,id=BoSectionId[ca
tegoryId=1,subCategoryId=7],Business Object=BoImpl[name=Line Item Summary
History,id=10000072,module=ModuleImpl[name=Line Item,id=27]]]][MID-3898920414]

WARN Resolution Area: Data Modeler

Name of object being saved Issue: Attempted to save a record that has the same unique
conflicts with existing object. name as an existing record.
Name: ''.
Suggested Action: Identify the Business Object that is having
conflicts and validate the unique identifier used as the mapped
name is valid. If not, update the mapped name and republished
the business object (NOTE, this will not change the names of
existing records). Review workflows that create records for the
business object and ensure that the proper data is mapped into
the create task for the record to be uniquely identified when
the record is created.
As seen in the Example: A record for the Business Object
cstBidDocument in Module Bid is being saving with a name of
’’.
Example
WARN [com.tririga.platform.smartobject.service.BaseSmartObjectService]
Name of object being saved conflicts with existing object. Name: ''. Existing object:
SmartObjectImpl[ID=10650471,Business
Object=BoImpl[name=cstBidDocument,id=10003095,module=ModuleImpl[name=Bid,id=35]]] New
object being saved: SmartObjectImpl[ID=13120040,Business
Object=BoImpl[name=cstBidDocument,id=10003095,module=ModuleImpl[name=Bid,id=35]]][MID-
317597477]
WARN Resolution Area: Data Modeler
No BO Mapping
Issue: A Business Object has been defined that may not be in a
(IBS_SPEC_TYPE_FIELD_MAP) found
valid published state.
for BO:
Suggested Action: Identify the Business Object, re-publish the
Business Object.
As seen in the Example: The Business Object Inbox Folder in
the Mail module.
Example
WARN [com.tririga.platform.metadata.dataaccess.BoDaoImpl]
No BO Mapping (IBS_SPEC_TYPE_FIELD_MAP) found for BO: BoImpl[name=Inbox
Folder,id=103516,module=ModuleImpl[name=Mail,id=17]] This is typically required in order
for a BO to be published.[MID-1159340835]
WARN Resolution Area: Data Modeler
Not adding field with name '$$$' Issue: A Business Object has a field that is not tied to a
to section : Database column.
Suggested Action: Identify the Business Object and field, revise
and re-publish the Business Object.
As seen in the Example: The Business Object Bid Response
Analysis Line Item has an issue with the field
DM_FILE_NAME in section Documents.
Example

© Copyright IBM Corporation 2011. 31

 Log Type: Details
Exception Header
WARN [com.tririga.platform.metadata.dataaccess.BoDaoImpl]
Not adding field with name 'DM_FILE_NAME' to section :
BoSectionImpl[name=Documents,id=BoSectionId[categoryId=2,subCategoryId=1],Business
Object=BoImpl[name=Bid Response Analysis Line Item,id=10000045,module=ModuleImpl[name=Line
Item,id=27]]] Reason: Field, 'DM_FILE_NAME' is not backed by a database field.[MID-
1778354461]

WARN Resolution Area: Form Builder

Not adding field, '$$$', to GUI
Issue: A Form has a field that no longer exists.
Section because backing Business
Object field does not exist: Suggested Action: Identify the Form and field, revise the Form,
remove the field in Form Builder from the tree view of the
Form layout, re-add the field to the Form, and publish the
Form.
As seen in the Example: The field Active Start Date, on GUI
Key, Tab: General, Section: KeySpecification is invalid.
Example
WARN [com.tririga.platform.metadata.dataaccess.GuiMetadataDaoImpl]
Not adding field, 'Active Start Date', to GUI Section because backing Business Object
field does not exist:
GuiSectionMetadataImpl[Name=KeySpecification,ID=11,GUI
Tab=GuiTabMetadataImpl[Name=General,ID=1,GUI=GuiMetadataImpl[Name=Key,ID=10000083]]][MID-
1871134927]

WARN Resolution Area: Report Manager

Not using invalid query filter:
Issue: A Query has a filter for a field that does not exist.
Suggested Action: Identify the Query and filter, remove the
filter in Report Manager, and save the Query.
As seen in the Example: The filter for the field triPaidDA, on
Query triPaymentLineItem - Display - Received Accounts
Receivable records associated as Has Payment, in Module
triCostItem is invalid.
Example
WARN [com.tririga.platform.metadata.dataaccess.BoQueryMetadataDaoImpl]
Not using invalid query filter:
BoQueryFilterMetadataImpl[Left side section=RecordInformation,Left side
field=triPaidDA,Operator=Equals,Right side
value=$$RUNTIME$$,Query=BoQueryMetadataImpl[ID=19845,Name=triPaymentLineItem - Display -
Received Accounts Receivable records associated as Has Payment,Module=triCostItem]] Caused
by: No field named 'triPaidDA' exists on this Business Object in the general sections:
BoImpl[name=triPaymentLineItem,id=10004638,module=ModuleImpl[name=triCostItem,id=27]][MID-
2170122156]

WARN Resolution Area: Data Modeler

The UOM Source for this field is
not UOM Managed. This field: Issue: A field has been identified to have a Unit of Measure
source field, but the source field does not store Units of
Measure.
Suggested Action: Identify the Business Object and Field,
update the UOM Source in Data Modeler, and re-publish the
Business Object.
As seen in the Example: The formula for the field
triDefaultCapacityNU, on Business Object triSpace, in
Module Location will not evaluate because one of the fields

© Copyright IBM Corporation 2011. 32

 Log Type: Details
Exception Header
used as a source UOM (triCapacityNU) does not store UOM.
Example
WARN
[com.tririga.platform.metadata.domain.BoFieldImpl]
The UOM Source for this field is not UOM Managed. This field:
BoFieldImpl[name=triDefaultCapacityNU,id=1188,Section=BoSectionImpl[name=RecordInformation
,id=BoSectionId[categoryId=1,subCategoryId=6],Business
Object=BoImpl[name=triSpace,id=10002873,module=ModuleImpl[name=Location,id=6]]]] UOM
Source Field:
BoFieldImpl[name=triCapacityNU,id=1119,Section=BoSectionImpl[name=RecordInformation,id=BoS
ectionId[categoryId=1,subCategoryId=6],Business
Object=BoImpl[name=triSpace,id=10002873,module=ModuleImpl[name=Location,id=6]]]][MID-
276069112]

WARN Resolution Area: Data Modeler

triThreshold Business Object does Issue: The Report Manager has the capability to run Metric
not exist. Reports, but the application does not include the Business
Objects required to support the functionality.
Suggested Action: At the time you would like to implement IBM
TRIRIGA Workplace Performance Management, upgrade the
application to 9.6 or higher. If you are not using IBM TRIRIGA
WORKPLACE PERFORMANCE MANAGEMENT, this warning can be
ignored.
As seen in the Example: N/A
Example
WARN
[html.en.default.reportTemplate.reportTemplateDesc]
triThreshold Business Object does not exist.[MID-75369837]

WARN Resolution Area: Data Modeler / Workflow Builder

Trouble setting the locator field Issue: The Data Modeler is using a field for a locator that is
because the locator metadata is different than the field that is being mapped into the field in a
invalid; setting with the linked workflow.
object's name instead.
Suggested Action: Review the field used in the Data Modeler
for the locator to ensure the proper mapping. Update if
necessary and republish the mapping. NOTE, locator fields are
sometimes used for multi-object mappings and this warning
may be seen in this scenario and can be ignored.
As seen in the Example: The Business Object Notification in
Module Mail had a locator with the name RefObject mapped to
the locator’s linked record name instead of the identified field
from the Data Modeler. This warning could be ignored.
Example
WARN
[com.tririga.platform.smartobject.domain.field.LocatorField]
(WFA-2.5:1837189 - 13119943 APPROVE_HIDDEN:14821226 IE=14821226)
Trouble setting the locator field because the locator metadata is invalid; setting with
the linked object's name instead. Locator field:
BoFieldImpl[name=RefObject,id=1021,Section=BoSectionImpl[name=AdditionalDetail,id=BoSectio
nId[categoryId=1,subCategoryId=6],Business
Object=BoImpl[name=Notification,id=107324,module=ModuleImpl[name=Mail,id=17]]]][MID-
1263122157]

© Copyright IBM Corporation 2011. 33

 Log Type: Details
Exception Header

WARN Resolution Area: Data Modeler

UOM Source for field does not Issue: A field has a source UOM field defined, but the source
exist: field cannot be found.
Suggested Action:
Review the field in question and ensure that the proper UOM
definitions are put in place. Revise and republish the Business
Object.
As seen in the Example:
The field triLtBrokerageCommissionNU, on Business Object
triAssetLease in module triContract has an invalid UOM
source.
Example
WARN
[com.tririga.platform.metadata.domain.BoFieldImpl]
UOM Source for field does not exist:
BoFieldImpl[name=triLtBrokerageCommissionNU,id=1560,Section=BoSectionImpl[name=RecordInfor
mation,id=BoSectionId[categoryId=1,subCategoryId=8],Business
Object=BoImpl[name=triAssetLease,id=10008550,module=ModuleImpl[name=triContract,id=21]]]]
This is being allowed for backward compatibility, but will likely cause issues in further
processing. The Business Object Field should be fixed to point to a valid UOM Source.[MID-
769296686]

WARN Resolution Area: Workflow Builder

Workflow SmartObject field Issue: A field or section in a workflow field mapping does not
mapping. exist on the underlying Business Object.
Suggested Action: Revise the Workflow, open the task, open,
review and save workflow map. Publish the workflow.
As seen in the Example: Workflow ID 10328588 version 3, task
Modify Records, has an invalid section map for the section
Team Members into the Capital Project Business Object in
the Project Module.
Example
WARN
[com.tririga.platform.workflow.template.sofieldmap.SOFieldMapImpl]
Workflow SmartObject field mapping.
MEObjectToSection[MapEntry Object-to-
Section,Type=30,TgtSectionCatagory=12,TgtSectionSubCatagory=1,TgtField=1,Map=SOFieldMapImpl.SOField
MapRO[ID=10853,WFTemplate=10328588.3]]. Mapping FROM: BoImpl[name=External
Contact,id=106849,module=ModuleImpl[name=People,id=7]], TO: BoImpl[name=Capital
Project,id=107010,module=ModuleImpl[name=Project,id=19]]. TaskStep: Modify Records(28)
WFTID=10328588.3 TSID=133061 Label='Modify Records' EventAction='Append'. Cause:
com.tririga.platform.metadata.MetadataNotFoundException: No section with name 'Team Members' exists
on this Business Object: BoImpl[name=Capital
Project,id=107010,module=ModuleImpl[name=Project,id=19]][MID-3776864463]
WARN Resolution Area: Workflow Builder
Workflow task handler error while Issue: A state transition is performed when it is not valid for
triggering action the current state of the record on which the workflow is
executing.
Suggested Action: Review the Business Object in question and

© Copyright IBM Corporation 2011. 34

 Log Type: Details
Exception Header
check that the action/transition is still there. If the state
transition is not there, you may want to add the state
transition, revise and republish the Business Object. If the
state transition is there, it may be a case where the workflow
is called on a record that is not in an appropriate state for this
transition to occur. Review your processes to ensure that
records are in the proper state before the Workflow executes.
As seen in the Example: In Workflow xxx, Task
cstCalculateEnd, the workflow is trying to execute state
transition cstCalculateEnd but it is not a valid transition from
the current state of the record.
Example
WARN
Workflow task handler error while triggering action 'cstCalcuateEnd'.
TaskStep: Trigger Action(31) WFTID=16680680.10 TSID=138571 Label='cstCalculateEnd'
EventAction='cstCalcuateEnd'.
Cause: com.tririga.platform.metadata.MetadataNotFoundException:
No transition exists on this Business Object from current state
'BoStateImpl[Name=triActive,Business
Object=BoImpl[name=cstTimeCalculator,id=10005047,
module=ModuleImpl[name=triHelper,id=21720]]]'
with transition name of 'cstCalcuateEnd'.
Available transitions out of this state are the following: …… [
BoStateTransitionImpl[ID=BoStateTransitionId[
WARN Resolution Area: None
ClassNotFoundException Issue: When JBoss starts up, the IBM TRIRIGA software tries to
reload the old sessions; however, the ear file has not yet
loaded, so it cannot find UserSessionHelper.
Suggested Action: None needed. This is harmless and to be
expected.
Example
WARN
[com.tririga.web.common.UserSessionHelper java.lang.ClassNotFoundException:
com.tririga.web.common.UserSessionHelper]
WARN Resolution Area: Data Modeler
Expression is missing for . boId Issue: An extended formula is indicated but not defined or a
= ###### Field = #### variable is not defined.
Suggested Action: Use the SQL below to identify the business
object and field. Update and publish.
As seen in the Example: Use this SQL to find out what field the
atr_seq is:
select * from ibs_spec_type where spec_template_id=######;
[BOID]
[will tell you what business object it is]

select * from sobjtype_fields where spec_template_id=###### and

atr_seq=####;
[will tell you which field it is]

© Copyright IBM Corporation 2011. 35

 Log Type: Details
Exception Header
Example
WARN
[com.tririga.architecture.util.FormulaEngine]
Expression is missing for . boId = ###### Field = ####
WARN This is logged during a publish. The INFO, WARN, DEBUG in the
Adding DB column, triTesting, log entry indicate what needs to be enabled in order for that
since it does not exist and the entry to exist.
BO expects it to be there. As seen in the Example: The example to the right shows logging
that occurs during a publish.
To see the DEBUG events, enable the Business Object Publish
option on the Administrator Console’s Platform Logging managed
object. Be sure this is done on the server where the BO Publish
Agent is running.
Example

-04 13:44:23,037 INFO [com.tririga.platform.metadata.service.BoPublishService](Thread-17) Publish started for

Business Object: BoImpl[name=testBo,id=10043142,module=ModuleImpl[name=testModule,id=26323]]
2008-12-04 13:44:23,083 WARN [com.tririga.platform.metadata.service.BoPublishService](Thread-17) Adding DB
column, triTesting, since it does not exist and the BO expects it to be there. Bo Field:
BoFieldImpl[name=triTesting,id=1001,Section=BoSectionImpl[name=General,id=BoSectionId[categoryId=1,subCategoryId
=1],Business Object=BoImpl[name=testBo,id=10043142,module=ModuleImpl[name=testModule,id=26323]]]]
2008-12-04 13:44:23,083 DEBUG [com.tririga.platform.metadata.service.BoPublishService](Thread-17) DDL Built:
Sql[SQL=ALTER TABLE T_TESTBO ADD (TRITESTING VARCHAR(150))] for Business Object:
BoImpl[name=testBo,id=10043142,module=ModuleImpl[name=testModule,id=26323]]
2008-12-04 13:44:23,755 INFO [com.tririga.platform.metadata.service.BoPublishService](Thread-17) Publish completed
for Business Object: BoImpl[name=testBo,id=10043142,module=ModuleImpl[name=testModule,id=26323]]
2008-12-04 13:44:23,771 INFO [com.tririga.platform.metadata.service.BoPublishService](Thread-17) Publish started for
Module: ModuleImpl[name=testModule,id=26323]
2008-12-04 13:44:23,927 DEBUG [com.tririga.platform.metadata.service.BoPublishService](Thread-17) Union BO in to
view: BoImpl[name=testBo,id=10043142,module=ModuleImpl[name=testModule,id=26323]]
2008-12-04 13:44:23,927 DEBUG [com.tririga.platform.metadata.service.BoPublishService](Thread-17) Union BO in to
view: BoImpl[name=testModule,id=10019042,module=ModuleImpl[name=testModule,id=26323]]
2008-12-04 13:44:23,927 DEBUG [com.tririga.platform.metadata.service.BoPublishService](Thread-17) DDL Built:
Sql[SQL=DROP VIEW M_TESTMODULE] for Module: ModuleImpl[name=testModule,id=26323]
2008-12-04 13:44:23,927 DEBUG [com.tririga.platform.metadata.service.BoPublishService](Thread-17) DDL Built:
Sql[SQL=CREATE VIEW M_TESTMODULE AS SELECT SPEC_ID SPEC_ID, SYS_PROJECTID SYS_PROJECTID, SYS_OBJECTSTATE
SYS_OBJECTSTATE, SYS_OBJECTID SYS_OBJECTID, SYS_GUIID SYS_GUIID, Sys_OrgName Sys_OrgName,
Sys_OrgNameObjId Sys_OrgNameObjId, Sys_ModifiedTime Sys_ModifiedTime, Sys_PriorState Sys_PriorState,
Sys_CreatedBy Sys_CreatedBy, LastName LastName, Sys_GeographyName Sys_GeographyName,
Sys_GeographyNameObjId Sys_GeographyNameObjId, Sys_GeographyId Sys_GeographyId, Sys_Type Sys_Type1,
Sys_ReviewStatus Sys_ReviewStatus, Sys_ModifiedBy Sys_ModifiedBy, triControlNumberCN triControlNumberCN,
Sys_Parent Sys_Parent1, Sys_OrganizationId Sys_OrganizationId, Sys_CreatedTime Sys_CreatedTime, Sys_LocationName
Sys_LocationName, Sys_LocationNameObjId Sys_LocationNameObjId, triTesting triTesting, Sys_LocationId
Sys_LocationId FROM T_TESTBO UNION ALL SELECT SPEC_ID SPEC_ID, SYS_PROJECTID SYS_PROJECTID,
SYS_OBJECTSTATE SYS_OBJECTSTATE, SYS_OBJECTID SYS_OBJECTID, SYS_GUIID SYS_GUIID, Sys_OrgName Sys_OrgName,
Sys_OrgNameObjId Sys_OrgNameObjId, Sys_ModifiedTime Sys_ModifiedTime, Sys_PriorState Sys_PriorState,
Sys_CreatedBy Sys_CreatedBy, LastName LastName, Sys_GeographyName Sys_GeographyName,
Sys_GeographyNameObjId Sys_GeographyNameObjId, Sys_GeographyId Sys_GeographyId, Sys_Type1 Sys_Type1,
Sys_ReviewStatus Sys_ReviewStatus, Sys_ModifiedBy Sys_ModifiedBy, triControlNumberCN triControlNumberCN,
Sys_Parent1 Sys_Parent1, Sys_OrganizationId Sys_OrganizationId, Sys_CreatedTime Sys_CreatedTime,
Sys_LocationName Sys_LocationName, Sys_LocationNameObjId Sys_LocationNameObjId, triTesting triTesting,
Sys_LocationId Sys_LocationId FROM T_TESTMODULE] for Module: ModuleImpl[name=testModule,id=26323]
2008-12-04 13:44:24,037 INFO [com.tririga.platform.metadata.service.BoPublishService](Thread-17) Publish completed

© Copyright IBM Corporation 2011. 36

 Log Type: Details
Exception Header
for Module: ModuleImpl[name=testModule,id=26323]
2008-12-04 13:44:24,037 INFO [com.tririga.platform.metadata.bopublish.BoPublishAgent](Thread-17)
Sending notification to user: [221931] Message: [Publication of testBo completed with warning(s).]

WARN Resolution Area: Data Modeler

com.tririga.platform.smartobject.
InvalidFieldRequestException: No Issue: An application is attempting to utilize the scheduling
field named 'triTimeZonesCL' custom tasks in workflow, but the calling Business Object does
exists on this Business Object in not have the field triTimeZonesCL, which is required to
the general sections: properly utilize the functionality.
Suggested Action: Revise the identified Business Object and
add the field triTimeZonesCL.
As seen in the Example: The Business Object
cstTimeCalculator in module triHelper is missing field
triTimeZonesCL.
Example
WARN [com.tririga.architecture.web.process.reserve.ReserveUtils]
com.tririga.platform.smartobject.InvalidFieldRequestException: No field named
'triTimeZonesCL' exists on this Business Object in the general sections:
BoImpl[name=cstTimeCalculator,id=10005047,module=ModuleImpl[name=triHelper,id=21720]]
WARN Resolution Area: Data Modeler
No value found in single lookup Issue: An HTML Form Report attempted to access a field that
does not exist on the underlying Business Object.
Suggested Action: Edit the HTML Form, look for the Section and
Field name referenced in the error, and correct the field.

The WARN in the server.log will have translated the

%%SECTION_FIELD%% contained in the HTML into
//Project-Project-RecordedBy//PeopleFullName
Example
WARN
No value found in single lookup using XPathExpr: '//Project-Project-
RecordedBy//PeopleFullName'

WorkflowCleanup.log

Starting with IBM TRIRIGA Application Platform 2.6.0, to assure proper workflow loading and execution,
a one-time startup validation process checks all of the currently published workflows and generates a
report. The report, named WorkflowCleanup.log, is written to the log directory of the installation
folder. It lists what was found and any actions taken. Review this report carefully to assure correct
workflow operation and for any manual actions that should be taken.

Appendix A of the IBM TRIRIGA Application Platform 3 Installation and Implementation Guide describes
the format of the WorkflowCleanup.log and summarizes issues that may be reported and suggested
actions.

© Copyright IBM Corporation 2011. 37

INDEX
<ANY> 5 Delete 21
<Number> Properties 12 Delete Job 11
Action 22 Delete Query 10
Add New Query 9 Delete Users 13, 20
Add Users 13, 19 Do Not Restrict to User List 20
Admin Main 2 Edit 18
Agent 3 Encrypt 18
Agent Registry 4 Expand Data 11
Agent Startup Table 4 Export Queries 11
AGENTS_NOT_ALLOWED 5 Fail Job 11
Analyze or Rebuild Indexes 8 Field 28, 31, 32
Apply 16 Fields 11
Asterisk 11 Flush A Cache 6
Async 22 Force Clean Up 11
at com.tririga 23 Force Garbage Collection 12
Broadcast Message 19 Formula 26, 27, 28
Business Object 31, 33 Full Access 3
Business Objects with Staging Tables 11 Full Error Log 12
Cache Monitor 16 Full Process Error Log. 12
Child Of 22 GUI Field 29, 30
Children 22 ID (Identification) 21
Cleanup BO 8 Import Queries 10
Cleanup Commands Section 8 In Progress 14
Cleanup Processes Section 14 Instance 21
Cleanup Scheduled Events 8 Instrumentation) 15
Cleanup WF 8 IP Address 19
Count 18 Java Stack Trace 23
Currency Conversion 29 Key Metrics Section 16
Current Step 22 Last 20 Major Exceptions Section 12
Currently Executing Events 21 Last 5 Lines From The Error Log Section 12
Custom Task 37 Licensed Products 19
CustomLogCategories.xml 16 Live Link Section 30
Database Admin Tasks Section 8 Locator Field 33
Database Environment Section 8 Lock System Section 18
Database Space Section 9 Log Out User 19
Database Summary Section 8 Log Type 23
DataConnect 24 log4j.xml 16
DataConnect Jobs 11 Logs Section 12

© Copyright IBM Corporation 2011. 38

Mapping 34 server.log 23
Maximum Threads 18 Set 15, 16
Metric Category 30 Set and Save 19
Module 21 Set Only 19
Monitor a single value 15 Settings for other Agents Section 20
Multi-Instance Agent 3 Single-Instance Agent 3
Name 21, 31 Smart Section Keys 11
Network Speed Throughput 15 Stack Trace 23
No Access 3 Start 14
Object 21 State 24
Oldest Event in Queue 21 State Transition 34
PC 22 Stop 14, 21, 22
Performance Monitoring Section 15 Suspend 21
PID 21 Suspendable 22
Process Error Log Section 12 Suspended Instances Section 21
Property Files Section 18 Switch 28
Query Filter 32 System Analysis 14
Read-Only Access 3 System Build Information 6
Ready Job 11 System language 13
Record to Log 16 Time / Avg 22
Refresh 22 Total Events for a User 20
Refresh Every ___ Seconds 12, 15, 16, 21 Total Time 22
Reports Section 14 Types of Events 20
Reset 15 Types of Events for Each User 20
Reset All 15 UOM 32
Restrict to User List 20 UOM Field 34
Resume 21 Update Console User 3
Retry Job 11 Upsert 11
Reverse Transaction 27 User 21
Roll 12, 16 User List Section 19
Roll All Log Files Now 12 Username and Password Encryption Section 18
Run Cleanup Scripts 8 View 18
Run Query 9 View Headers and Request Parameters 15
Run Workflows Triggered By Scheduled Events VM Stat 15
20 Workflow 27
Running Instances Section 21 Workflow Instance Recording 20
Save 20 WorkflowCleanup.log 37
Save Query 9

© Copyright IBM Corporation 2011. 39

 Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries.
Consult your local IBM representative for information on the products and services currently available
in your area. Any reference to an IBM product, program, or service is not intended to state or imply
that only that IBM product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may be used instead.
However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product,
program, or service.

IBM may have patents or pending patent applications covering subject matter described in this
document. The furnishing of this document does not grant you any license to these patents. You can
send license inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

For license inquiries regarding double-byte character set (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property Licensing

Legal and Intellectual Property Law
IBM Japan, Ltd.
1623-14, Shimotsuruma, Yamato-shi
Kanagawa 242-8502 Japan

The following paragraph does not apply to the United Kingdom or any other country where such
provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT
WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore,
this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically
made to the information herein; these changes will be incorporated in new editions of the publication.
IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not
in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not
part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without
incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the
exchange of information between independently created programs and other programs (including this
one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation
2Z4A/101
11400 Burnet Road
Austin, TX 78758
U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some
cases, payment of a fee.

The licensed program described in this document and all licensed material available for it are provided
by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or
any equivalent agreement between us.

Information concerning non-IBM products was obtained from the suppliers of those products, their
published announcements or other publicly available sources. IBM has not tested those products and
cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM
products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of
those products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without
notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily business operations. To illustrate
them as completely as possible, the examples include the names of individuals, companies, brands, and
products. All of these names are fictitious and any similarity to the names and addresses used by an
actual business enterprise is entirely coincidental.

Trademarks

IBM, the IBM logo, ibm.com, and TRIRIGA are trademarks or registered trademarks of International
Business Machines Corp., registered in many jurisdictions worldwide.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle
and/or its affiliates.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the
United States, other countries, or both.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.

Other product and service names might be trademarks of IBM or other companies. A current list of IBM
trademarks is available on the Web at “Copyright and trademark information” at
www.ibm.com/legal/copytrade.shtml.