Installation Guide

1. On the command line, move into the $SERVER_HOME/bin/ directory.
2. In a Unix environment run:

   ./standalone.sh

   Copy to Clipboard Toggle word wrap
   In a Windows environment run:

   ./standalone.bat

   Copy to Clipboard Toggle word wrap

1. On the command line, move into the $SERVER_HOME/bin/ directory.
2. In a Unix environment run:

   ./standalone-secure.sh

   Copy to Clipboard Toggle word wrap
   In a Windows environment run:

   ./standalone-secure.bat

   Copy to Clipboard Toggle word wrap

1. Navigate to http://localhost:8080/business-central in a web browser. If the user interface has been configured to run from a domain name, substitute localhost for the domain name. For example http://www.example.com:8080/business-central.
2. Log in with the user credentials that were created during installation. For example: User = helloworlduser and password = Helloworld@123.

1. Download the jboss-bpmsuite-brms-VERSION-supplementary-tools.zip, which contains Apache Zookeeper, Apache Helix, and quartz DDL scripts. After downloading, unzip the archive: the Zookeeper directory ($ZOOKEEPER_HOME) and the Helix directory ($HELIX_HOME) are created.
2. Now Configure ZooKeeper:
   1. In the ZooKeeper directory, go to conf directory and do the following:

      cp zoo_sample.cfg zoo.cfg

      Copy to Clipboard Toggle word wrap
   2. Open zoo.cfg for editing and adjust the settings including the following:

      # the directory where the snapshot is stored.
      dataDir=$ZOOKEEPER_HOME/data/
      # the port at which the clients connects
      clientPort=2181
      server.1=server1:2888:3888
      server.2=server2:2888:3888
      server.3=server3:2888:3888
      

      Copy to Clipboard Toggle word wrap
      Make sure the dataDir location exists and is accessible.
   3. Assign a node ID to each member that will run ZooKeeper. For example, use "1", "2" and "3" respectively for node 1, node 2 and node 3 respectively. ZooKeeper should have an odd number of instances, at least 3 in order to recover from failure.
      The node ID is specified in a field called myid under the data directory of ZooKeeper on each node. For example, on node 1, run: $ echo "1" > /zookeeper/data/myid
3. Set up ZooKeeper, so you can use it when creating the cluster with Helix:
   1. Go to the $ZOOKEEPER_HOME/bin/ directory and start ZooKeeper:

      ./zkServer.sh start

      Copy to Clipboard Toggle word wrap
      You can check the ZooKeeper log in the $ZOOKEEPER_HOME/bin/zookeeper.out file. Check this log to ensure that the 'ensemble' (cluster) is formed successfully. One of the nodes should be elected as leader with the other two nodes following it.
4. Once the ZooKeeper ensemble is started, the next step is to configure and start Helix. Helix only needs to be configured once and from a single node. The configuration is then stored by the ZooKeeper ensemble and shared as appropriate.
   Set up the cluster with the ZooKeeper server as the master of the configuration:
   1. Create the cluster by providing the ZooKeeper Host and port as a comma separated list:

      $HELIX_HOME/bin/helix-admin.sh --zkSvr ZOOKEEPER_HOST:ZOOKEEPER_PORT --addCluster CLUSTER_NAME

      Copy to Clipboard Toggle word wrap
   2. Add your nodes to the cluster:

      $HELIX_HOME/bin/helix-admin.sh --zkSvr ZOOKEEPER_HOST:ZOOKEEPER_PORT --addNode CLUSTER_NAME NODE_NAMEUNIQUE_ID

      Copy to Clipboard Toggle word wrap

      Example 6.1. Adding three cluster nodes

      ./helix-admin.sh --zkSvr server1:2181,server2:2181,server3:2181 --addNode bpms-cluster nodeOne:12345
      ./helix-admin.sh --zkSvr server1:2181,server2:2181,server3:2181 --addNode bpms-cluster nodeTwo:12346 
      ./helix-admin.sh --zkSvr server1:2181,server2:2181,server3:2181 --addNode bpms-cluster nodeThree:12347

      Copy to Clipboard Toggle word wrap
5. Add resources to the cluster.

   Example 6.2. Adding vfs-repo as resource

   ./helix-admin.sh --zkSvr server1:2181,server2:2181,server3:2181 --addResource bpms-cluster vfs-repo 1 LeaderStandby AUTO_REBALANCE

   Copy to Clipboard Toggle word wrap
6. Rebalance the cluster with the three nodes.

   Example 6.3. Rebalancing the bpms-cluster

   ./helix-admin.sh --zkSvr server1:2181,server2:2181,server3:2181 --rebalance bpms-cluster vfs-repo 3
   

   Copy to Clipboard Toggle word wrap
   In the above command, 3 stands for three zookeeper nodes.
7. Start the Helix controller in all the nodes in the cluster.

   Example 6.4. Starting the Helix controller

   ./run-helix-controller.sh --zkSvr server1:2181,server2:2181,server3:2181 --cluster bpms-cluster 2>&1 > /tmp/controller.log &

   Copy to Clipboard Toggle word wrap

Procedure 6.1. Stopping Helix and Zookeeper

1. Stop JBoss EAP server processes.
2. Stop the Helix process that has been created by run-helix-controller.sh, for example,kill -15 <pid of HelixControllerMain>.
3. Stop ZooKeeper server using the zkServer.sh stop command.

1. Set up the database. Make sure to use one of the supported non-JTA data source. Note, that since Quartz need a non-JTA data source, you cannot use the Business Central data source. In the example code, PostgreSQL with the user bpms and password bpms is used. This database will need to be connected to your application server, so make sure to keep a note on the database information and credentials.
2. Create Quartz tables on your database to allow timer events synchronization. To do so, use the DDL script for your database, which is available in the extracted supplementary zip archive in QUARTZ_HOME/docs/dbTables.
3. Create the Quartz configuration file quartz-definition.properties in $JBOSS_HOME/PROFILE/configuration/ directory and define the Quartz properties.

   Example 6.5. Quartz configuration file for a PostgreSQL database

    #============================================================================
   # Configure Main Scheduler Properties  
   #============================================================================
   
   org.quartz.scheduler.instanceName = jBPMClusteredScheduler
   org.quartz.scheduler.instanceId = AUTO
   
   #============================================================================
   # Configure ThreadPool  
   #============================================================================
   
   org.quartz.threadPool.class = org.quartz.simpl.SimpleThreadPool
   org.quartz.threadPool.threadCount = 5
   org.quartz.threadPool.threadPriority = 5
   
   #============================================================================
   # Configure JobStore  
   #============================================================================
   
   org.quartz.jobStore.misfireThreshold = 60000
   
   org.quartz.jobStore.class=org.quartz.impl.jdbcjobstore.JobStoreCMT
   org.quartz.jobStore.driverDelegateClass=org.quartz.impl.jdbcjobstore.PostgreSQLDelegate
   org.quartz.jobStore.useProperties=false
   org.quartz.jobStore.dataSource=managedDS
   org.quartz.jobStore.nonManagedTXDataSource=notManagedDS
   org.quartz.jobStore.tablePrefix=QRTZ_
   org.quartz.jobStore.isClustered=true
   org.quartz.jobStore.clusterCheckinInterval = 20000
   
   #============================================================================
   # Configure Datasources  
   #============================================================================
   org.quartz.dataSource.managedDS.jndiURL=jboss/datasources/psbpmsDS
   org.quartz.dataSource.notManagedDS.jndiURL=jboss/datasources/quartzNotManagedDS
   

   Copy to Clipboard Toggle word wrap

   Note the configured datasources that will accommodate the two Quartz schemes at the very end of the file.

   Important

   The recommended interval for cluster discovery is 20 seconds and is set in the org.quartz.jobStore.clusterCheckinInterval of the quartz-definition.properties file. Depending on your set up consider the performance impact and modify the setting as necessary.
   Also note the org.quartz.jobStore.driverDelegateClass property that defines the DB dialect to be used when communicating with the set database (in this example, org.quartz.impl.jdbcjobstore.PostgreSQLDelegate. When using Oracle, use org.quartz.impl.jdbcjobstore.oracle.OracleDelegate).

1. Install your JDBC driver as a core module: copy the driver jar to $EAP_HOME/modules/system/layers/base/ and create a module.xml file in the directory.
2. Edit the module.xml file as of the respective module XSD.

   Example 6.6. The module.xml file content for a PostgreSQL datasource

   <module xmlns="urn:jboss:module:1.0" name="org.postgresql">
     <resources>
       <resource-root path="postgresql-jdbc.jar"/>
     </resources>
   
     <dependencies>
       <module name="javax.api"/>
       <module name="javax.transaction.api"/>
     </dependencies>
   </module>
   

   Copy to Clipboard Toggle word wrap
3. Configure individual server nodes in the main-server-group element in the $EAP_HOME/domain/configuration/host.xml file with properties defined in Table 6.1, “Cluster node properties”:
   Note that a when configuring a JBoss EAP cluster with Zookeeper, a different number of JBoss EAP nodes than Zookeeper nodes is possible (keeping in mind that Zookeeper should to have an odd number of nodes). However, having the same node count for both Zookeeper and JBoss EAP is considered best practice.
   Expand

   Table 6.1. Cluster node properties

   Property name	Value	Description
   jboss.node.name	nodeOne	node name unique within the cluster
   org.quartz.properties	/bpms/quartz-definition.properties	absolute path to the quartz configuration file
   org.uberfire.cluster.autostart	true	This value delays VFS clustering until the application is fully initialized to avoid conficts when all cluster members create local clones.
   org.uberfire.cluster.id	bpms-cluster	Helix cluster name
   org.uberfire.cluster.local.id	nodeOne_12345	unique ID of the Helix cluster node Note that : is replaced with _.
   org.uberfire.cluster.vfs.lock	vfs-repo	name of the resource defined on the Helix cluster
   org.uberfire.cluster.zk	server1:2181	Zookeeper location
   org.uberfire.metadata.index.dir	/home/jbpm/node[N]/index	location where the index for search is to be created (maintained by Apache Lucene)
   org.uberfire.nio.git.daemon.host	nodeOne	the name of the daemon host machine in a physical cluster.
   org.uberfire.nio.git.daemon.port	9418	port used by the VFS repo to accept client connections The port must be unique for each cluster member.
   org.uberfire.nio.git.dir	/home/jbpm/node[N]/repo	GIT (VFS) repository location on node[N]
   org.uberfire.nio.git.ssh.host	nodeOne	the name of the SSH host machine in a physical cluster.
   org.uberfire.nio.git.ssh.port	8003	the unique port number for ssh access to the GIT repo for a cluster running on physical machines.
   org.uberfire.nio.git.ssh.hostport and org.uberfire.nio.git.daemon.hostport	8003 and 9418	In a virtualized environment, the outside port to be used.

   Show more

   Example 6.7. Cluster nodeOne configuration

   <system-properties>
   				
     <property name="org.uberfire.nio.git.dir" value="/tmp/bpms/nodeone" boot-time="false"/>
     <property name="jboss.node.name" value="nodeOne" boot-time="false"/>
     
     <property name="org.uberfire.cluster.id" value="bpms-cluster" boot-time="false"/>
     <property name="org.uberfire.cluster.zk" value="server1:2181,server2:2181,server3:2181" boot-time="false"/>
     <property name="org.uberfire.cluster.local.id" value="nodeOne_12345" boot-time="false"/>
     <property name="org.uberfire.cluster.vfs.lock" value="vfs-repo" boot-time="false"/>
     <property name="org.uberfire.cluster.autostart" value="true" boot-time="true"/>
     
     <property name="org.uberfire.nio.git.daemon.host" value="nodeOne" />
     <property name="org.uberfire.nio.git.daemon.port" value="9418" boot-time="false"/>
     <property name="org.uberfire.nio.git.daemon.hostport" value="9418" boot-time="false"/>
     
     <property name="org.uberfire.nio.git.ssh.port" value="8003" boot-time="false"/>
     <property name="org.uberfire.nio.git.ssh.hostport" value="8003" boot-time="false"/>
     <property name="org.uberfire.nio.git.ssh.host" value="nodeOne" />
     
     <property name="org.uberfire.metadata.index.dir" value="/tmp/jbpm/nodeone" boot-time="false"/>
     <property name="org.uberfire.nio.git.ssh.cert.dir" value="/tmp/jbpm/nodeone" boot-time="false"/>
     
     <property name="org.quartz.properties" value="/tmp/jbpm/quartz/quartz-db-postgres.properties" boot-time="false"/>
     
   </system-properties>

   Copy to Clipboard Toggle word wrap

   Example 6.8. Cluster nodeTwo configuration

   <system-properties>
   				
     <property name="org.uberfire.nio.git.dir" value="/tmp/bpms/nodetwo" boot-time="false"/>
     <property name="jboss.node.name" value="nodeTwo" boot-time="false"/>
     
     <property name="org.uberfire.cluster.id" value="bpms-cluster" boot-time="false"/>
     <property name="org.uberfire.cluster.zk" value="server1:2181,server2:2181,server3:2181" boot-time="false"/>
     <property name="org.uberfire.cluster.local.id" value="nodeTwo_12346" boot-time="false"/>
     <property name="org.uberfire.cluster.vfs.lock" value="vfs-repo" boot-time="false"/>
     <property name="org.uberfire.cluster.autostart" value="true" boot-time="true"/>
     
     <property name="org.uberfire.nio.git.daemon.host" value="nodeTwo" />
     <property name="org.uberfire.nio.git.daemon.port" value="9418" boot-time="false"/>
     <property name="org.uberfire.nio.git.daemon.hostport" value="9418" boot-time="false"/>
     
     <property name="org.uberfire.nio.git.ssh.port" value="8003" boot-time="false"/>
     <property name="org.uberfire.nio.git.ssh.hostport" value="8003" boot-time="false"/>
     <property name="org.uberfire.nio.git.ssh.host" value="nodeTwo" />
     
     <property name="org.uberfire.metadata.index.dir" value="/tmp/jbpm/nodetwo" boot-time="false"/>
     <property name="org.uberfire.nio.git.ssh.cert.dir" value="/tmp/jbpm/nodetwo" boot-time="false"/>
     
     <property name="org.quartz.properties" value="/tmp/jbpm/quartz/quartz-db-postgres.properties" boot-time="false"/>				
   
   
   </system-properties>

   Copy to Clipboard Toggle word wrap

   Example 6.9. Cluster nodeThree configuration

   <system-properties>
   				
     <property name="org.uberfire.nio.git.dir" value="/tmp/bpms/nodethree" boot-time="false"/>
     <property name="jboss.node.name" value="nodeThree" boot-time="false"/>
     
     <property name="org.uberfire.cluster.id" value="bpms-cluster" boot-time="false"/>
     <property name="org.uberfire.cluster.zk" value="server1:2181,server2:2181,server3:2181" boot-time="false"/>
     <property name="org.uberfire.cluster.local.id" value="nodeThree_12347" boot-time="false"/>
     <property name="org.uberfire.cluster.vfs.lock" value="vfs-repo" boot-time="false"/>
     <property name="org.uberfire.cluster.autostart" value="true" boot-time="true"/>
     
     <property name="org.uberfire.nio.git.daemon.host" value="nodeThree" />
     <property name="org.uberfire.nio.git.daemon.port" value="9418" boot-time="false"/>
     <property name="org.uberfire.nio.git.daemon.hostport" value="9418" boot-time="false"/>
     
     <property name="org.uberfire.nio.git.ssh.port" value="8003" boot-time="false"/>
     <property name="org.uberfire.nio.git.ssh.hostport" value="8003" boot-time="false"/>
     <property name="org.uberfire.nio.git.ssh.host" value="nodeThree" />
     
     <property name="org.uberfire.metadata.index.dir" value="/tmp/jbpm/nodethree" boot-time="false"/>
     <property name="org.uberfire.nio.git.ssh.cert.dir" value="/tmp/jbpm/nodethree" boot-time="false"/>
     
     <property name="org.quartz.properties" value="/tmp/jbpm/quartz/quartz-db-postgres.properties" boot-time="false"/>				
   
   
   </system-properties>

   Copy to Clipboard Toggle word wrap
4. Add management users as instructed in the Administration and Configuration Guide for Red Hat JBoss EAP and application users as instructed in Red Hat JBoss BPM Suite Administration and Configuration Guide.
5. Start the application server:

   ]$ $JBOSS_HOME/bin/domain.sh

   Copy to Clipboard Toggle word wrap
6. Check that the nodes are available.

1. Change the predefined persistence of the application to the required data base (PostgreSQL): in persistence.xml change the following:
   1. jta-data-source name to the source defined on the application server (java:jboss/datasources/psbpmsDS)
   2. hibernate dialect to be match the data source dialect (org.hibernate.dialect.PostgreSQLDialect)
2. Log on as the management user to the server Administration console of your domain and add the new deployments using the Runtime view of the console. Once the deployment is added to the domain, assign it to the correct server group (main-server-group).

Procedure 7.1. 

1. Download the following ZIP archives containing the required repositories:
   • https://access.redhat.com/jbossnetwork/restricted/listSoftware.html?product=bpm.suite&version=6.1.0
2. Unzip the downloaded ZIP files into an arbitrary location in a local file system.
3. Add entries for the unzipped repositories to Maven's settings.xml file. The following code sample contains a profile with the repositories, configuration of authentication for access to the repositories, and an activation entry for the profile:

   <?xml version="1.0" encoding="UTF-8" standalone="no"?>
   <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/xsd/settings-1.0.0.xsd">
     <localRepository/>
     <profiles>
       <!-- Profile with local repositories required by JBoss BRMS/JBoss BPM Suite -->
       <profile>
         <id>brms-bpms-local-profile</id>
         <repositories>
           <repository>
             <id>jboss-brms-bpmsuite-repository</id>
             <name>BRMS/BPMS 6.1.0 GA Repository</name>
             <url>file://<!-- path to the repository -->/jboss-brms-bpmsuite-6.1.0.GA-redhat-2-maven-repository/maven-repository</url>
             <layout>default</layout>
             <releases>
               <enabled>true</enabled>
               <updatePolicy>never</updatePolicy>
             </releases>
             <snapshots>
               <enabled>false</enabled>
               <updatePolicy>never</updatePolicy>
             </snapshots>
           </repository>
         </repositories>
         <pluginRepositories>
           <pluginRepository>
             <id>jboss-brms-bpmsuite-repository</id>
             <name>BRMS/BPMS 6.1.0 GA Repository</name>
             <url>file://<!-- path to the repository -->/jboss-brms-bpmsuite-6.1.0.GA-redhat-2-maven-repository/maven-repository</url>
             <layout>default</layout>
             <releases>
               <enabled>true</enabled>
               <updatePolicy>never</updatePolicy>
             </releases>
             <snapshots>
               <enabled>false</enabled>
               <updatePolicy>never</updatePolicy>
             </snapshots>
           </pluginRepository>
         </pluginRepositories>
       </profile>
     </profiles>
   
     <!-- Configuring pre-emptive authentication for the repository server -->
     <server>
       <id>brms-bpms-m2-repo</id>
       <username>admin</username>
       <password>admin</password>
       <configuration>
         <wagonProvider>httpclient</wagonProvider>
         <httpConfiguration>
           <all>
             <usePreemptive>true</usePreemptive>
           </all>
         </httpConfiguration>
       </configuration>
     </server>
     
     <!-- Alternative to enabling pre-emptive authentication - configuring 
          the Authorization HTTP header with Base64-encoded credentials
     <server>
       <id>brms-bpms-m2-repo</id>
       <configuration>
         <httpHeaders>
           <property>
             <name>Authorization</name>
             <value>Basic YWRtaW46YWRtaW4=</value>
           </property>
         </httpHeaders>
       </configuration>
     </server>
     -->
     
     <activeProfiles>
      <!-- Activation of the JBoss BRMS/JBoss BPM Suite profile -->
      <activeProfile>brms-bpms-local-profile</activeProfile>
     </activeProfiles>
   </settings>

   Copy to Clipboard Toggle word wrap

Procedure 7.2. Configuring Maven to Use the Online Repositories

1. Add entries for the online repositories and configuration of authentication for accessing them to Maven's settings.xml file as in the code sample below:

   <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0" 
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
         xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
   
     <profiles>
       <!-- Profile with online repositories required by BRMS/BPMS -->
       <profile>
         <id>brms-bpms-online-profile</id>
         <repositories>
           <repository>
             <id>jboss-ga-repository</id>
             <url>http://maven.repository.redhat.com/techpreview/all</url>
             <releases>
               <enabled>true</enabled>
             </releases>
             <snapshots>
               <enabled>false</enabled>
             </snapshots>
           </repository>
         </repositories>
         <pluginRepositories>
           <pluginRepository>
             <id>jboss-ga-plugin-repository</id>
             <url>http://maven.repository.redhat.com/techpreview/all</url>
             <releases>
               <enabled>true</enabled>
             </releases>
             <snapshots>
               <enabled>false</enabled>
             </snapshots>
           </pluginRepository>
         </pluginRepositories>
       </profile>    
     </profiles>
     
     <!-- Configuring pre-emptive authentication for the repository server -->
     <server>
       <id>brms-bpms-m2-repo</id>
       <username>admin</username>
       <password>admin</password>
       <configuration>
         <wagonProvider>httpclient</wagonProvider>
         <httpConfiguration>
           <all>
             <usePreemptive>true</usePreemptive>
           </all>
         </httpConfiguration>
       </configuration>
     </server>
     
     <!-- Alternative to enabling pre-emptive authentication - configuring 
          the Authorization HTTP header with Base64-encoded credentials
     <server>
       <id>brms-bpms-m2-repo</id>
       <configuration>
         <httpHeaders>
           <property>
             <name>Authorization</name>
             <value>Basic YWRtaW46YWRtaW4=</value>
           </property>
         </httpHeaders>
       </configuration>
     </server>
     -->
   
     <activeProfiles>
       <!-- Activation of the BRMS/BPMS profile -->
       <activeProfile>brms-bpms-online-profile</activeProfile>
     </activeProfiles>
   
   </settings>

   Copy to Clipboard Toggle word wrap
2. If you modified the settings.xml file while JBoss Developer Studio was running, you must refresh Maven settings in the IDE. From the menu, choose Window → Preferences. In the Preferences Window, expand Maven and choose User Settings. Click the Update Settings button to refresh the Maven user settings in JBoss Developer Studio.
   

   View larger image

   

   Figure 7.2. Update Maven User Settings

Procedure 8.1. Install the Drools and jBPM JBoss Developer Studio Plug-in

1. Start JBoss Developer Studio.
2. Select Help → Install New Software.
3. Click Add to enter the Add Repository menu.
4. Give the software site a name next to Name field and add the following url in the Location field: https://devstudio.jboss.com/updates/8.0/integration-stack/
5. Click OK.
6. Select the JBoss Business Process and Rule Development feature from the available options and click Next and then Next again.
7. Read the license and accept it by selecting the appropriate radio button, and click Finish.
8. After installation of the plug-ins has completed, restart JBoss Developer Studio.

Procedure 8.2. Configure JBoss BRMS Runtime

1. Extract the runtime jar files located in the jboss-brms-VERSION-engine.zip archive that you can download from Red Hat Customer Portal.
2. From the JBoss Developer Studio menu, select Window and click Preferences.
3. Select Drools → Installed Drools Runtimes.
4. Click Add...; provide a name for the new runtime, and click Browse to navigate to the directory where you extracted the runtime files in step 1. Click OK to register the selected runtime in JBDS.
5. Mark the runtime you have created as the default Drools runtime by clicking on the check box next to it.
6. Click OK. If you have existing projects, a dialog box will indicate that you have to restart JBoss Developer Studio to update the Runtime.

Procedure 8.3. Configure the Server

1. Open the jBPM view by selecting Window → Open Perspective → Other and select jBPM and click OK.
2. Add the server view by selecting Window → Show View → Other... and select Server → Servers.
3. Open the server menu by right clicking the Servers panel and select New → Server.
4. Define the server by selecting JBoss Enterprise Middleware → JBoss Enterprise Application Platform 6.4+ and clicking Next.
5. Set the home directory by clicking the Browse button. Navigate to and select the installation directory for JBoss EAP 6.4 which has JBoss BPM Suite installed.
6. Provide a name for the server in the Name field, make sure that the configuration file is set, and click Finish.

Procedure 8.4. Cloning a Remote Git Repository

1. Start the Red Hat JBoss BRMS/BPM Suite server (whichever is applicable) by selecting the server from the server tab and click the start icon.
2. Simultaneously, start the Secure Shell server, if not running already, by using the following command. The command is Linux and Mac specific only. On these platforms, if sshd has already been started, this command fails. In that case, you may safely ignore this step.

   /sbin/service sshd start

   Copy to Clipboard Toggle word wrap
3. In JBoss Developer Studio, select File → Import... and navigate to the Git folder. Open the Git folder to select Projects from Git and click Next.
4. Select the repository source as Clone URI and click Next.
5. Enter the details of the Git repository in the next window and click Next.

   

   View larger image

   

   Figure 8.1. Git Repository Details

6. Select the branch you wish to import in the following window and click Next.
7. To define the local storage for this project, enter (or select) a non-empty directory, make any configuration changes and click Next.
8. Import the project as a general project in the following window and click Next. Name the project and click Finish.

Procedure 8.5. Importing a Local Git Repository

1. Start the Red Hat JBoss BRMS/BPM Suite server (whichever is applicable) by selecting the server from the server tab and click the start icon.
2. In JBoss Developer Studio, select File → Import... and navigate to the Git folder. Open the Git folder to select Projects from Git and click Next.
3. Select the repository source as Existing local repository and click Next.
   

   View larger image

   

   Figure 8.2. Git Repository Details

4. Select the repository that is to be configured from the list of available repositories and click Next.
5. In the dialog that opens, select the radio button Import as general project from the Wizard for project import group and click Next. Name the project and click Finish.

   

   View larger image

   

   Figure 8.3. Wizard for Project Import