Startup Properties

The values in installed.prop­erties now set most properties for the process monitor to pass when starting a server. All command-line options for the startappserver script are now in in­s­talled.prop­erties (see Overriding Properties). These are active for each execution of the server (even a mediation server) on the machine where the override exists. Command line arguments override these properties.

The following are properties you can set in owareapps\installprops\lib\ installed.properties to configure servers:

• Set to true on Solaris only when using 64-bit VM and 4GB is available for server.

oware.server.aggressive.heap=false

• Default server partition name also used by client and mediation to locate a server

oware.client.partition.name=demo1

• Default interface used by servers and direct access cut-thru sessions.

oware.local.ip.address=192.168.0.10 [for example]

The IP address also appears in database connection properties:

com.dorado.meta_database.name=//192.168.0.10:3306/owmetadb

com.dorado.jdbc.database_name.mysql=//192.168.0.10:3306/owbusdb

To change the IP address, stop the server, set these properties to the new IP address and delete the content of the oware/temp directory. Then restart the server.

ipaddresschange

A simpler alternative to changing properties is to use the ipaddresschange script. If you were to install this application on a machine on one network, then move your machine to another network, the IP address from your original network remains hard-coded. You must change the application’s IP address to reflect the new network for the software to function correctly. Here is how to do it, once you have connected the application server machine to the new network:

a. First, shut down the Oware Server Manager. Open a com­mand shell (Start > Run cmd, in Windows) then type: net stop "Oware Server Manager" (including the quote marks)

b. Next, find out what your new IP address is. To do this type ipconfig in the command shell you just opened, and make note of the IP Address that appears. You will need that number in a subsequent step.

c. Type oware at the command line. This sets the environ­ment.

d. In the same shell, type ipaddresschange -n [the IP address discovered in b]

e. Restart Oware Server Manager by typing: net start "Oware Server Manager" (including the quote marks)

Your machine should then be able to connect to other devices on this network and function correctly.

[spacer]

After the utility is done, if you are using Server Monitor, its Icon in the program tray has an x through it. You must either reboot or use Windows’ Administrative facility stop the oware server manager service and restart it.

• Use only https for web services and web clients

oware.appserver.web.enable.https=false

• Set to true when there is no graphics adaptor available for server

java.awt.headless=false

• Primary cluster member (must be running for members to join)

oware.config.server=localhost

• Cluster peer to peer multicast address

oware.cluster.multicast.address=226.10.20.30

• Subnet mask for mediation device coverage

oware.mediation.subnet.mask=255.255.255.0

• To change the default HTTP/HTTPS port numbers for web application or web services, add the following properties to owareapps/installprops/lib/installed.properties:

oware.appserver.web.http.port=[default port number:80]

oware.appserver.web.https.port=8443

You may then change the port values for these property entries and restart the Application Server. Special setup (outside the scope of this document) is necessary to run a web server on port numbers lower than 1024 on many operating systems.

[spacer]

Do not change the system time while the Application Server is running. If you must change the system time, shut down the server before the change, and restart it afterwards.