Where do you set or change the host name URL?


I installed IBM TRIRIGA Application Platform 3.5.3 in Linux CentOS 7. While running the TRIRIGA installer, I selected an embedded server, that is IBM WebSphere Application Server (WAS) Liberty Profile 17.0.0.2. This server is successfully installed and up and running.

From the log, I found that the server host where IBM TRIRIGA is accessed has an URL something like this: http://some.static.ab-xyz.com:8001. This URL value was taken by default. I did not provide this value. My question is: How do I change this host name URL? Where is the setting for this?

I’m not sure what log you’re looking at and what specifically you’re seeing. What is set as your FRONT_END_SERVER value in your TRIRIGAWEB.properties file?

[Admin: To see other related posts, use the Hostname tag.]

Continue reading

Advertisements

Getting a failure when installing TRIRIGA 3.5.0 on WebSphere 8.5.5


When installing TRIRIGA 3.5.0 on WebSphere 8.5.5.8, the deployment of the TRIRIGA application to WebSphere is failing. We are seeing errors in the was-ant.log and the install fails. The errors noted in the was-ant.log are:

  • Incomplete config id: need closing parenthesis in “”.
  • Invalid parameter value “” for parameter “parent config id” on command “create”.
  • Invalid parameter value server1 for parameter serverName for command setJVMProperties.

The deploy scripts default to localhostNode and localhostCell and then change them to the hostname (which is different). To resolve the problem, it was necessary to provide the correct Node and Cell names in the WAS properties page. If you leave the defaults (localhostNode01 and localhostNode01Cell), the deploy scripts will fail. After changing this, the deployer completed cleanly.

The problem seems to be that even if you explicitly specify the node and cell as “localhostNode01” and “localhostNode01Cell” when creating the WAS profile via WAS’s pmt.sh GUI profile wizard tool, or with the manageprofile.sh shell script, what gets set in the profile is whatever the hostname is (output of the “hostname” command). So “xxx-kdsjd-lapp01Node01” and “xxx-kdsjd-lapp02Node01Cell” are set in the profile.

You can cat (concatenate) this file: /IBM/WebSphere/AppServer/profiles/AppSrv01/logs/AboutThisProfile.txt and see that the node and host names are not localhost as was used in the create-profile script. So now, running the TRIRIGA installer, you need to specify these values in the WAS properties page. If you leave the defaults localhostNode01 and localhostNode01Cell, the deploy scripts fail, unless of course localhost is the system-recognized hostname (which typically it isn’t).

Continue reading

IV83657: Cross-site request forgery (CSRF) vulnerability


A CSRF attack forces an authenticated victim’s browser to send an unauthenticated request to a vulnerable web application, which then performs unauthorized action on behalf of the attacker. This issue has been identified in various places throughout the application. This APAR is meant specifically for the example below.

Steps to replicate:

  • 1. Set the KNOWN_REFERRER_LIST to the hostname.
  • 2. Restart the TRIRIGA application server.
  • 3. Navigate to Configure > People > Employees.
  • 4. Select any existing employee.
  • 5. Click on the Delete button and intercept the form.
  • 6. Change the “sNo” field in the form to that of another user.
  • 7. Save the form as an HTML file, and open it in the browser, where you are currently logged in to TRIRIGA.
  • 8. Submit the CSRF form and see that the other user is deleted.

[Admin: This post is related to the 03.16.16 post and 04.04.16 post about another cross-site request forgery (CSRF) attack vulnerability (IV82436).]

Continue reading

Why is the Workflow Agent failing to run after upgrade?


The TRIRIGA Workflow Agent will not start on the application server. The startup failed as follows:

2015-07-09 09:34:36,075 INFO [com.tririga.platform.agent.AgentManager] (WebContainer : 1) Start requested for WFAgent on xxxxx.
2015-07-09 09:34:36,310 WARN [com.tririga.platform.agent.AgentManager] (HeartbeatThread) Agent is not startable on this host, it may already be running: WFAgent[MID-297637996]

The root cause was that the application server was not resolving the hostname on the machine. This is generally a network DNS configuration issue. Explicitly defining the instance_id and instance_name is our recommended way to define the servers. It makes it easier to identify the servers in the Admin Console visually and also bypasses the need to have the specific IP or DNS defined. To resolve the problem:

  • Set the instance_id and instance_name on both application and process server in the TRIRIGAWEB.properties.
  • Explicitly identify the application and process servers with unique instance_id and instance_name values in the TRIRIGAWEB.properties file.
  • Set the instance_id=1000 and instance_name=appserver on the application server and set the instance_id=2000 and instance_name=procserver on the process server.
  • Then go into the TRIRIGA Admin Console and set the hostnames to match the new instance names given.
  • Save and restart the agents.

Continue reading

Getting a database connection error with integration object


Each time I enter the DB credentials in the Integration Object connection form for the Oracle JDBC:ODBC driver in the defined format JDBC:ODBC:host:Port(1521):Sid. But upon clicking on Test DB Connection, it shows connection failed. However, we are able to connect to the same DB through SQL Developer using the same credentials. We have tried entering the IP address as well, in place of the hostname, but the problem still persists.

Server log after failed connection:

oracle.net.ns.NetException: The Network Adapter could not establish the connection
at oracle.net.nt.ConnStrategy.execute(ConnStrategy.java:392)
at oracle.net.resolver.AddrResolution.resolveAndExecute(AddrResolution.java:434)
at oracle.net.ns.NSProtocol.establishConnection(NSProtocol.java:687)
at oracle.net.ns.NSProtocol.connect(NSProtocol.java:247)
at oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:1102)
at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:320)
… 103 more

Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:381)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:243)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:230)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:377)
at java.net.Socket.connect(Socket.java:539)
at oracle.net.nt.TcpNTAdapter.connect(TcpNTAdapter.java:150)
at oracle.net.nt.ConnOption.connect(ConnOption.java:133)
at oracle.net.nt.ConnStrategy.execute(ConnStrategy.java:370)

Continue reading 

Having an issue with the sender email address in TRIRIGA


For the emails sent out from TRIRIGA, the sender email address is defaulted to SYSTEM@[hostname]. For my current situation, the hostname is not a publicly available domain, only an internal development server. The emails are received by Google Mail and Yahoo Mail, but not being received by corporate email hosts. I suspect it is because of the invalid hostname and rejected as spam. I’ve tried to set the “mail.smtp.from” property in the WebSphere Application Server Admin Console, but it is not working. Any suggestions?

Continue reading