Client Configuration

You must configure each client’s properties so it can communicate with the cluster. Both the owappserver.properties and ow­data­base.properties files may need overrides in /owareapps/installprops/lib/installed.properties to function properly.

owdatabase.properties Overrides

Each client must point to the database server only if you launch any thick client application--for example, Agent Mapper. Override all database server properties to your database server. If you are unsure whether your application has thick client components, then set these properties in installed.properties.

[spacer]

When connecting to a cluster whose primary application server goes down, clients may lose connection to the application server (cluster). If you receive the lost connection to appserver dialog, wait a few minutes for the client to reconnect (or restart the client).

owjms.properties Overrides

You must also uncomment the following sonicmq jms properties in /oware/lib/owjms.properties on the client:

 

#jms.provider=SONICMQ

#jms.qf=QueueConnectionFactory

#jms.tf=TopicConnectionFactory

#com.dorado.eventchannel.VendorInitFactoryClass.sonicmq=com.dorado.core.jms.OWSonicMQInitFactory

#com.dorado.jms_vendor.port.sonicmq=2506

#com.dorado.eventchannel.protocol.sonicmq=tcp://

 

[spacer]

After making the change to the above properties, you must re-source the Oware Environment.