Updating global properties

The global.properties.xml file is the master configuration file for Web Studio and Portal Interface. After you install Enterprise Portal, there are properties you must change to match your enterprise. This section describes the changes you need to make.

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.

1. Use any text editor to open global.properties.xml, which is located in the Repository/WebApplication/onepage/config subdirectory of your EAServer installation.

2. Search for the send.mail property and change the value to “false.”

3. Save the file but do not close it.

Sending e-mail to users

1. 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.

2. Search for the property called mail.host. Change the value to the name of your company’s SMTP-based e-mail host server.

3. Save the file.

Configuring multi-machine installations

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

1. Search for the catalog_cache_refresh_list property in the Global properties section of the configuration file.

2. 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:

   "catalog_cache_refresh_list=
   demo1.$DOMAIN:8080/onepage,
   demo2.$DOMAIN:8080/onepage"
   

3. 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:

   "CacheRefreshList=
   demo1.$DOMAIN:8080/onepage,
   demo2.$DOMAIN:8080/onepage"
   

4. 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:8080/onepage,
   demo2.$DOMAIN:8080/onepage"
   

Configuring different EAServers 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 EP installation.

1. Open global.properties.xml in any text editor.

2. Search for hostname and replace it with the name of the EAServer machine host name that is on a different port, for example, “tahiti”. hostname is the machine name entered at installation.

3. Change the value of the default_http_port property to the new port for the different machine hosting EAServer:

   <Property name="default_http_port" value=“new http port" description="the application server port" menugroup="10"/>
   

4. Verify that the value to which you changed the default_http_port property is the value for which the application server is configured.

   In EAServer, the portal requires that there is 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
   

5. 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.

1. In the UWP properties section, set TraceOn and VerboseTrace to “false.”

2. In the Docservers properties section, set TraceOn and VerboseTrace to “false.”

3. In the Portal properties section, set TraceOn and VerboseTrace to “false.”

4. In the Capture properties section, set CaptureTraceOn to “off.”

Enabling proxy servers

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

1. In the Global properties section, set the proxy property to “true.”

2. Set the remaining proxy properties (proxy.host, proxy.port, proxy.bypass_list) to the correct values for your proxy configuration.

3. Save and exit the file, close the text editor, then stop and restart EAServer.

Copyright © 2004. Sybase Inc. All rights reserved.

View this book as PDF