OpenShift 2.3.0.Beta1 What's New

< Main Index CDI Tools >

OpenShift Express Console

OpenShift Express Console

OpenShift Express console is a view where you can get easy access to your existing OpenShift accounts and applications. Actions in the context menu allow you manage your user accounts, domains, applications, embedded cartridges etc.

OpenShift Express Console

Related Jira

Context menu for Applications

Right click on Applications for easy access to common operations.

These operations currently include:

  • Web Browser - opens the url for the application.
  • Remote Console - opens the remote console for the application - this tails the logging files for your application.
  • Edit embeddable Cartridges - allow you to add/remove cartridges from your application.
  • Import application - starts the OpenShift wizard preconfigured to import the selected application
  • Create a server Adapter - setup a server adapter for the applictation
  • Properties - shows the properties view

Properties Details to the item selected in the OpenShift console are shown in the Properties view

OpenShift Express Properties

Related Jira

Save password You can now optionally save your OpenShift user password in the secure storage. Avoiding you to have to type in the password on every interaction with OpenShift.

Related Jira

Embedded cartridges "Edit embed cartridges" allow you to add or remove embedded cartridges for your applications. This is available by right-clicking on the application in the Express Console.

Creation and Import Wizards

Create or Use Existing Application You may now create a new OpenShift application and import it to your workspace in a single flow. Choose name, type, any embedded cartridges you want active on the project and the wizard will create the application on OpenShift and import it into Eclipse.

You can also choose to use an existing application.

Using the Browse... button you can choose from existing applications.

Workspace project When you create or import an OpenShift application, you may choose to either import it into a new project or to have the wizard enable the select OpenShift Application on an existing local project in your workspace. We currently allow you to enable OpenShift for Eclipse WTP projects but we'll widen this up in upcoming releases.

When you use an existing project what happens behind the scenes is that the project contents gets merged with the key metadata files from the OpenShift application and you can then deploy your own local application into OpenShift.

OpenShift Maven Profile When you enable OpenShift for an existing maven project in your workspace, we'll make sure it has a maven openshift profile which is used when the project is built on OpenShift. Note: We only add it to the pom if it's not present yet.

Related Jira

OpenShift Server

OpenShift Server Runtime

In M5 the server adapter was only created when importing an OpenShift application. Beta1 improves this a lot and allows you to create the server adapter independently of the application import.

Choose Create a Server Adapter in the context menu of the OpenShift Express Console and here you go, you get a fresh adapter for your existing OpenShift application.

create server adapter

We always try to stick to the Eclipse standards and therefore now also allow you to create the adapter like any other Eclipse WTP server adapter. Choose the Eclipse new server wizard and pick the OpenShift Express Server.

The second wizard page configures all OpenShift specific settings: your credentials, the OpenShift application and your workspace project.

Any Application Deployed

The new OpenShift Server Adapter is not bound to JBoss AS7 any more, it has no runtime connection.

You may therefore use it to publish to any OpenShift application. The prior limitation that restricted you to publish to jbossas-7 applications only, is gone.

Related Jira

OpenShift Server Editor The Server Editor now reports all relevant informations that are involved when publishing the workspace project to the OpenShift PaaS. You'll find the project, the OpenShift application, the host, user name, git branch and deployments directory.

Related Jira

Source & Binary Deployment

The new OpenShift Server adapter is now able to publish source and binary artifacts.

When you create the adapter, it will be associated to a git enabled OpenShift project in your workspace.

This project is used as the "source" deployment, thus any changes within this project is expected to be built via OpenShift source build process when git push occurs.

In addition we now also support you to drag any existing deployable artifact such as WTP projects, deployable datasources etc. to the OpenShift server. If these artifacts are not part of the "source" project the server adapter will package them up and place by default inside the /deployments folder of the project. Then when git push occurs these binaries will be part of the deployments on OpenShift for the "source" project.

This is what we call "binary" deployment and is useful for applications that for any reasons or another cannot be build remotely.

Note: OpenShift have a storage limit thus storing to many binaries or doing too many binary changes will make you reach this limit faster so be careful.

Related Jira