WAS and 3.4 Install - [wsadmin] Java Result: 103

If you get the error above in the ant.log file while running the 3.4 installer with WebSphere 8.5.5, you will have to update the Cell and Node setting in the installer steps because it is case sensitive. We had to change it from sw72tririgaNode01 to SW72TRIRIGANode01. This step is crucial because it automatically sets WAS to have the TRIRIGA settings.

set-jaxp-properties:

  [wsadmin] profileName=AppSrv01 registry=D:\softwares\IBM\WebSphere\AppServer\properties\profileRegistry.xml

  [wsadmin] profileHome=D:\softwares\IBM\WebSphere\AppServer\profiles\AppSrv01

  [wsadmin] WASX7209I: Connected to process "server1" on node SW72TRIRIGANode01 using SOAP connector;  The type of process is: UnManagedProcess

  [wsadmin] WASX7015E: Exception running command: "set server [$AdminConfig getid /Node:sw72tririgaNode01/Server:server1/] ;     set jvm [$AdminConfig list JavaVirtualMachine $server] ;     set name [list name javax.xml.transform.TransformerFactory] ;     set value [list value org.apache.xalan.processor.TransformerFactoryImpl] ;     set propertyExist [$AdminConfig getid /Property:javax.xml.transform.TransformerFactory/] ;     if {[llength $propertyExist] > 0 } {       puts Property_Exists ;     } else {      $AdminConfig create Property $jvm [list $name $value] ;     } ;"; exception information:

  [wsadmin] com.ibm.ws.scripting.ScriptingException: WASX7077E: Incomplete config id: need closing parenthesis in ""

  [wsadmin] Java Result: 103

Make sure that it matches the server name including case on whatever server your installing TRIRIGA on.

NOTE:

Not a defect, cell and node are case sensitive.

http://publib.boulder.ibm.com/infocenter/wsdoc400/v6r0/index.jsp?topic=/com.ibm.websphere.iseries.doc/info/ae/ae/adrdftappsvr.htm

Problem with IBM TRIRIGA OOB Security Group Report

I encountered an issue with the out of the box report and IBM has confirmed that it is a defect and has provided me with a workaround. It seems to only happen if TRIRIGA is using SQL as the database. 

This should be done with someone that is a BIRT Report Developer. Once the report has been updated, take the updated .zip file and check out the older report and check in the new one in Document Manager.

Here is the workaround. 

1 - In the report designer, expand the Data Sets section to reveal the SecurityGroups and SecurityPermissions datasets.

2 - Expand the SecurityGroups dataset to reveal the NAME1 object.

3 - Click on the Advanced vertical tab in the Property Editor.

4 - Scroll down to find the Query property. It will look as if the Value is set to SELECT name1.

5 - Click on the Value and you should see this SQL:

SELECT name1

FROM t_group

WHERE name1 <> 'Admin Group'

6 - Everything except 'Admin Group' should be in uppercase in order for SQL to process the query correctly.

How to use JDBC or datasets with starter reports and adding addtional JDBC datasources

Another customer reported this issue in 3.2 and was a confirmed documentation defect. I did not see this added in the 3.4 IBM TRIRIGA Reporting Guide and thought this would be useful to someone who is encountering the same roadblock. 

1. Copy JDBC JAR files
I copied over the two TRIRIGA jar files into the ecilipse plugin directory, you only need one depending on your database platform.
C:\Tririga\lib
-jtds-1.2.5.jar (SQLServer)
-ojdbc6.jar (Oracle)
<installdir>\eclipse\plugins
2. Click Manage Drivers... button
Depending on whether you connecting to Oracle or SQLServer.
Click manage Drivers... button.
Click add jar and add the two jars from above step 1.

You should then beable to select Driver class

Step 5,6,7,8 :-
Oracle
Driver Class: oracle.jdbc.OracleDriver (v11.2)
Database URL: jdbc:oracle:thin:@databaseserver:1521:orcl
User Name: tririga
Password: password
JNDI URL: jdbc/local/Datasource-TRIRIGA-data



SQLServer
Driver Class: net.sourceforge.jtds.jdbc.Driver (v1.2)
Database URL: jdbc:jtds:sqlserver://demobase/tridata
User Name: tririga
Password: password
JNDI URL: jdbc/local/Datasource-TRIRIGA-data

Step 9
Test Connection...

Then click finish and setup the dataset.

Taken from: http://www-01.ibm.com/support/docview.wss?uid=swg1IV15813

SQL Script to Display TRIRIGA User Login History

If you would like to know who has logged into your TRIRIGA system within the past 30 days and when, here is a script you can run against the tririga schema. You can update this script to filter for specific users or filter specific users out (such as data integration users). 

SELECT DISTINCT
user_credentials.user_account AS USERNAME,
session_history.start_time AS LOGIN
FROM
user_credentials, session_history
WHERE
user_credentials.user_id = session_history.user_id AND
session_history.start_time > (sysdate - 30)
UNION ALL
SELECT DISTINCT
user_credentials.user_account AS USERNAME,
active_session_user.start_time AS LOGIN
FROM
active_session_user, user_credentials
WHERE
user_credentials.user_id = active_session_user.user_id
ORDER BY 1, 2;

Taken from http://www.tririga.info/2008/01/system-usage-script.html

3.3.2.1 Fix Pack Installer Workaround

Issue:

There is a defect with the 3.3.2.1 fixpack installer.

I had two servers to test on. One with Oracle and the other SQL.

Both environments had TRIRIGA 3.3.2 installed. When I ran the fixpack on the oracle box, it installed correctly with no issues. For SQL, it does not get pass the verify database. 

Resolution:

There is a non expected behavior with the installer that IBM is addressing. It will be addressed as a permanent fix on the next fix pack release. The work around is as follows:

1.    Download both versions of the JTDS file: 1.2.5 and 1.2.8

2.    Copy both jar files (jtds-1.2.5.jar and jtds-1.2.8.jar) to <Home Tririga>/lib  folder (default: /home/tririga/tririga/lib).

3.    Execute the FP installer.  

IBM Knowledge Center - Installation checklists

IBM TRIRIGA Application Platform Version 3.4.0

---

Installation checklists

Before you install the IBM® TRIRIGA® Application Platform, you can follow the application server and database checklists that apply to your implementation.

Checklist for new IBM TRIRIGA Application Platform installations

Item	Description
Release notes	Read the IBM TRIRIGA Release Notes that apply to your installation version for information and instructions that are specific to that release.
Data recovery and backups	Before starting the installation process, create a data recovery plan to be used in the event of a IBM TRIRIGA Application Platformsystem failure. IBM TRIRIGA is a Java enterprise application that runs on a variety of Java application servers and database platforms. Each application server and database platform provides different methods and recommendations for backups and recovery. Consult the product information provided with the application server and database platform you are using with IBM TRIRIGA for backup and recovery operation standards and best practices. After a successful installation, the IBM TRIRIGA installation folder can be backed up regularly to preserve IBM TRIRIGA system settings.
Full installation	Follow the full installation process for a new installation. If you are upgrading an existing IBM TRIRIGA implementation, see the IBM TRIRIGA Application Platform 3 Upgrade Installation Guide.
Language packs	The installer copies language packs into the [install directory]\userfiles\LanguagePacks folder. Starting with the IBM TRIRIGA Application Platform version 3.3, the directory structure of the language packs separates the label packs from the data packs. You must unpack the main language pack before you select the individual language pack to import. Make sure that you import the correct type of language pack in the specific interface. For example, if you are in the Label Manager, you must import a label pack. If you are in the Language Manager, you must import a data pack. Importing a data pack is not required if your installation is US English only. For more information, see the IBM TRIRIGA Application Platform 3 Localization User Guide.
First step in the installation	The first step in the installation is to run the installer: From the Windows environment, double-click the install.exe file. On Windows, C:\Tririga is the default installation location. Connect and log in to your application server as the IBM TRIRIGA user through SSH or other remote terminal application. From the UNIX or Linux command line, log in to a terminal as the IBM TRIRIGA user and type ./install.bin -i console. To go back, type back and press the Enter key. On UNIX servers, /usr/local/tririga is the typical installation location. After the root super user pre-creates this directory, run the chown tririga /usr/local/tririga command as root, where tririga is the name of the installation user.
Java virtual machine (JVM)	During the installation: Select the path to the Java virtual machine (JVM) that you want the installer to use. The screen lists the java.exe versions that are available on your target computer. IBM TRIRIGA supports Java 6 only. WebSphere® Application Server installations support IBM Java versions 6 or 7. JBoss and WebLogic Server installations supportOracle Java. If you see the following message, “Unable to install the Java Virtual Machine included with this installer”, then continue with the installation. This message is caused by the version of InstallAnywhere that is used by the installer. It has no effect on the installation.
Installation directory	During the installation, specify the complete path of the directory to which you want to install the files: The installation path must not have any spaces. If it has spaces, specify another path. On Windows, C:\Tririga is the typical location. On UNIX, /usr/local/tririga is the typical location. The directory must not have an existing installation. If it has an existing installation, rename that directory. For example, rename the directory to add the word "old" and the date.
Application data	During the installation, choose the compressed file where the IBM TRIRIGA application data is stored. This compressed file is nameddata.zip and is selected automatically by the installer. If the file is not selected, then locate and select the correct file.
After the installation	After the installation is complete: Verify that your installation is running properly. For more information, see the topic about the verification checklist.

Checklist for new IBM TRIRIGA Application Platform installations on Oracle Database

Item	Description
Release notes	Read the IBM TRIRIGA Release Notes.
Multibyte language support	If you support multibyte languages, the Oracle Database must originally be installed as a multibyte database. If the database was not originally installed as a multibyte database, it cannot be changed afterwards.
Multibyte language support	If you support multibyte languages, take the following steps before you begin the installation: Set the instance character set to UTF-8 or UTF-16. If you do not select a UTF-8 or UTF-16 character set, a multibyte character is shown as a question mark when saved in the database. Set the NLS_LENGTH_SEMANTICS parameter to CHAR (not BYTE). If you use BYTE instead of CHAR, the platform does not run the length operations correctly and data can be lost. Set a block size of at least 16K.
User name requirement	For Oracle Database, the schema owner must use the same user ID as the database user.

Checklist for new IBM TRIRIGA Application Platform installations on Microsoft SQL Server

Item	Description
Release notes	Read the IBM TRIRIGA Release Notes.
Users	Verify that the database user that is being used for the new installation is uniquely associated to the database.
Multibyte language support	If you support multibyte languages, take the following steps during the installation: Select the option to configure your database for multibyte support. Choose a collation for the database.
Multibyte language support and WebLogic Server	If you support multibyte languages, verify on the WebLogic Server that the JDBC URL in your DataSource-TRIRIGA-data sets the property of SendStringParametersAsUnicode to true.
Multibyte language support and WebSphere Application Server	If you support multibyte languages, verify in the WebSphere Application Server data source that the custom property ofsendStringParametersAsUnicode is set to true.
Multibyte language support and JBoss Enterprise Application Platform	If you support multibyte languages, verify in the JBoss Enterprise Application Platform data source, tririga-ds.xml, that the custom property of sendStringParametersAsUnicode is set to true.
User name requirement	For Microsoft SQL Server, you can use different values for the database name and the database user ID.

http://www-01.ibm.com/support/knowledgecenter/SSHEB3_3.4.0/com.ibm.tap.doc_3.4.0/ins_install/c_ist_installation_checklists.html?lang=en

TRIRIGA and Custom DB Permissions

FYI

If a customer wants to use TRIRIGA with custom permissions on their database.

TRIRIGA requires the tridata user to have all the permissions listed below in order to work correctly. Custom permissions are not supported.

GRANT ANALYZE ANY TO TRIDATA;
GRANT CREATE VIEW TO TRIDATA;
GRANT CREATE TABLE TO TRIDATA;
GRANT ALTER SESSION TO TRIDATA;
GRANT CREATE SESSION TO TRIDATA;
GRANT CREATE SYNONYM TO TRIDATA;
GRANT CREATE TRIGGER TO TRIDATA;
GRANT CREATE SEQUENCE TO TRIDATA;
GRANT CREATE PROCEDURE TO TRIDATA;
GRANT DROP PUBLIC SYNONYM TO TRIDATA;
GRANT UNLIMITED TABLESPACE TO TRIDATA;
GRANT CREATE PUBLIC SYNONYM TO TRIDATA;
GRANT CONNECT TO TRIDATA;
GRANT RESOURCE TO TRIDATA;
 
ALTER USER TRIDATA DEFAULT ROLE CONNECT, RESOURCE;