Setting Up SSL From Client to Web Server and Plugin to WAS

Here below is the document link which helps for setting up the SSL from client to webserver and plugin to WAS..

http://www-01.ibm.com/support/docview.wss?uid=swg27036662&aid=1

LaunchAnywhere Error when installing CI 12.1.1

IBM TRIRIGA CAD Integrator / Publisher 12.1.1 Installation requires administrator access.  64-bit operating system is recommended.  Java 7 update 67 is required.

In http://www.oracle.com/technetwork/java/javase/7u67-relnotes-2251330.html you can see Java™ SE Development Kit 7, Update 67 (JDK 7u67). The full version string for this update release is 1.7.0_67-b01 (where "b" means "build"). The version number is 7u67. 

Forgot password and cannot access WebSphere Application Server administrative console

Problem(Abstract)

Forgot the password and cannot access WebSphere Application Server administrative console.

Cause

After enabling WebSphere Application Server with security, the administrator forgot the user id and password and could no longer access the server.

Resolving the problem

WARNING: Please use this as the last resort and make sure the server is not in the middle of processing any transactions.

There are 2 possible methods for disabling security:

By way of wsadmin command:

1. <WAS_INSTALL_DIR>/bin/> wsadmin -conntype NONE
2. wsadmin> securityoff
3. wsadmin> exit
4. Restart the servers.
5. Enable the security from administrative console.
6. Restart the servers.

By way of manual edit of security.xml file, which is typically located in <WAS_POFILE_HOME>/config/cells<CELL_NAME> /:

1. Create a copy for security.xml file, in case you need to roll back.
2. Disable the security from the security.xml file (change the very first occurrence of... enabled="true" to enabled="false")
3. Restart the servers.
4. Enable the security from administrative console.
5. Restart the servers.

For additional information regarding enabling administrative security, please refer to this link:
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/tsec_csec2.html

Taken From https://www-304.ibm.com/support/docview.wss?uid=swg21405302

BO Size limits - Sparse Columns use in TRIRIGA with Microsoft SQL Server

Microsoft SQL Server has a limitation for row size at about 8060 bytes of data. This applies to data that is stored in the row. Most VARCHAR/NVARCHAR data is kept off row (just a pointer is stored on the row).

Some users have had issues storing data because the row data is too big on specific Business Object tables (T tables like T_TRIREALESTATECONTRACT, T_TRICAPITALPROJECT and T_TRIBUILDING). Users see the dreaded "Cannot Create a row of size NNNN which is greater than the allowable maximum row size of 8060" in the server.log and they cannot save their record.

To remedy the situation, you must analyze the Business Object and delete unused fields. Another alternative you can use is sparse columns.

Sparse column support was introduced in SQL Server 2008. A sparse column is an ordinary column that has been optimized for null value storage. Null value storage is optimized at the expense of value storage; a sparse column with a null value takes up no storage space at all. However, if the column has a value, 2-4 extra bytes over the value size are required to save the field value. There is a trade-off and the ratio of non-null to null values needs to be significant for any benefit. Microsoft suggests not using sparse columns unless the space saved is at least 20-40%. There is also a cost when reading non-null values from sparse columns; table operations including this column may require more processing.

Depending on the data being stored, this could be an option for making the row sizes smaller.

TRIRIGA Application Platform 3.4.1 does not support sparse columns out of the box. To make a sparse column, you would need to work outside of TRIRIGA directly in the database. You also need to avoid publishing the Business Object as this could make the field revert to non-sparse.

For more information, see the Microsoft documentation (http://technet.microsoft.com) and search on sparse columns. Use sparse columns sparingly as they could have a performance impact to your system depending on the data."

Taken from https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20TRIRIGA1/page/Sparse%20Columns%20use%20in%20TRIRIGA%20with%20Microsoft%20SQL%20Server

Release Versions Summary

IBM TRIRIGA release information is listed in the following table.   Release information includes the type of release, the platform associated with the release, and if the release included cumulative fixes from the previous release.

Release Version	Release Type	Tririga Platform	Cumulative	Release Includes Fix Pack
10.4	Minor	3.4	No
10.3.2	Mod	3.3.2
10.3.1.1	Fix Pack	3.3.1	Yes (for Fix Packs)	10.3.2
10.3.1	Mod	3.3.1	No
10.3.0.1	Fix Pack	3.3.0.1	Yes (for Fix Packs)	10.3.1
10.3	Minor	3.3.0.1	No
10.2.0.3	Fix Pack	3.3 / 3.2	Yes (for Fix Packs)	10.3.2
10.2.0.2	Fix Pack	3.2	No	10.3.1
10.2.0.1	Fix Pack	3.2	No	10.3
10.2	Minor	3.2	No
10.1.0.1	Fix Pack	3.3	Yes (for Fix Packs)	10.3.2
10.1	Minor	3.1.7	Yes
10.0.0.1	Fix Pack	3.3	Yes (for Fix Packs)	10.3.2
10.0	Major	3.0	No
9.7.1	Mod	2.7.2.6	Yes
9.7.0	Minor	2.7.0	No

Taken from https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20TRIRIGA1/page/Release%20Versions%20Summary

TRIRIGA WebSphere Installation Issues

When in installing WebSphere, sometimes the installer has issues with characters in the path. IBM suggest that you use C:\PROGRA~2\IBM\WEBSPH~1\APPSER~1.