Home > Articles

Like this article? We recommend

Globus Toolkit Installation

After you have met all of the prerequisites, proceed with the Globus Toolkit version 3.x installation. It is recommended that you create a special system account (for example, globus) to own the Globus Toolkit version 3.x files, then perform the installation as this user. The Globus Toolkit tries to minimize the usage of super-user privileges to avoid security problems.

This section documents all Globus Toolkit 3.x installation steps. The installation steps are not specific to the Solaris OS platform, but are common to all UNIX operating systems.

Phase 1: Installing Globus Toolkit 3.x Core

The following steps guide you through the process of installing the Globus Toolkit version 3.x core.

To Install Globus Toolkit 3.x Core

  1. Set the JAVA_HOME environment variable to point to your JDK distribution; add $JAVA_HOME/bin to your PATH environment variable.

  2. Set the ANT_HOME environment variable to point to your Ant distribution; add $ANT_HOME/bin to the PATH environment variable.

  3. Download the Globus Toolkit version 3.x source installation bundle from http://www-unix.globus.org/ftppub/gt3/3.0/3.0.2/gt3.0.2-source-installer.tar.gz, and extract it to your preferred location, which is referred to as <GLOBUS_SOURCE_INSTALLER> from here on.

  4. Choose an installation directory for Globus Toolkit version 3.x.

  5. This directory is different than the source distribution directory and from here on is referred to as <GLOBUS_LOCATION>.

  6. Change directory to the <GLOBUS_SOURCE_INSTALLER> directory, and run the install-gt3 installation script.

  7. It is recommended that you edit the install-gt3 script and append \ -verbose to the definitions of the GPT_BUILD and GPT_INSTALL variables. This increases verbosity. You should capture the installation log to a file as follows:

    $ ./install-gt3 <GLOBUS_LOCATION> 2>&1| tee install.log
  8. After the script exits, check the log for errors:

  9. $ grep ERROR install.log

    If there are no errors, continue with the installation. Otherwise, check the log file to find the cause of the installation error.

  10. Change directory to the <GLOBUS_LOCATION> directory and run ant setup.

  11. Log in as super-user, change directory to the <GLOBUS_LOCATION> directory, and run the following commands:

  12. # mkdir <JAVA_HOME>/jre/lib/endorsed
    # cp endorsed/xalan.jar <JAVA_HOME>/jre/lib/endorse

    where <JAVA_HOME> is the directory of your Java distribution.

Phase 2: Installing Certificate Authority (CA) and Issuing Certificates

Security is one of the main concerns of Globus Toolkit 3.x. The Globus Toolkit is built upon the Grid Security Infrastructure (GSI) layer. GSI provides authentication, access control, and confidentiality of data. It uses PKI and digital certificates to authenticate grid entities.

You need a host certificate for your host, an LDAP certificate for your directory service, and a user certificate for each grid user. A trusted Certificate Authority (CA) must sign all these certificates. You can use your own existing CA, you can use the Globus CA, or you can install your own simple CA with basic functionality for testing purposes.

The first option is not always available. The second one is quite impractical because there is a delay of approximately two days between the time you request a signed certificate, and the time it is sent to you by the Globus CA. Thus, for testing purposes, it is recommended that you install your own CA.

To Install Your Own CA

  1. Download the Globus Toolkit CA bundle from ftp://ftp.globus.org/pub/gsi/simple_ca/globus_simple_ca_bundle-latest.tar.gz.

  2. Copy the simple CA bundle to the <GLOBUS_SOURCE_INSTALLER> directory, then issue the following commands from the account you are using to install Globus Toolkit 3.x:

  3. $ export <GLOBUS_LOCATION>=/path/to/globus/installation
    $ $<GLOBUS_LOCATION>/sbin/gpt-build \
     globus_simple_ca_bundle-latest.tar.gz <flavor>
    $ $<GLOBUS_LOCATION>/sbin/gpt-postinstall

    where flavor is the platform for which you want to install. For more information on flavors, consult the Globus Toolkit 3 Administration Guide. Examples of flavors are gcc32, gcc32dbg, and gcc32pthr.


    During the post-installation phase, you will be prompted to provide information about the newly created CA; make sure this information is valid.

    In the $HOME/.globus directory of the user account you want to use to perform the installation, you can now find the simple CA directory where the CA has been installed. The cacert.pem file represents the CA public key. Also in this directory, you can find a tarball named globus_simple_ca_<CA-HASH>_setup.tar.gz where CA-HASH represents the hashcode for the CA certificate (cacert.pem).

  4. Compute the hashcode for your certificate using the following command:

  5. $ openssl x509 -in <certificate_file> -hash –noout

    This tarball can then be distributed to other hosts that want to be clients for your CA, or trust your CA. They can install it using gpt. Your CA certificate file with other needed configuration files will be installed on the client machines.

  6. To setup the grid security for your installation, log in as root, and run the following command:

  7. # $<GLOBUS_LOCATION>/setup/globus_simple_ca_<hashcode>_setup/setup-gsi

    This configures the security infrastructure to use the newly created CA and create the proper directory structure under the /etc/grid-security directory.

To Install a Globus Toolkit CA

  • If you choose to install and set up the Globus Toolkit CA instead of your own CA, run the setup-gsi script under the $<GLOBUS_LOCATION>/setup directory.

  • Under the $<GLOBUS_LOCATION>/setup directory is the globus directory that contains the data needed to install the Globus CA as your trusted CA.

To Issue Certificates


After setting up grid security, you must create certificates for your grid host, for your directory service LDAP server, and for your users. The tools to create and sign the certificate are located in $<GLOBUS_LOCATION>/bin.

  1. Add the $<GLOBUS_LOCATION>/bin location to the PATH environment variable.

  2. To create a certificate request for your host, use the following command syntax:

  3. $ grid-cert-request -service host -host <hostname>

    For example:

    $ grid-cert-request -service host -host \ solaris.ddns.comp.nus.edu.sg

    This certificate is used by the GRAM and GridFTP services.

  4. To create a certificate for your LDAP server, use the following command syntax:

  5. $ grid-cert-request -service ldap –host <hostname>

    For example:

    $ grid-cert-request -service ldap –host \ solaris.ddns.comp.nus.edu.sg
  6. To create a certificate request for your user, use following command syntax:

  7. $ grid-cert-request

    After you create your certificates, you must sign them using your CA. You can sign the certificates using the grid-ca-sign utility.

  8. Sign the certificates using the grid-ca-sign utility.

  9. $ grid-ca-sign –in <certificate_request.pem> -out <certificate.pem>
  10. Obtain the signed certificates from the CA, and copy them to the proper locations:

    • /etc/grid-security for the host certificate

    • /etc/grid-security/ldap for your LDAP certificate

    • $HOME/.globus for the user certificate

    Ensure that the certificates for the trusted CA are saved in the directory /etc/grid-security/certificates/. For example, the file 42864e48.0 is the trusted certificate for Globus Certification Authority.

    After installing the host certificate, proceed with the next phase of installation, installing the Master Managed Job Factory Service (MMJFS), as described in the next section.

Phase 3: Installing Master Managed Job Factory Service

After you have the host certificate in place, install the Master Managed Job Factory Service (MMJFS), logged in as the user you performed the core installation as.

To Install MMJFS

  1. Change directory to the <GLOBUS_SOURCE_INSTALLER> directory, and run the install-gt3-mmjfs installation script.

  2. It is recommended that you edit the install-gt3-mmjfs script and append \ -verbose to the definitions of the GPT_BUILD and GPT_INSTALL variables.

    This recommendation increases verbosity. It is recommended that you capture the installation log to a file as follows:

    $ ./install-gt3-mmjfs <GLOBUS_LOCATION> 2>&1| tee install-mmjfs.log
  3. After the script exits, check the log for errors:

  4. $ grep ERROR install-mmjfs.log

    If there are no errors, continue with the installation. Otherwise, check the log file to find the cause of the installation error.

  5. Log in as the super-user, and run the script setperms.sh:

  6. # $<GLOBUS_LOCATION>/bin/setperms.sh

    Proceed to the next section for configuration and testing.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020