anchor.diff:  
   $ oc project <projectname>
   ----
  +
  +. Create a sample project as described in link:#fuse-create-an-application-from-the-maven-archetype-catalog[Create an Application from the Maven Archetype Catalog].
   
   . Build and push the project to OpenShift. You can use following maven goals for building and pushing docker images.
   
  
positive.code: 
  Begin by selecting the archetype which matches the type of application you would like to create.
  
  ==== Simple Workflow to Create an Application from Maven Archetype Catalog
  
  . Use the Maven archetype catalog to create a sample project with the required resources. In order to use archetypes it is important to configure the Maven repositories which holds the archetypes and artifacts you may need:
  
  * JBoss Fuse repository: `https://repo.fusesource.com/nexus/content/groups/public/`
  * RedHat GA repository: `https://maven.repository.redhat.com/ga`
  +
  You can then use the Maven archetype catalog to create a sample project with the required resources. For example, the following command will create a sample project:
  +
  ----
  $ mvn archetype:generate \
    -DarchetypeCatalog=https://repo.fusesource.com/nexus/content/groups/public/archetype-catalog.xml \
    -Dfilter=io.fabric8.archetypes:
  ----
  
  . This will create a maven project with all required dependencies. Maven properties and plug-ins that are used to create Docker images are added to the *_pom.xml_* file.
  
  . Set the following environment variables to communicate with OpenShift and a Docker daemon:
  
  
negative.code: Red Hat JBoss Fuse Integration Services provides a set of tools and containerized xPaaS images that enable development, deployment, and management of integration microservices within OpenShift.
  
  [IMPORTANT]
  ====
  There are significant differences in supported configurations and functionality in Fuse Integration Services compared to the standalone JBoss Fuse product.
  ====
  
  === Differences Between Fuse Integration Services and JBoss Fuse
  There are several major functionality differences:
  
  * Fuse Management Console is not included as Fuse administration views have been integrated directly within the OpenShift Web Console.
  * An application deployment with Fuse Integration Services consists of an application and all required runtime components packaged inside a Docker image. Applications are not deployed to a runtime as with Fuse, the application image itself is a complete runtime environment deployed and managed through OpenShift.
  * Patching in an OpenShift environment is different from standalone Fuse since each application image is a complete runtime environment. To apply a patch, the application image is rebuilt and redeployed within OpenShift. Core OpenShift management capabilities allow for rolling upgrades and side-by-side deployment to maintain availability of your application during upgrade.
  * Provisioning and clustering capabilities provided by Fabric in Fuse have been replaced with equivalent functionality in Kubernetes and OpenShift. There is no need to create or configure individual child containers as OpenShift automatically does this for you as part of deploying and scaling your application.
  * Messaging services are created and managed using the A-MQ xPaaS images for OpenShift and not included directly within Fuse. Fuse Integration Services provides an enhanced version of the camel-amq component to allow for seamless connectivity to messaging services in OpenShift through Kubernetes.
  * Live updates to running Karaf instances using the Karaf shell is strongly discouraged as updates will not be preserved if an application container is restarted or scaled up. This is a fundamental tenet of immutable architecture and essential to achieving scalability and flexibility within OpenShift.
  
  Additional details on technical differences and support scope are documented in an associated https://access.redhat.com/articles/2112371[KCS article].
  
  == Using Fuse Integration Services
  You can start using Fuse Integration Services by creating an application and deploying it to OpenShift using one of the following application development workflows: 
  
  * Fabric8 Maven Workflow
  * OpenShift Source-to-Image (S2I) Workflow
  
  Both workflows begin with creating a new project from a Maven archetype.
  
  === Maven Archetypes Catalog
  The Maven Archetype catalog includes the following examples:
  
  |===
  