The downloaded DE contains both EGO and the EGO Software Developer Kit (SDK) for the selected operating system. You can install these components separately or together. To run the provided SDK samples, you must install EGO (see both the EGO SDK installation and EGO 1.2.3 installation sections).
For Java APIs, read the EGO Java SDK section.
For Web Services (Linux and Windows) or C APIs (Linux only), you need to install both the EGO 1.2.3 SDK and EGO 1.2.3.
Both Windows and Linux packages are provided for EGO 1.2.3. For Linux platforms, the required package-type depends if you are installing on a management host or compute host.
This document uses EGO_TOP to describe the top-level EGO directory (where EGO is installed). %EGO_CONFDIR% (Windows) or $EGO_CONFDIR (Unix) is an environment variable and is used when the document is describing where configuration files can be found. When you have enabled failover, this directory differs from EGO_TOP.
Refer to appropriate EGO 1.2.3 installation documents (found on the EGO FTP site) for details on planning and installing a cluster.
Note that a single host is sufficient for running samples 1 through 4. However, samples 5 through 7 require a minimum of two hosts to be installed in the cluster.
The EGO web service gateway supports the following optional configuration parameters: The parameters can be defined in $EGO_CONFDIR/kernel/conf/wsg.conf on Linuxor %EGO_CONFDIR%\kernel\conf\wsg.conf on Windows.
WSG_PORT: The web service gateway listening port, default 9090.
WSG_SSL: Security option for communication between web service gateway and its client. Default is NO.
WSG_LOGDIR: Logging directory for web service gateway to save the log file. Default location relative to the installation directory is EGO_TOP/eservice/wsg/log on Linuxor EGO_TOP\eservice\wsg\log on Windows.
WSG_DEBUG_DETAIL: By default, EGO web service gateway will run as a daemon. When the debug is turned on (value is set to 1), it will run in console mode and log all messages to stderr.
Eclipse can be downloaded from http://www.eclipse.org/downloads. The required plug-ins can be added from the Callisto Discovery update site. Add the plug-ins by following these steps:
From the Help menu, select Software Updates and then Find and Install.
In the Install/Update dialog box, click Search for new features to install. Click Next.
In the New Update Site dialog box, type the name Callisto Discovery Site, enter the URL http://download.eclipse.org/callisto/releases, and then click OK.
In the Install dialog box, select callistor and then Finish.
In the Update Site Mirrors dialog box, select the mirror for your download.
After installing the EGO plug-in, you can find further documentation about using it by navigating to Help > Help Contents > EGO Developer Documentation.
Note that a single host is sufficient for running samples 1 through 4. However, samples 5 through 7 require a minimum of two hosts to be installed in the cluster.
Java samples (requires JDK 5.0)
Sample 1: Connects to the EGO web service gateway to get information on resources in the EGO cluster.
Sample 3: Allocates a resource and starts an activity on it.
Sample 4: Monitors load on a resource with an activity running on it.
Sample 5: Starts multiple activities on a resource, monitors load and adjusts resources based on load.
Sample 6: Illustrates the use of the EGO service controller API to start a service.
Sample 7: Illustrates the use of the EGO service director API.
To run the Java samples, see their main methods for the arguments needed. All of them need the URL for the web service gateway as the first argument. If it is running on the master host at the default port, then the URL would be http://masterhostname:9090/. Samples 2-7 all take a port number as the second argument. This is where they run the notification service. You can use 9091 if it is unused on your machine. The third and fourth arguments are the name and description of the client that wishes to register with EGO. For example you can use “Test” and “Testing EGO”.
Sample 1: Connects to the EGO cluster and finds cluster information and information on the resources in the cluster.
Sample 2: Registers with EGO cluster, requests a resource and starts a container on the resource. It explicitly reads messages synchronously from the EGO cluster.
Sample 3: Same as sample 2 but uses asynchronous callbacks from the cluster.
Sample 4: Requests multiple resources and starts activities on them.
Sample 5: Extends sample 4 by monitoring the activities started by the client and dynamically flexes the resources based on load.
Sample 6: Illustrates the use of the EGO service controller API to start a service.
Sample 7: Illustrates the use of the EGO service director API.
Note that a single host is sufficient for running the first four samples. However, the last two samples (ResourceSample and ServiceSample) require a minimum of two hosts to be installed in the cluster.
ClusterSample: Connects to the Platform EGO web service gateway to get information on resources in the Platform EGO cluster.
AllocateSample: Allocates a resource and starts an activity on it.
ActivitySample: Monitors load on a resource with an activity running on it.
ResourceSample: Starts multiple activities on a resource, monitors load and adjusts resources based on load.
ServiceSample: Illustrates the use of the Platform EGO service controller API to start a service
To run the Java samples, see their main methods for the arguments needed. All of them need the URL for the web service gateway as the first argument. If it is running on the master host at the default port, then the URL would be http://masterhostname:9090/.
In $EGO_CONFDIR/kernel/conf/wsg.conf, the parameter WSG_DEBUG_DETAIL is currently set to a value of 1 by default and means debug is turned on. When set to 0, debug is still turned on. The correct behavior is for the default to be set to 0, meaning the debug is turned off.
The Platform Management Console is a tool for EGO administrators to monitor and manage the cluster. It supports both Internet Explorer and Mozilla Firefox, and can be used to perform the following activities:
From the Console you can add new users or change passwords. Use the Console to manage EGO users, consumers, and resources.
In addition to the Platform Management Console, the EGO command line interface (CLI) is also used to manage the cluster. Using egosh commands, you can start and stop EGO daemons or services. Monitoring functionality is also provided.
For a description of various egosh commands, run egosh help or see the Platform EGO Reference guide. Like other shells, egosh can be used to execute a single command or used as a shell. For example:
The Platform EGO™ documentation set is available from the EGO Knowledge Center, installed with your package and accessible from the Platform Management Console. It is also available from ftp.platform.com, in the /docs directory. It includes the following documents:
Planning and Installing your Cluster (Windows or Linux version): Plan your installation, install a production cluster with a Windows or Linux master host, and grow the cluster to include management hosts and compute hosts.
Installing a Single-Host Cluster (Windows or Linux version): Deploy, configure, and test software on a single-host Windows or Linux cluster. Learn how to reconfigure and migrate to a production cluster.
Administering and Using Platform EGO: Manage the cluster by controlling hosts, creating user accounts, and adding administrators and users. Manage resources by building a consumer tree, creating consumers, creating resource groups, and configuring a resource distribution plan. Find information about log files and events, services and daemons, and general EGO concepts. Follow four scenarios to learn key concepts and steps involved in creating resource groups, building a consumer tree, adding a new service to the cluster, and creating resource plans.
Platform EGO Reference: Comprehensive reference to EGO commands, daemons, events, and environment variables.
Platform EGO Developers Guide: A developer's resource for understanding and working with system services, APIs, web service components, WSDLs and schemas. Learn how to create client projects. Find tutorials on getting started with C client and Java client.
Platform EGO C API Reference: Covers all the EGO functions, data structures, pre-processor directives, and enumerations that are available to the C application developer.
Platform EGO Java API Reference: Covers all the Platform EGO details of all the class/interface methods and fields available to the Java application developer.
Platform EGO Web Services WSDL Reference: Provides details about available Web Service operations including input arguments and responses.
Platform EGO Web Services XML Schema Reference: Describes the elements and associated data types used in the WSDLs. Schema diagrams support the descriptions.