Using the Good Intranet Server Console

Use the following procedure to open the console:

1. Open a web browser and enter the following URL:

http://hostname:port

where hostname is the host name of Good Intranet Server and port is the port number.

The default port number is 19001, but you can use the admin.html.port property in the config.props file to change this value.

A login screen appears.

2. Enter the user name and password for the console and click OK. When you first login to the console, use the following values:

Login: admin
Password: admin

To maintain system security, Good Technology recommends you change the default login and password. For more information, see Administration

The server console appears.



3. Select the tabs to view status information and set attributes and configuration properties that are not on the Main page.

   Server Console Pages

   Tab Name	Information Displayed
   Main	Shows general information about the server including hostname and software version number.
   Traffic	Shows HTTP request and response traffic volume sent between wireless handhelds and the server. You can also use this page to configure traffic display options.
   Logging	Enables or disables log files for common server components.
   Site Access	Enables you to: - Limit internet access (set Walled Garden) for users by disabling the Go to web Address command on handhelds. - Set the default home page for handhelds. - Enable URL and hostname remapping for URL requests. - Specify the maximum size, in KB, of files being uploaded by users.
   Push	Enables you to send and manage push messages to users enabled on server. For more information, see Using Push Technology
   Proxy	Enables you to configure your proxy server or per user proxy settings.
   Admin	Enables you to manage login information for the Good Intranet Server. You can change the default administration login and password for the server.

Main

The Main tab of the server console displays general information about Good Intranet Server. This includes hostname, software version, and location of the server properties file (config.props).

Traffic

The traffic page of the server console displays the amount of HTTP traffic sent between wireless handhelds and Good Intranet Server. This page is useful for comparing network traffic activity over hourly, daily, or weekly periods.

The following figure shows the default traffic display. This display shows response traffic sent to handhelds for the current day and the previous seven days.

Important: If the traffic page does not appear, make sure the traffic display is enabled in the config.props file. (See Traffic Display for more information.)

Setting Traffic Display Options

To set Traffic display options:

1. Click Advanced Settings.

The Traffic Visualization screen appears.



2. Enter Traffic display options as desired. Options include:

   Traffic Display Options

   Item	Description
   Chart Type	Displays traffic as either a bar chart, line chart, or tab-delimited text. You can paste the tab-delimited text into an Excel spreadsheet.
   Data Frequency	Sets the time period that appears across the bottom of the display (along the X-axis). You can display data in hourly, daily, or weekly increments.
   Plot Series	Controls whether HTTP responses, requests, or both are included in the display. In charts, requests and responses are differentiated by color.
   Dates	Sets the start and end data for displayed data.

3. When you have finished entering options, click Create Chart. The Traffic Visualization page appears.

Logging

Good Intranet Server includes both production logs and diagnostics logs. With the exception of the access log, production logs are enabled by default and cannot be disabled. Diagnostic logs are disabled by default and can be enabled if desired. The server also sends logging information to the event log.

The logging page of the server console lists logs that have been enabled for the server and allows you to enable or disable logging for Good Intranet Server components.

In addition to enabling and disabling logs with the Good Intranet Server Console, you can use the config.props file to control logging behavior. For details, refer to Server Configuration Parameters

Types of Log Files

The following table lists Good Intranet production and diagnostic logs.

Log Files

Production Logs
Access	Logs information about HTTP requests and responses. Because this log tracks handheld access to your corporate network, Good Technology recommends checking this log periodically for security purposes.
Admin	Records initialization of the server console and errors. It also tracks HTML management activities.
Content	Logs content errors, such as incorrect HTML tags that prevent Good Intranet from displaying a page. Entries appear for errors relating to incorrectly encoded HTTP messages and also for HTML parsing errors.
Default	Contains start up, configuration, and shutdown information. It contains information about the normal running operations of the server. The log contains information related to normal startup, configuration, user administration, and shutdown.
Push	This log stores information about the states of push messages and their deliverables. It also includes information about when push messages are stored on the server and when they are delivered to the client. It contains a push identifier, user's email address, and push status. The push identifier is system generated and assigned to the push message when the push was initially submitted to the system for delivery.
Stderr	Logs serious error messages that would otherwise be sent to the standard error. This log should always be empty. If the server generates unhandled exceptions, save them (as they contain diagnostic information) and contact Customer Support at Good Technology.
Stdout	Primarily logs serious messages that would otherwise be sent to the standard output. Aside from initial startup entries, this log should always be empty. If the server generates any other entries, save them and contact Customer Support at Good Technology.
Note: With the exception of the Access log, production logs are always enabled.
Diagnostic Logs
Diagnostic logs are disabled by default. You can use the Good Intranet Server Console to enable these logs. Note: Good Technology does not recommend using diagnostics logs in a production environment.
Converter	The server includes a set of content-conversion adapters for mapping text-based web content to a compiled form that can be sent to handhelds. The converter log stores messages related to content conversion.
Diff	Logs caching of new content and sending of differential data.
Redirect	Logs data when server encounters an HTTP redirection response from a web server.

This table lists the most important logs created by the server. Additional logs can be enabled to support specific Good Intranet features. For example, if you use a proxy server for making HTTP requests, you can enable a proxy log to store proxy-related log messages. Also, you can enable an SSL log to track SSL activities (including trusted certificate loading). The SSL log can be run without greatly impacting server performance.

Log File Location

All log files have a Good Intranet assigned name and are stored in server's log directory. The log directory location is set during installation and stored in the registry. By default, log files are located in:

install_dir\logs

Individual log files are named using the following convention:

install_dir\logs\logname.log

where logname identifies the type of log being maintained (for example, responsize.log).

The most-recent logging information is always stored in files with the simple logging name (logname.log). When a log file is rolled over, the old file is closed and renamed with a time/date stamp. For example:

install_dir\logs\responsesize.log10-22-06.14-35-48

where 10-22-06.14-35-48 is 2:35 PM and 48 seconds on October 22, 2006.

Event Log and Good Operations Log

To maintain consistency with the Good Management Server, Good Intranet Server is configured to send important (not all) log messages to the Event Viewer Application log. Also, the good-ndc.log file contains log events related to communication with the Good Operations Center. For more information on the good-ndc.log file, see the Good Mobile Messaging Administrator's Guide.

Shared Log Messages

In some cases, when communicating with the Good Operations Center, the Good Intranet Server and Good Messaging Server share the same log messages. Even though the Good Intranet Server generates these messages, the term "Good Messaging Server" may appear in the messages.

Shared messages include:

• logMsgXmlGwLoginFailed "Good Intranet Server failed to login to Good Operations Center as hostname <host_name> Error code <error_code>"
• logMsgXmlGwCannotConnect "Good Intranet Server cannot connect to Good Operations Center at URL <url_name>. Confirm network access to Good Operations Center. Code <error_code>"
• logMsgXmlGwHookupFailed "Good Intranet Server failed to connect and authenticate with Good Operations Center at <location> with hostname <host_name>. Reason code <error_code>"
• logMsgXmlGwAckFailed "Send of acknowledgment of message received and processed failed from Good Intranet Server to Good Messaging<network. Message: <message>. Code <error_code>"
• logMsgXmlGwRemoveFailed "Good Intranet Server failed to remove msg <message_id> from Good Operations Center. Code <error_code>"
• logMsgXmlGwAddQFailedQueueFull "Good Intranet Server failed to send a message to connection <connection_name> because the network queue is full."
• logMsgXmlGwCallbackThrew "Good Intranet Server protocol engine callback to session manager threw an exception."
• logMsgXmlGwSessMgrRefusedMsg "Good Messaging session manager refused message, id <message_id>, from Good Operations Center. Code <error_code>"
• logMsgXmlGwGetQFailed "Good Intranet Server received an error fetching a message from the Good Operations Center. Code <error_code>"
• logMsgXmlGwStatusReportFailed "Good Intranet Server failed to report status to Good Operations Center. Attempted to report status <status>. Got code <error_code>"

Site Access

The Site Access page allows you to:

• Limit internet access for users by disabling the "Go to web Address" command on handhelds.
• Set the default home page for handhelds.
• Map the host name received in a URL to a different host name (Host Substitution).
• Map the path following the host name in a URL to a different path (URL Substitution).

URL substitution in combination with host substitution makes it possible to fully change the URL that a wireless handheld requests without reconfiguring the handheld. This can be useful, for example, if you want to change the server host.

Host Substitutions

In host substitution, server replaces the destination host name in a URL with a different host name. This page allows you to enable or disable host substitution, to specify host-name substitutions, and to delete previous host-name substitutions.

To set up host substitution:

1. In the Host Substitutions area of the page, select Enabled > Yes. Then, click Set.
2. Enter the name of the From host. This is the original destination hostname that appears in the URL.
3. Enter the name of the To host. This is the name of the new host to include in the URL.
4. Click Add.

The substitution you just added appears on the page. You can continue to add host substitutions as desired.

5. If you want to remove a substitution, click the Remove button next to the substitution.

URL Substitutions

In URL substitution, the server replaces the path in a URL that follows the destination host name with a different path. Make sure you enter a valid URL. If you do not use a valid URL, an error may occur when the Good Intranet Server is restarted. You can comment the urlsubst.sub line out if a problem with URL substitution occurs.

To set up URL substitution:

1. In the URL Substitutions area of the page, select Enabled > Yes. Then, click Set.
2. Enter the name of the From URL. This is the original destination URL.
3. Enter the name of the To URL. This is the name of the new URL.
4. Click Add.

The substitution you just added appears on the page. You can continue to add URL substitutions as desired.

5. If you want to remove a substitution, click the Remove button next to the substitution.

Important: URL substitution is applied before host-name substitution. Thus, to map the URL http://localhost/intro.html to http://www.myvendor.com/demo/docdemo.html, you need to keep localhost as the host name in URL substitution.

Configuring Internet Access for Users

You can configure the Good Intranet client from the Site Access page. You can set:

• Global Home page
• User-specific home page
• NTLM password and time-outs
• Walled garden settings
• File upload settings

1. To specify the default home page on handhelds:
1. In the Global Home Page area, specify whether or not a user can select the DocStore or Home page as the Good Intranet start page.
2. In the Default Home page section, enter a home page address.
3. Click Save to save the address.

If you do not specify a home page, and leave this field blank, www.good.com is used as the default. The first time a user accesses the Good Intranet client, the default home page is shown, even if you have changed it. The new page you defined appears thereafter.

2. To specify an specific page for one or more users:
1. Select the email addresses of the users you want to change.
2. Enter the URL of the home page.
3. Click Save to save the address.
3. To set NTLM or Basic password time-outs:
1. Locate the NTLM/Basic Password area of the page.
2. Select Always, Never, or set the timeout value.
3. Select Save.
4. To limit access:
1. Locate the Walled Garden area of the page.
2. Select Enabled > Yes.

When Walled Garden is enabled, the Page > Go to web Address command on handhelds is disabled.

1. To set file upload options, specify the maximum file upload size, in kilobytes. The default is 512KB and the maximum value is 800KB. If you set this value to 0, the file upload feature is disabled.
2. To update existing user handhelds, click Update Clients.

Handhelds for all users enabled on the server are updated with the latest Walled Garden and home page settings.

If you don't click Update Clients, these settings only apply to handhelds you set up after you configure internet access.

For more information about how to create an HTML page that allows users to upload files, see the Good Mobile Intranet Developer's Guide.

Push

The Push page allows you to send and manage push messages to users enabled on the server. For more information, refer to Using Push Technology

Proxy

The Proxy page allows you to manage your proxy server settings. You can enable a proxy server and proxy logging from this page. You can also enable automatic proxy configuration. A proxy server sits between the Good Intranet Server and the web server or origin server. It intercepts all requests to the Good Intranet Server to see if it can fulfill the requests itself. If not, it forwards the request to the Good Intranet Server.

Proxy settings are defined to route requests from the Good Intranet server, through the proxy server that is defined, to the originating web server. Proxy servers can also be used to filter requests. For example, your company might use a proxy server to prevent employees from accessing a specific set of web sites.

You can configure Good Intranet Server to use proxy servers for the HTTP and HTTPS (secure HTTP) requests it receives. There can be multiple servers for each protocol. For example, you can define a proxy server for all HTTP requests sent to HTTP://www.oneurl.com and a separate proxy for all HTTP requests sent to HTTP://www.twourl.com. Similarly, you can define separate proxy servers for HTTPS requests sent to the same destinations.

For each proxy server you define, assign the proxy a name and configure the following properties:

• host
• port
• rule
• exceptions

For a single proxy, there may be multiple rules, each with its own rule name.

Thus, for two HTTP proxies, HTTP_Proxy1 and HTTP_Proxy2 and one HTTPS proxy, HTTPS_Proxy1, you potentially have the following sets of properties:

proxy.Http_Proxy1.host	proxy.Http_Proxy2.host	proxy.Https_Proxy1.host
proxy.Http_Proxy1.port	proxy.Http_Proxy2.port	proxy.Https_Proxy1.port
		proxy.Https_Proxy1.options
proxy.Http_Proxy1. realm.username	proxy.Http_Proxy2.realm.username	proxy.Https_Proxy1.realm.username
proxy.Http_Proxy1. realm.password	proxy.Http_Proxy2.realm.password	proxy.Https_Proxy1.realm.password

For proxies that need to authenticate themselves in order to access an HTTP realm, you also need to set the following properties:

• realm username
• realm password

Proxies for HTTPS require an additional property:

proxy.proxy_name.options

In addition, for each proxy there must be one or more proxy.rule_name.rule properties and you can also specify any exceptions. An exception is defined for certain URLs that are not routed through the proxy server, even though they match a proxy rule. These URLs are defined using regular expressions.

Enabling Automatic Proxy Configuration

Using the Good Intranet Server Console, you can enable automatic proxy configuration. When this option is enabled, you can configure the PAC (proxy auto configuration) file. This file can be specified as an HTTP UTL or you can upload it to the Good Intranet Server from the local file system. When you submit the file or URL, the proxy configuration changes are made immediately. The Good Intranet Server does not have to be restarted.

To enable automatic configuration:

1. From the main Proxy screen, select Enable Proxy auto configuration.
2. Select Configure to specify the URL or add the PAC file.

1. Select Update to save your changes.

Enabling Per User Proxy

Good Intranet lets you enable a proxy for your users. When this option is enabled, users are prompted to enter their usernames and passwords when accessing sites using Good Intranet. The usernames and passwords are associated with the proxy server. You can also set the amount of time allowed to pass before users need to enter their passwords again.

To set enable the per user proxy:

1. From the main Proxy screen, select Per User Proxy.
2. On the Per User Proxy Settings page, select Enable Per User Proxy.
3. Select Save and Update Clients.

To set the timeout value for users' passwords:

1. From the main Proxy screen, select Per User Proxy.
2. On the Per User Proxy Settings page, select Always, Never, or set the timeout value.
3. Select Save and Update Clients.

Administration

The Administration page allows you manage administrator login information for managing the Good Intranet Server. You can use this page to change the default user name and password for the server.

The user name and password you enter are encrypted and stored in the config.props file. If you forget the password:

1. Delete the admin.html.username and admin.html.password properties from the config.props file.
2. Restart the Good Intranet Server.
3. Use the default login to open the console.

Login: admin
Password: admin

1. Click the Admin tab and create a new username and password.