Oracle® Enterprise Pack for Eclipse User's Guide
Release 12.1.3.1
E53428-02
  Go To Table Of Contents
Contents

Previous
Previous
 
Next
Next
 

6 Integrating Oracle Cloud Services

Oracle Cloud Service enables you to use the cloud to develop, collaborate, and deploy your OEPE applications from one central source.

Currently OEPE supports only the Java Cloud Service, which includes the WebLogic server, and optional Oracle Cloud database services.

For more information about Oracle Cloud, or to open an Oracle Cloud account, visit http://cloud.oracle.com.

This document contains the following:

6.1 Adding Your Oracle Cloud Services

To add an Oracle Cloud Service to your application use the Cloud view, from the Java EE perspective.

To add a Cloud Service:

  1. In the OEPE application Cloud view, choose Connect. The Oracle Cloud dialog appears, as shown in Figure 6-1.

  2. Enter the details in the dialog fields. When you sign up for an Oracle Cloud Service, the configuration details are emailed to you.

  3. Click Test Connection. You can also test with Perform whitelist scan prior to publish. This does a local test to determine if your application deploys successfully to Oracle Cloud.

  4. Click Finish.

Figure 6-1 Oracle Cloud Connection - Add Details

Image as described in the surrounding text

6.1.1 Using the Cloud View

Add and manage your cloud services using the Cloud view. Right clicking from the Cloud node gives you options to open your browser-based cloud portals, as well as Cloud connection properties, as shown in Figure 6-2 and Figure 6-3.

Right-clicking from your service node gives you access to a variety of features including Service Instances, Service Jobs, and the Service web-based console, as shown in Figure 6-4. For more information see Viewing the Java Cloud Service Jobs Log, and Viewing the Java Cloud Service Instance Log.

Figure 6-2 Cloud View - Right-Click Server Instance Options

Image as described in the surrounding text

Figure 6-3 Cloud View And Corresponding Cloud Service Portal

Image as described in the surrounding text

Figure 6-4 Cloud View - Right-Click Java Service Options

Image as described in the surrounding text

6.2 Getting up and Running with Your Java Cloud Service

With the Oracle Java Cloud Service you can manage the backend infrastructure of your OEPE applications without exposing the runtime to its service users. When you sign up for the Java Oracle Cloud Service, you get a deployment target for your OEPE application using a set of Java EE release 5, Java EE release 6, and Oracle WebLogic Server capabilities, in addition to a My Services web-based interface to manage your cloud tools.

For more information on the Java Cloud Service see, http://cloud.oracle.com.

To add Java Cloud Service to your OEPE application:

  1. Subscribe to the Java Cloud Service at http://cloud.oracle.com. You will get an email with the service details, which you will need to configure your OEPE application for the cloud.

  2. Open your application.

  3. Follow the steps in Adding Your Oracle Cloud Services.

6.2.1 Viewing the Java Cloud Service Jobs Log

The Oracle Java Cloud Service Jobs log, shown in Figure 6-5, provides comprehensive information on the jobs being executed by the Java Cloud Service, including Id, status, duration, and nature of your operation.

Figure 6-5 Oracle Java Cloud Service - Jobs Window

Oracle Java Cloud Service Service Jobs Window

To view the Oracle Java Cloud Service - Jobs log:

Right-click your service in the Servers view and select Java Cloud Service Instance Log.

You can filter jobs shown in the window by clicking the Filter icon in the toolbar to open the Jobs Filter, shown in Figure 6-6.

Figure 6-6 Jobs Filter Dialog

Jobs Filter Dialog

6.2.2 Viewing the Java Cloud Service Instance Log

The Oracle Java Cloud Service Instance log provides detail on the performance of your services, as shown in Figure 6-7.

Figure 6-7 Oracle Java Cloud Service Instance Log

Oracle Java Cloud Service Instance Log

To view the Oracle Java Cloud Service Jobs log:

Right-click your service in the Servers view and select Java Cloud Service Jobs.

You can select the Filter icon in the toolbar to filter service instances using the Events Filter dialog, shown in Figure 6-8.

Figure 6-8 Events Filter - Service Instances

Events Filter

6.3 Validating with the Whitelist Scan

The whitelist scan feature enables you to locally ensure that your application is valid for deployment to Oracle Cloud. Whitelist scanning can be invoked in three ways:

6.4 Deploying to the Cloud

OEPE enables you to deploy your project to Oracle Cloud or Oracle WLS, depending on your preference.

To deploy to Oracle Cloud, use one of the following methods:

6.5 Oracle Developer Cloud Service

OEPE includes integration for Oracle Developer Cloud Service, which exposes the most common development tasks from the cloud directly from within the application. Oracle Developer Cloud Service is a collection of software and services hosted on the Oracle Cloud. It is a cloud-based software development Platform as a Service (PaaS) and a hosted environment for your application development infrastructure. It provides open-source, standards-based solutions to develop, collaborate, and deploy applications within Oracle Cloud.

Oracle Developer Cloud Service integration with OEPE includes the following:

6.5.1 Logging In to Oracle Developer Cloud Service

You can log in to Oracle Developer Cloud Service from Oracle Cloud view.

To open Oracle Cloud view:

  1. Click Window > Show View > Oracle Cloud.

    If the Oracle Cloud option is not available in the Show View submenu, click Other and choose Oracle Cloud > Oracle Cloud in the Show View dialog.

  2. Click Connect.


Tip:

The Oracle Cloud view is available in Java EE perspective, by default. To open the Java EE perspective, select Window > Open Perspective > Java EE.


If you are connecting to Oracle Developer Cloud Service for the first time, click the Connect link. In the Oracle Cloud Service Connection dialog, enter the following:

  • Data Center: Select the Oracle Cloud data center.

  • Identity Domain: Enter the identity domain of Oracle Developer Cloud Service.

  • Username and Password: Enter the user name and password.

  • Connection Name: Enter a name for the service instance, if required. By default, the connection name is set to the identity domain name.

After validating credentials, you are logged in to Oracle Developer Cloud Service from OEPE. After you log in, Oracle Cloud view displays all projects that are assigned to you.

6.5.2 Getting Up and Running with Your Developer Cloud Service

To log in to Oracle Developer Cloud Service from OEPE, open the Oracle Cloud view and click New Cloud Connection Wizard. The Oracle Cloud view is available in Java EE perspective. To open Java EE perspective, select Window > Open Perspective > Java EE.

To add Developer Cloud Service to your OEPE application:

  1. Subscribe to the Developer Cloud Service at http://cloud.oracle.com. You will get an email with the service details, which you will need to configure your OEPE application for your cloud service.

  2. Open your application.

  3. Follow the steps in Section 6.1, "Adding Your Oracle Cloud Services". Choose the Developer Cloud Service from the server list.

6.5.3 Using the Oracle Developer Services Cloud View

Oracle Cloud View displays all your projects, and links to the common features of your service.

You can have multiple Oracle Developer Cloud Service accounts in the Oracle Cloud view. To add another account, select Oracle Public Cloud in Oracle Cloud view, right-click, and select New. Select the data center, enter the identity domain, user name and credentials, and click Finish.

Oracle Cloud view enables you to run the following actions for each project:

6.5.4 Importing an Oracle Developer Cloud Service Project

Importing a project from Oracle Developer Cloud Service to OEPE Workspace creates a local clone of Oracle Developer Service Git repository. After creating the local Git clone, Eclipse projects can be imported into the workspace.

To import a Project from Oracle Developer Cloud Service to OEPE Workspace:

  1. In the Oracle Cloud view, expand the project, and select the Git repository from the Source node.

  2. Double-click the selected Git repository to clone it to local machine.

    A dialog appears informing that Git repository is ready for cloning. Click OK.

  3. The cloned repository will be visible in Git Repositories view. If the view is not visible, open it from Window > Show View > Git Repositories.

  4. Right-click the repository name in the Git Repositories view, and choose Import Projects.

  5. Select a wizard to use for importing projects page of Import Projects from Git Repository dialog, choose the desired option, and click Next.

    If you are not sure which option to select, select the Import as General Project option.

  6. In the Import Project page of Import Projects from Git Repository dialog, verify the project name and directory, and click Finish.

6.5.5 Exporting a Project from OEPE to Oracle Developer Cloud Service

Exporting a project from OEPE workspace to Oracle Developer Cloud Service is useful if you already have an active local Git repository and want to push the source to the hosted Git repository.

To export a Project from OEPE Workspace to Oracle Developer Cloud Service:

  1. Select the project in Project Explorer, right-click, and choose Team > Share Project.

  2. In the Share Project wizard, select Git as the repository type, and click Next.

  3. In the Configure Git Repository page, select the remote Git repository you would want to export the project to, and click Finish.

  4. In Project Explorer, select the project, right-click, and choose Team > Commit.

  5. In the Commit Changes dialog, enter commit description, select the files you want to commit, and click Commit and Push.

  6. In the Push Results dialog, click OK to export the project to Oracle Developer Cloud Service.

6.5.6 Using eGit for DCS Source Control and Versioning

OEPE uses eGit for source control and version on DCS projects. EGit is an Eclipse Team provider for Git. Git is a distributed SCM, which means every developer has a full copy of all history of every revision of the code, making queries against the history very fast and versatile. For more information in eGit, see http://www.eclipse.org/egit/.

To open a Git repository view in OEPE:

  • Select Window > Show View > Git Repositories.

In some cases, the Git option my be under other...

On the right side of the Git view is a toolbar with the icons that you click to manage your Git features. Icon actions include:

  • Collapse all

  • Add an existing local repository

  • Clone a Git repository

  • Create a new Git repository

  • Refresh your repository

  • Adjust layout preferences

  • Display latest branch commits

6.5.7 Using Git Tools in OEPE

Using the Team context menu in Project Explorer, you can perform various Git actions such as commit a project to Git repository, commit file changes, merge, branch, and push changes to the hosted Git repository.

To add a project to Local Git Clone:

  1. Right-click the project, and select Team > Share Project.

  2. In the Share Project wizard, select Git from the list of available source control systems, and click Next.

  3. In Configure Git Repository page, select the Git repository, and click Finish.

6.5.8 Committing Changes to Oracle Developer Cloud Service Git Repository

Committing changes to the Oracle Developer Cloud Service Git repository is a two-step process: committing to the local Git clone or branch, and then pushing the changes to the cloud repository

To commit changes to Oracle Developer Cloud Service Git Repository:

  1. To commit a change, right click the file, directory, or project and select Team > Commit.

  2. In the Commit Changes dialog, add a commit message and select the files to be committed to the local repository, and click Commit.


    Notes:

    • If you have an Active Task, the Task ID and URL are automatically added to your commit message. For more information, see Associating a Task with a Commit Transaction.

    • All committed changes appear in the home page of Browse module and the Activity Feed of Oracle Developer Cloud Service web interface.


6.5.9 Pushing Changes From the Local Git Repository to Oracle Developer Cloud Service Git Repository

To push latest updates from the local cloned Git repository to the Git cloud repository, use the Push command.

To push changes to Oracle Developer Cloud Service Git Repository

  1. Open the Git Repositories view.

  2. Right-click the repository, and then select Push Upstream.

  3. In Push Results dialog, verify the message details, and then click OK.

6.5.10 Managing Documentation

You can also add wiki pages to your project from OEPE. Select and expand the project in Oracle Cloud view, select Documentation, right-click, select Open in Browser. The Wiki module home page opens in the web browser

From the Wiki home page, you can add or edit wiki pages of the project. If you have administrative privileges of a project, you can change the wiki markup type.

For more information about managing documentation and wiki pages, see Section 6.5.10, "Managing Documentation".

6.5.11 Updating Tasks

By default, following task queries are available in the Tasks node of Oracle Cloud view:

  • All: Lists all tasks of the project

  • Mine: Lists all tasks assigned to you

  • Open: Lists all open tasks

  • Recent: Lists all recently changed tasks

  • Related: Lists all tasks related to you

Double-click a query to run it, and then double-click a task to open it in the Task Editor.

You can also perform the following tasks related actions from OEPE:

  • Create a new query and import tasks, features, and defects from Oracle Developer Cloud Service

  • Update imported tasks from OEPE

  • Create local tasks and export them to Oracle Developer Cloud Service

6.5.11.1 Importing Tasks from Oracle Developer Cloud Service With a Custom Query

To import tasks from Oracle Developer Cloud Service, you would need to create a search query. For example, you can create a query to import all open defects assigned to you.

To import tasks with a custom query:

  1. Select Tasks node of your project in Oracle Cloud view.

  2. Right-click, and choose New Query.

  3. In the Oracle Developer Cloud Service Tasks Query dialog, enter the search criteria.

    For example, if you want to import all open defects assigned to you, enter the name of the query, select your name from the Person list, select Defect as Type, and Assigned as Status.

  4. Click Finish.

All tasks matching the specified criteria will get imported to Task List view. To open Task List view, select Window > Show View > Task List. You can create multiple queries as per your requirement.

6.5.11.2 Creating a Local Task

To create a task, click the New Task icon in the Task List toolbar. When you create a Task, you can choose the repository as a local repository, or your project's repository on Oracle Developer Cloud Service.

If you choose Oracle Developer Cloud Service as the repository, the task will be automatically added to Oracle Developer Cloud Service and reflected in Tasks home page of the web interface.

6.5.11.3 Editing a Task

To view and edit a specific task, double-click the task in the Task List view to load it in the Task Editor. Update the task, and click Submit. If it is a local task, it will be updated in local task repository. If it is a Oracle Developer Cloud Service task, it will be automatically updated in Oracle Developer Cloud Service task repository.

6.5.11.4 Synchronizing Tasks with Oracle Developer Cloud Service

To synchronize a task (or a query) between OEPE and Oracle Developer Cloud Service, right-click the task (or the query) in Task List view, and choose Synchronize.

6.5.11.5 Associating a Task with a Commit Transaction

If you want to associate a task with a commit transaction, you should activate the task first. To activate a task, select and right-click the task in Task List view, and choose Activate.

OEPE also provides integration with Mylyn. Activating a task enables Mylyn to track which files are related to the current task. Mylyn automatically hides files that are not related to the active task. When committing changes to Git for the Active task, your commit message automatically references the Task ID in Oracle Developer Cloud Service. This effectively creates a link between the code commit and the task allowing for easy traceability. Links between source commits and Tasks are also reflected in the web interface of Oracle Developer Cloud Service.

You can find more information about working with Mylyn Tasks and the Tasks user interface in the Mylyn User Guide at the following URL:

http://wiki.eclipse.org/Mylyn_User_Guide

6.5.12 Monitoring Hudson Builds

To view all jobs of the Hudson builds, expand the Build node of a project in Oracle Cloud view. To perform any action, select the job (or the build) and click Open in Browser. The Builds module of Oracle Developer Cloud Service opens in the web browser.