HTTP requests are no longer forwarded to TRIRIGA

This same troubleshooting applies to Liberty.
See: https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20TRIRIGA1/page/Troubleshooting%20SSO

HTTP requests are no longer forwarded to TRIRIGA
After you upgrade TRIRIGA on WebSphere Application Server, IBM HTTP Server no longer forwards requests to TRIRIGA.
You must reconfigure the web server in WebSphere Application Server. One method of reconfiguring the web server is to use the WebSphere Customization Toolbox (WCT). WCT contains the Web Server Plug-ins Configuration Tool, which steps through the process of deleting and re-creating the web server definition for IBM HTTP Server.
Tip: When you specify the application server location in the Configuration Scenario Selection dialog, if your configuration scenario is local then browse to the location of the \AppServer folder. For example, a common location for the application server is C:\Program Files (x86)\IBM\WebSphere\AppServer.
If you change the host name, check the plugin-cfg.xml file to make sure that it contains the correct host name specified. Specifically, check the Transport Hostname property. The plugin-cfg.xml is typically in pathToInstall/IBM/HTTPServer/Plugins/config/webServerName/plugin-cfg.xml.


Thank you DAN!

Using LdapQuery to debug LDAP connection problems in WebSphere Application Server

Technote (troubleshooting)

Problem(Abstract)

How to use LdapQuery web application to debug LDAP configuration problems with IBM® WebSphere® Application Server

Resolving the problem

Use the ldapQuery web application utility to search the LDAP server.
This will allow you to quickly determine if the search is returning what you expect.
Once you have successfully queried the LDAP server, you may use the settings in IBM® WebSphere® Application Serve to enable security to the server.

Useful when:

• Configuring security using an LDAP server for the first time
• Currently using one LDAP server but want to test connections to another
• Planning to change from stand-alone LDAP to federated LDAP servers

Information taken from http://www-01.ibm.com/support/docview.wss?uid=swg21648889

Troubleshooting IHS - MustGather information for Windows OS

IBM HTTP Server version.

install_root/apache -v

Configuration file:

install_root/conf/httpd.conf

Error log:

install_root/logs/error.log

Access log:

install_root/logs/access.log

LDAP properties file

install_root/conf/ldap.prop

Traces: IBM HTTP Server LDAP over SSL

1. Stop IBM HTTP Server.
2. Clear all logs in the install_root/logs directory.
3. Edit the httpd.conf file:
• Change Loglevel to debug.
• Add SSLTrace directive to the bottom of the httpd.conf file.

Enable LDAP tracing:

Create the following system variable:

LDAP_TRACE_FILE

Set the value with the name for the log file (for example: c:\ldaptrace.log).

Create the following system variable:

LDAP_DEBUG

Set the value to 65535.

Enable GSKit trace:

Create the following system variable:

GSK_TRACE_FILE.

Set the value with the name for the log file (for example: c:\gsktrace.log).

6. Start IBM HTTP Server.
7. Recreate the problem.
8. Capture the following:

netstat -na > netstat.out

Collect the following data files:

• httpd.conf, error_log, access_log
• netstat.out
• ldaptrace_log
• gsktrace_log
• ldap.prop
• IBM HTTP Server version
• Include the date and time of failure along with the browser version and the full URL that resulted in the LDAP failure. For example:

https://www.ihshost.com/mystuff/goodies/index.html

How to delete a WAS Profile

1. cd install_root/bin
2. wasprofile -delete -profileName profile

Where profile is the name of the profile in WAS that you are deleting

Upgrade from TRIRIGA version 10.0 and TRIRIGA Application Platform version 3.0 to the most current application and platform releases

To upgrade from TRIRIGA version 10.0 and TRIRIGA Application Platform version 3.0, you must upgrade TRIRIGA, TRIRIGA Application Platform, apply object migration packages, and run patch helpers.

Check the release notes for the packages you are installing for details about new features and fixes for the release. Refer to the release version summary table for a summary of the TRIRIGA releases available.

1. Shut down the application server.
2. Upgrade the platform to IBM® TRIRIGA Application Platform version 3.4 as described in the  IBM TRIRIGA Application Platform version 3 Upgrade Installation Guide.
3. Start the server and ensure the server startup processes are running.
4. Apply the TRIRIGA version 10.1 minor release cumulative package.
5. Restart the application server.
6. Apply the TRIRIGA version 10.2 minor release package.
7. Restart the application server.
8. Update DateTime system fields from VARCHAR to NUMERIC
9. Apply the TRIRIGA version 10.3 minor release package.
10. R epublishing Business Objects for Localization
11. Apply the TRIRIGA version 10.3.1 mod release package.
12. Apply the TRIRIGA version 10.3.2 mod release package.
13. Apply the TRIRIGA version 10.4 minor release package
14. Apply the TRIRIGA version 10.4.1 mod release package.
15. Importing Patch Helper Records.

Taken from https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20TRIRIGA1/page/Upgrade%20from%20TRIRIGA%20version%2010.0%20and%20TRIRIGA%20Application%20Platform%20version%203.0%20to%20the%20most%20current%20application%20and%20platform%20releases

Security warnings when loading to AutoCAD 2014: Troubleshooting

The installation or upgrade process for version 12 of TRIRIGA® CAD Integrator/Publisher for the AutoCAD 2014 application might generate security warnings. You can resolve this issue by adding the TRIRIGA CAD Integrator/Publisher installation path to the AutoCAD TRUSTEDPATHS variable.

Symptoms

In a security concern window, you see a message that an executable file was found outside of the specified trusted locations.

The security window is displayed twice: once for the TRIRIGA CAD Integrator/Publisher program commands, and once for the IBM TRIRIGA menu items.

In both security windows, you click Load, and TRIRIGA CAD Integrator/Publisher starts. However, the next time you start TRIRIGA CAD Integrator/Publisher, the security windows are displayed again, and you must load the path names again.

Resolving the problem

To prevent the security windows from being displayed, add the TRIRIGA CAD Integrator/Publisher installation path to the AutoCAD TRUSTEDPATHS variable.

1. Open AutoCAD 2014.
2. In the command line, enter TRUSTEDPATHS.
3. Add the TRIRIGA CAD Integrator/Publisher installation path. The default location is C:\Program Files\IBM\TRIRIGA\CI-12\bin\ac.

Taken from http://www-01.ibm.com/support/knowledgecenter/SSFCZ3_10.4.1/com.ibm.tri.doc/ci_cadint/ts_troubleshoot_AutoCAD2014_security_warnings.html

Default URL for the WebSphere Application Server (WAS) Admin Console

Question

A successful installation of WAS has completed and now the administrative console needs to be accessed. How is the admin console accessed? Access to this console may be necessary in preparing for the ITIM installation.

Answer

Assuming a successful install, using default properties, the URL for the administrative console would be:

http://yourserver:9060/ibm/console
or
https://yourserver:9043/ibm/console

(where 'yourserver' is the server WebSphere is installed on)

This is also assuming the 9060 and 9043 ports were not already in use. If the ports are already in use the WAS admin console port can be changed to another port by modifying the HTTPTransport_4 and HTTPTransport_5 port values in the $WAS_HOME/profiles/profileName/config/cells/cellname/virtualhosts.xml file.

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

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.