Skip Headers
Oracle® Enterprise Manager Ops Center Cloud Infrastructure API and CLI Reference Guide
12c Release 1 (12.1.4.0.0)

Part Number E25150-06
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

2 Getting Started

This chapter identifies the prerequisites for the cloud infrastructure APIs and CLI, and describes their installation and configuration.

The following topics are covered in this chapter:

2.1 Prerequisites

The following prerequisites must be met before using the APIs and CLI:

  • Installation of Java Runtime Environment (JRE) or Java Development Kit (JDK) version 1.6 or later appropriate for the platform where the APIs and CLI will be run or installed

  • Access to the Enterprise Controller

2.2 Installation

This section explains the installation process for the APIs and CLI.

2.2.1 Cloud Infrastructure API

The Web service is automatically installed on the Enterprise Controller as part of the Oracle Enterprise Manager Ops Center installation process. No further steps are required.

2.2.2 Cloud Infrastructure Java Client API

The Java Client API is delivered as a package with the Oracle Enterprise Manager Ops Center product. This package can be installed as a standalone package on a different computer with a connection to the Enterprise Controller.

Package Name Operating System
ORCL-sysman-iaas-api.pkg Oracle Solaris
orcl-sysman-iaas-api.rpm Linux

To install this package, enter the following commands as root user:

  • For Oracle Solaris:

    # cd <repo>/src/dvd/SunOS_i386/Product/components/packages/
    # pkgadd -d ORCLsysman-iaas-api.pkg
    
  • For Linux:

    # cd <repo>/src/dvd/Linux_i686/Product/components/packages/
    # rpm -i orcl-sysman-iaas-api.rpm
    

The API jar files from the package are stored at /opt/oracle/iaas/iaas-java-api.

Before you use the API JAR file, set the JAVA_HOME environment variable and ensure that the environment variable is part of your PATH.

2.2.3 Cloud Infrastructure CLI

The cloud infrastructure CLI is delivered as a separate package with the Oracle Enterprise Manager Ops Center product. This package can be installed as standalone package on a different computer with a connection to the Enterprise Controller.

Package Name Operating System
ORCLsysman-iaas-cli.pkg Oracle Solaris
orcl-sysman-iaas-cli.rpm Linux

To install this package, enter the following commands as root user:

  • For Oracle Solaris:

    # cd <repo>/src/dvd/SunOS_i386/Product/components/packages/
    # pkgadd -d ORCLsysman-iaas-cli.pkg
    
  • For Linux:

    # cd <repo>/src/dvd/Linux_i686/Product/components/packages/
    # rpm -i orcl-sysman-iaas-cli.rpm
    

The files from the package are stored at /opt/oracle/iaas/cli. To execute the CLI commands, the user must have permissions to access this directory.

Before using the cloud infrastructure CLI:

  1. Set the JAVA_HOME environment variable and ensure that the environment variable is part of your PATH:

    • Korn and bash shells:

      export JAVA_HOME=<jdk-install-dir>
      export PATH=$JAVA_HOME/bin:$PATH
      
    • Bourne shell:

      JAVA_HOME=<jdk-install-dir>
      export JAVA_HOME
      PATH=$JAVA_HOME/bin:$PATH
      export PATH
      
    • C shell:

      setenv JAVA_HOME <jdk-install-dir>
      setenv PATH $JAVA_HOME/bin:$PATH
      export PATH=$JAVA_HOME/bin:$PATH
      
  2. Set the IAAS_HOME environment variable:

    • Korn and bash shells:

      export IAAS_HOME=/opt/oracle/iaas/cli
      
    • Bourne shell:

      IAAS_HOME=/opt/oracle/iaas/cli
      export IAAS_HOME
      
    • C shell:

      setenv IAAS_HOME /opt/oracle/iaas/cli
      

2.3 Next Steps

Before the cloud administration can use the APIs or the CLI, the cloud administrator must complete the following tasks:

  1. Create vDC and an account for the vDC.

  2. Create a cloud user and associate the user with the account and vDC.

After getting the cloud user credentials, a cloud user must create an access key for the account in order to manage any resource in the account. For more information, see "Creating an Access Key".