Procedure 5.1. Launch CLI in Linux or Microsoft Windows Server

• • Launch the CLI in Linux

    Run the EAP_HOME/bin/jboss-cli.sh file by entering the following at a command line:

    $ EAP_HOME/bin/jboss-cli.sh

  • Launch the CLI in Microsoft Windows Server

    Run the EAP_HOME\bin\jboss-cli.bat file by double-clicking it, or by entering the following at a command line:

    C:\>EAP_HOME\bin\jboss-cli.bat

Procedure 5.2. Connect to a Managed Server Instance

• Run the connect command

  From the Management CLI, enter the connect command:

  [disconnected /] connect
  Connected to domain controller at localhost:9999

  • Alternatively, to connect to a managed server when starting the Management CLI on a Linux system, use the --connect parameter:

    $ EAP_HOME/bin/jboss-cli.sh --connect

  • The --connect parameter can be used to specify the host and port of the server. To connect to the address 192.168.0.1 with the port value 9999 the following would apply:

    $ EAP_HOME/bin/jboss-cli.sh --connect --controller=192.168.0.1:9999

Procedure 5.3. Deploy an Application in a Standalone Server

• Run the deploy command

  From the Management CLI, enter the deploy command with the path to the application deployment.

  [standalone@localhost:9999 /] deploy /path/to/test-application.war

  Note that a successful deploy does not produce any output to the CLI.

Procedure 5.4. Undeploy an Application in a Standalone Server

• Run the undeploy command

  To undeploy the application and delete the deployment content, enter the Management CLI undeploy command with the filename of the application deployment.

  [standalone@localhost:9999 /] undeploy test-application.war

  To undeploy the application, but retain the deployment content, enter the Management CLI undeploy command with the filename of the application deployment and the parameter --keep-content.

  [standalone@localhost:9999 /] undeploy test-application.war --keep-content

Procedure 6.1. 

1. Ensure that JBoss Operations Network and the JBoss Fuse Service Works instance of JBoss EAP are running. Log in to the JBoss Operations Network server GUI.
2. Click on the Inventory button at the top of the page.
3. Select Servers from the menu on the left hand side. Select SOA-P server from the list presented on the Servers page.
4. Select the Inventory tab on the SOA-P page, then click Connection Settings.
5. Update the User and Passwords fields on the General Properties section with an administrator User ID and Password for the JBoss Fuse Service Works JBoss EAP instance.

Procedure 7.1. task

1. Launch a web browser and navigate to http://localhost:8080/bpel-console.
2. Enter your user name and password.
3. Click on the Runtime tab.
4. Select the Deployments option. You will now be able to see the version information and current status (active or retired) of each process definition.
5. Check if there is any active process consisting of any unfinished instances, retire the process.
6. Undeploy the process only when there is no active process instance.

Procedure 7.2. task

1. Launch a web browser and navigate to http://localhost:8080/bpel-console.
2. Enter your user name and password.
3. Click on the Managed Instances tab to see which BPEL processes are currently deployed. The process version information for each of these processes is also visible.
4. Only one version of a process can be active at a time. When you open a process definition, the active version is automatically selected.

Procedure 7.3. task

1. Launch a web browser and navigate to http://localhost:8080/bpel-console.
2. Enter your user name and password.
3. Click on the Managed Instances tab to see which BPEL processes are currently deployed. The process version information for each of these processes is also visible.
4. Select a process definition to open it.
5. Use the Execution History to produce a chart. Here you can specify a particular period of time to review and choose whether or not to include failed and terminated instances in the chart.

Procedure 7.4. task

1. Open the deploy.xml file in a text editor.

   Note

   deploy.xml file exists with every BPEL deployment unit.
2. Configure the deploy.xml file as follows:

   <deploy xmlns="schemas"
       xmlns:bpl="examples"
         xmlns:intf="examples/wsdl">
           <process name="bpl:HelloGoodbye">
              <active>true</active>
              <process-events generate="all"/>
              <provide partnerLink="helloGoodbyePartnerLink">
              <service name="intf:HelloGoodbyeService" port="HelloGoodbyePort"/> 
              </provide>
           </process>
   </deploy>

   Note

   Add the process-events element to generate all the events. For more information, navigate to the Apache ODE events http://ode.apache.org/ode-execution-events link.
3. Save the file and exit.

Procedure 7.5. task

1. Launch a web browser and navigate to http://localhost:8080/bpel-console.
2. Enter your user name and password.
3. Under the Managed Instances tab, select the Open Button list to view the deployed process definitions. When you select any one of the process, it displays the list of process definitions and version of that particular process.
4. Select a process instance to open it. You can see its details in the Execution Details panel.
5. Click the Instance Data button. It displays all the details about the process.
6. Click the Execution Path button. It opens the related instance execution graph.

   Note

   The instance execution graph is a visual representation of a running instance of a process. It tells the user about the process instance's performance over time.
7. The View tab shows the instance execution graph, while the Source tab below it shows all of the "activity" events.

Procedure 7.6. Task

1. Log into the BPEL Web Console.
2. Choose a process definition and a process status from the list box.
   You can also optionally choose to input the correlation key, the start time and the end time as search criteria.
3. Go to the History Instances List and double-click on a row. A window will pop up showing you all of the execution events that happened when that process ran.

Procedure 7.7. Task

1. Launch a web browser and go to http://localhost:8080/bpel-console.
2. Input your user name and password.
3. Click on the Runtime tab.
4. Select the Deployments option.
   You will now be able to see the version information and current status (active or retired) of each process definition.
5. Select the particular version of the process definition you want to retire and then press the Retire button.

   Note

   If you undeploy a process, its end-points will only deactivate if no previous versions of that process have ever existed.

Procedure 7.8. task

1. Open the deploy.xml file in a text editor.
2. Add <process-events generate="all"/> parameter in the deploy.xml file.

Procedure 8.1. Task

1. Start the server.
2. Access the following URL:

   http://localhost:8080/gadget-web

3. Enter a username and specify a password. A default user is provided called fswAdmin.
4. When the Overlord Runtime Governance UI is displayed the first time, you must enter a new page by pressing the + button.
5. To browse gadgets, click on the Gadget Store button.

Procedure 9.1. Task

1. Start the server.
2. Access the following URL:

   http://localhost:8080/dtgov-ui

3. Enter your credentials and log in. The Dashboard will be displayed.
   

Procedure 11.1. Task

1. To view the Overlord Run-Time Governance properties, access the properties file located in $JBOSS_HOME/standalone/configuration/overlord-rtgov.properties.
2. Add and modify classes to manage governance.

1. Navigate to jboss-eap-6.1/dtgov-data and create a local settings.xml containing the user credentials for the S-RAMP repository. This file must also contain the Overlord admin password that you configured during installation. Here is an example:

   <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">
     <servers>
       <server>
         <id>local-sramp-repo</id>
         <username>admin</username>
         <password>cust0mpwd</password>
       </server>
       <server>
         <id>local-sramp-repo-snapshots</id>
         <username>admin</username>
         <password>cust0mpwd</password>
       </server>
     </servers>
   </settings>

2. Ensure that the server is up and running, and deploy the "SimpleReleaseProcess" sample workflow to the server by running the following command:

   mvn -s local-settings.xml deploy

Procedure 13.1. Create the Initial Administrative User for the Remote Management Interfaces

1. Invoke the add-user.sh or add-user.bat script.

   Change to the EAP_HOME/bin/ directory. Invoke the appropriate script for your operating system.

   Red Hat Enterprise Linux

   [user@host bin]$ ./add-user.sh

2. Choose to add a Management user.

   Hit ENTER to select the default option a to add a Management user. This user is added to the ManagementRealm and is authorized to perform management operations using the web-based Management Console or command-line based Management CLI. The other choice, b, adds a user to the ApplicationRealm, and provides no particular permissions. That realm is provided for use with applications.

3. Enter the desired username and password.

   When prompted, enter the username and password. You will be prompted to confirm the password.

4. Review the information and confirm.

   You are prompted to confirm the information. If you are satisfied, type yes.

5. Choose whether the user represents a remote JBoss EAP 6 server instance.

   Besides administrators, the other type of user which occasionally needs to be added to JBoss EAP 6 in the ManagementRealm is a user representing another instance of JBoss EAP 6, which must be able to authenticate to join a cluster as a member. The next prompt allows you to designate your added user for this purpose. If you select yes, you will be given a hashed secret value, representing the user's password, which would need to be added to a different configuration file. For the purposes of this task, answer no to this question.

6. Enter additional users.

   You can enter additional users if desired by repeating the procedure. You can also add them at any time on a running system. Instead of choosing the default security realm, you can add users to other realms to fine-tune their authorizations.

7. Create users non-interactively.

   You can create users non-interactively, by passing in each parameter at the command line. This approach is not recommended on shared systems, because the passwords will be visible in log and history files. The syntax for the command, using the management realm, is:

   [user@host bin]$ ./add-user.sh username password

   To use the application realm, use the -a parameter.

   [user@host bin]$ ./add-user.sh -a username password

8. You can suppress the normal output of the add-user script by passing the --silent parameter. This applies only if the minimum parameters username and password have been specified. Error messages will still be shown.

Procedure 13.2. Alternative Properties Files

• • To specify an alternative directory for the server configuration, use the -sc argument. This argument specifies an alternative directory that will contain the server configuration properties files.
  • To specify an alternative directory for the domain configuration, use the -dc argument. This argument specifies an alternative directory that will contain the domain configuration properties files.
  • To specify an alternative user configuration properties file, use the -up or --user-properties argument. It can an absolute path or it can be a file name used in conjunction with the -sc or -dc argument that specifies the alternative configuration directory.
  • To specify an alternative group configuration properties file, use the -gp or --group-properties argument. It can an absolute path or it can be a file name used in conjunction with the -sc or -dc argument that specifies the alternative configuration directory.

Procedure 14.1. Setup the Service

1. Locate the start-up script and configuration file

   The start-up script and an associated configuration file are located in the EAP_HOME/bin/init.d/ directory. Open the configuration file jboss-as.conf to edit it.

2. Customize the start-up options in the jboss-as.conf file

   There are several options within the jboss-as.conf file. At the minimum, specify the correct values for JBOSS_HOME and the JBOSS_USER variables. If these variables are absent, add them.

3. Copy files into system directories

   1. Copy the modified configuration file to the /etc/jboss-as directory.

      [user@host init.d]$ sudo mkdir /etc/jboss-as

      [user@host init.d]$ sudo cp jboss-as.conf /etc/jboss-as/

   2. Copy the start-up script to the /etc/init.d directory.

      [user@host init.d]$ sudo cp jboss-as-standalone.sh /etc/init.d

4. Add the start-up script as a service.

   Add the new jboss-as-standalone.sh service to list of automatically started services, using the chkconfig service management command.

   [user@host init.d]$ sudo chkconfig --add jboss-as-standalone.sh

5. Start the service.

   Test that the service has been installed correctly by using the standard syntax for starting Red Hat Enterprise Linux services.

   [user@host bin]$ sudo service jboss-as-standalone.sh start

   If everything has gone correctly, you should get a green [OK]. If you get an error, check the error logs and make sure your paths are correct in the configuration file.

6. Make the service start automatically when you restart your server.

   To add the service to the list of services which start automatically when your server restarts, issue the following command.

   [user@host init.d]$ sudo chkconfig jboss-as-standalone.sh on

Procedure 15.1. Configuring Governance and S-RAMP in a Clustered Environment

1. Add the <distributable/> entry inside the <web-app> element of the following web.xml files:

   • standalone/deployments/s-ramp-server.war/WEB-INF/web.xml
   • standalone/deployments/s-ramp-ui.war/WEB-INF/web.xml
   • standalone/deployments/dtgov.war/WEB-INF/web.xml
   • standalone/deployments/dtgov-ui.war/WEB-INF/web.xml
   • standalone/deployments/overlord-commons-idp.war/WEB-INF/web.xml
   • standalone/deployments/overlord-rtgov/gadget-web.war/WEB-INF/web.xml
   • standalone/deployments/overlord-rtgov/gadgets.war/WEB-INF/web.xml
   • standalone/deployments/overlord-rtgov/overlord-rtgov.war/WEB-INF/web.xml
2. Add the <replication-config> entry:

   <replication-config>
     <cache-name>web/sso</cache-name>
   </replication-config>

   inside the <jboss-web> element of the following jboss-web.xml files:

   • standalone/deployments/s-ramp-server.war/WEB-INF/jboss-web.xml
   • standalone/deployments/s-ramp-ui.war/WEB-INF/jboss-web.xml
   • standalone/deployments/dtgov.war/WEB-INF/jboss-web.xml
   • standalone/deployments/dtgov-ui.war/WEB-INF/jboss-web.xml
   • standalone/deployments/overlord-commons-idp.war/WEB-INF/jboss-web.xml
   • standalone/deployments/overlord-rtgov/gadget-web.war/WEB-INF/jboss-web.xml
   • standalone/deployments/overlord-rtgov/gadgets.war/WEB-INF/jboss-web.xml
   • standalone/deployments/overlord-rtgov/overlord-rtgov.war/WEB-INF/jboss-web.xml
3. Configure the ModeShape and Infinispan subsystems, and the jGroups TCP Stack in the standalone/configuration/standalone-ha.xml file as in the following code sample:

   <!-- Infinispan subsystem configuration -->
   
   <cache-container name="modeshape" module="org.modeshape"
     start="EAGER">
     <transport lock-timeout="60000" />
     <replicated-cache name="sramp" mode="SYNC" batching="true">
       <locking isolation="NONE" />
       <transaction mode="NON_XA" />
       <string-keyed-jdbc-store datasource="java:jboss/datasources/srampDS"
         passivation="false" purge="false">
         <string-keyed-table prefix="ispn_bucket">
           <id-column name="id" type="VARCHAR(500)" />
           <data-column name="datum" type="VARBINARY(60000)" />
           <timestamp-column name="version" type="BIGINT" />
         </string-keyed-table>
       </string-keyed-jdbc-store>
     </replicated-cache>
   </cache-container>
   <cache-container name="modeshape-binary-cache-container"
     aliases="modeshape-binary-cache" module="org.modeshape">
     <transport lock-timeout="60000" />
     <replicated-cache name="sramp-binary-fs" mode="SYNC"
       batching="true">
       <transaction mode="NON_XA" />
       <file-store relative-to="jboss.server.data.dir"
         path="modeshape/binary-store/sramp-binary-data-${jboss.node.name}"
         passivation="false" purge="false" />
     </replicated-cache>
   </cache-container>
   
   <!-- ModeShape subsystem configuration -->
   
   <subsystem xmlns="urn:jboss:domain:modeshape:1.0">
     <repository name="sramp" cache-name="sramp" cache-container="modeshape"
       security-domain="overlord-idp" anonymous-roles="readonly"
       cluster-name="sramp-cluster" cluster-stack="tcp">
       <indexing rebuild-upon-startup="if_missing" />
       <local-file-index-storage
         path="modeshape/clustered-repo/${jboss.node.name}_indexes" />
       <cache-binary-storage data-cache-name="binary-fs"
         metadata-cache-name="binary-fs-meta" cache-container="modeshape-binary-cache-container" />
     </repository>
   </subsystem>
   
   <!-- jgroups tcp stack configuration -->
   
   <subsystem xmlns="urn:jboss:domain:jgroups:1.1" default-stack="udp">
     ...
     <stack name="tcp">
     ...
       <protocol type="TCPPING">
         <property name="initial_hosts">0.0.0.0[7600],0.0.0.0[7600]</property>
         <property name="num_initial_members">2</property>
         <property name="port_range">0</property>
         <property name="timeout">2000</property>
       </protocol>
     </stack>
   </subsystem>

1. Stop JBoss EAP 6.

   Stop JBoss EAP 6 by sending an interrupt in the appropriate way for your operating system. If you are running JBoss EAP 6 as a foreground application, the typical way to do this is to press Ctrl+C.

2. Restart JBoss EAP 6, specifying the bind address.

   Use the -b command-line switch to start JBoss EAP 6 on a specific interface.

   Example 16.1. Specify the public interface.

   EAP_HOME/bin/domain.sh -b 10.1.1.1

   Example 16.2. Specify the management interface.

   EAP_HOME/bin/domain.sh -bmanagement=10.1.1.1

   Example 16.3. Specify different addresses for each interface.

   EAP_HOME/bin/domain.sh -bmanagement=127.0.0.1 -b 10.1.1.1

   Example 16.4. Bind the public interface to all network interfaces.

   EAP_HOME/bin/domain.sh -b 0.0.0.0