Chapter 9: Configuring Global Properties

Updating global properties

The global.properties.xml file is the master configuration file for Mobile Web Studio and Portal Interface. After you install Unwired Accelerator, there are properties you must change to suit your enterprise. The Unwired Accelerator Installation Guide describes changes to make to the global.properties.xml file for the Unwired Accelerator host, domain, and port configuration; Mobile Web Studio and M-Business Anywhere integration; and proxy server (if used). This section describes additional changes you must make to configure Unwired Accelerator.

Read through all the procedures in this section to determine which properties you must change. After changing each property, save the file, but do not close it, until you have made all of the necessary changes. When you are finished, save and exit the file, close the text editor, then stop and restart the application server.

Sending e-mail to a file

The send.mail property, by default, is set to true, which means that SMTP-based e-mail is sent when a new user account is created. If you do not have SMTP-based e-mail, set this value to false, which writes the e-mail content to <WorkRoot>/e-mail. See “Global property group” for information about the send.mail property.

Use any text editor to open global.properties.xml, which is located in:
- Tomcat – SYBASE\tomcat\Webapps\onepage\config
- EAServer – SYBASE\EAServer\Repository\WebApplication\onepage\ config
Search for the send.mail property and change the value to false.
Save the file but do not close it.

Sending e-mail to users

If you have an SMTP-based e-mail host and leave the send.mail value set to true, you must change the mail.host property value for this functionality to work.

Search for the property called mail.host. See “Global property group” for information about the mail.host property.
Change the value to the name of your company’s SMTP-based e-mail host server.
Save the file.

Configuring multimachine installations

If you installed UA on multiple machines, there are several properties in global.properties.xml that you must update to reflect this configuration.

Search for the catalog_cache_refresh_list property in the Global properties section of the configuration file.
Enter a comma-separated list of machines with catalogs that must be refreshed when a cache refresh is triggered. If you use the machine name, there must be a DNS entry inside the machine to resolve the entry.

This list must be machines that are internally addressable from within the servers themselves and must include the port number, followed by the Web application name, which is “onepage.” For example, using Tomcat:
```
"catalog_cache_refresh_list=
demo1.$DOMAIN:4040/onepage,
demo2.$DOMAIN:4040/onepage"
```
See the table in Global property group for information about the catalog_cache_refresh_list property.
Search for the CacheRefreshList property in the UWP properties section of the configuration file.

Enter a comma-separated list of internally addressable machines names to refresh the cache. If you use the machine name, there must be a DNS entry inside the machine to resolve the entry.

This list must be machines that are internally addressable from within the servers themselves and must include the port number, followed by the Web application name, which is “onepage.” For example, using Tomcat:
```
"CacheRefreshList=
demo1.$DOMAIN:4040/onepage,
demo2.$DOMAIN:4040/onepage"
```
See “UWP property group” for information about the CacheRefreshList property.
Search for the CacheRefreshList property in the Docserver properties section of the configuration file.

Enter a comma-separated list of internally addressable machines names to refresh the cache. If you use the machine name, there must be a DNS entry inside the machine to resolve the entry.

This list must be machines that are internally addressable from within the servers themselves and must include the port number, followed by the Web application name, which is “onepage.” For example:
```
"CacheRefreshList=
demo1.$DOMAIN:4040/onepage,
demo2.$DOMAIN:4040/onepage"
```
See “Docservers property group” for information about the CacheRefreshList property.

Configuring different machines and ports for the same domain

This example illustrates the settings used to configure a different machine and port for the same domain as other machines in your UA installation.

Search for hostname and replace it with the name of the Tomcat or EAServer machine host name that is on a different port, for example, “lab2k”. hostname is the machine name entered at installation.
Change the value of the default_http_port property to the new port for the different machine hosting Tomcat or EAServer:
```
<Property name="default_http_port" value=“new http port" description="the application server port" menugroup="10"/>
```
See “Global property group” for information about the default_http_port property.
Verify that the value to which you changed the default_http_port property is the value for which the application server is configured.

In either Tomcat or EAServer, the portal requires a listener configured for both the IP address 127.0.0.1 and the new port that you configured for the default_http_port property:
```
hostname.domain    new http port
127.0.0.1           new http port
```
Stop and restart the application server.

Turning trace functionality off for production

If you are running the portal in a production environment, you may want to turn off the trace settings, which are turned on by default, to improve performance.

In the UWP properties section, set TraceOn and VerboseTrace to false. See “UWP property group” for information about the TraceOn and VerboseTrace properties.
In the Docservers properties section, set TraceOn and VerboseTrace to false. See “Docservers property group” for information about the TraceOn and VerboseTrace properties.
In the Portal properties section, set TraceOn and VerboseTrace to false. See “Portal property group” for information about the TraceOn and VerboseTrace properties.
In the Capture properties section, set CaptureTraceOn to off. See “Capture logging properties” for information about the CaptureTraceOn property.

Enabling proxy servers

If you are using a HTTP proxy server, there are several settings in global.properties.xml that you must modify.

In the Global properties section, set the proxy property to true.
Set the remaining proxy properties (proxy.host, proxy.port, proxy.bypass_list) to the correct values for your proxy configuration. See “Global property group” for information about the proxy properties, and the Unwired Accelerator Installation Guide for detailed.
Save and exit the file, close the text editor, then stop and restart Tomcat or EAServer.

View this book as PDF