Configuring CA Harvest SCM for Mobile Package Approval

Configuring the CA Harvest SCM for mobile package approval webapp involves:

Configuring the notify process
Installing the CA Harvest SCM mobile webapp
- Installing the HarvestMobile Web Interface
- Preparing for the HarvestMobile Web Interface Installation
- Installing the HarvestMobile Web Interface (Windows)
- Installing the HarvestMobile Web Interface (Linux)

Configure Notify Process

The administrator configures the notify process to notify the change approver(s) about the pending approvals. This configuration can be customized as per your requirements as follows:

Standalone process
Pre-Link process
Post‑Link process

Example:

The following example is sample notify process configuration for mobile approval:

Mail Utility

hsmtp -m <mailserver>  -p <smtp portnumber> -f  <email from>

Mail Message

Please review and approve the following package in

Project:[project]

State:[state]

Package:[package]

Click on the following link:

[harvestwebserver]/<HarvestSCMMobile WebApp name>/?brokerName=[broker]&projectId=[project]&stateId=[state]&packageId=[package]

</PackageAccessUrl>

For more information about the system variables, see the Using the System Variables section.

Important! You must specify the URL only in the <PackageAccessUrl> tags. The project, state, and package variables that are enclosed in between the <PackageAccessUrl> and the </PackageAccessUrl> are replaced with the object IDs instead of object names.

The harvestwebserver system variable value is picked up from the Hserver.arg file.

Note: When a user selects package or packages or package group from Workbench to invoke the notify process configured as stated above, the output URL contains the respective package ID(s).

The output of the content enclosed between <PackageAccessUrl> tags displays as a URL in the mail message. If there are multiple packages to be approved, the URL contains the package IDs that are separated with comma.

Example:

http://anega01:8080/HarvestSCMMobile/?brokerName=anega01&projectId=15&stateId=63&packageId=1058,1037,1048

On clicking the URL, the user is navigated to the Harvest Mobile Webapp login screen. On successful login, the user gets to see the list of packages.

Installing the HarvestMobile Web Interface

Important! Installing the HarvestMobile Web Interface is one step in the overall implementation process.

How to Prepare for the HarvestMobile Web Interface Installation

If you have not already done so, read the Release Notes. Do not install the HarvestMobile Web Interface until you have read that information and understand it.

Note: You can find the Release Notes at http://ca.com/support.

Follow these steps:

Verify that the CA CA Harvest SCM client has been installed. For your convenience, the HarvestMobile Web Interface installation media includes the installation files for the product client on all supported platforms, including the product client.
Verify that a supported mobile browser is installed on all client computers that will access the HarvestMobile Web Interface.
Note: For information about supported mobile browsers, see the Release Notes.
Verify that a supported release of the Java SDK Standard Edition is installed on your web server.
Note: For information about supported releases of the Java SDK, see the Release Notes.
Set and test system variables on your web server.
Install, start, or stop your application server software.
Note: Stop the Web Application Server if it is Tomcat or Jboss. For information about supported application/web servers, see the Release Notes.

Install the HarvestMobile Web Interface (Windows)

Note: In the installation media, the \HarvestMobileSupport directory contains the installation files for the HarvestMobile Web Interface on all supported platforms. This process includes the installation of the web services also.

Follow these steps:

Insert the HarvestMobile Web Interface ISO image in the drive of your Windows computer.
Open a command prompt and change directories to the HarvestMobile Web Interface directory on the Web Interface installation media.
For example: cd DVD-drive:\HarvestMobileSupport
At the command prompt, enter the following command to start the HarvestMobile Web Interface installation:
```
install.bat
```
The console displays two packaging types.
Select one of the packaging options.

Package WAR files

This option lets you to package the WAR files. Go to Step 5.

Package and Deploy WAR files

This option lets you to package the WAR files and deploys the same. Go to Step 6.
If you have want to package your WAR files only, follow these steps:
1. Type 1.
2. Provide the temporary location, web server host name, web server port number when prompted.
  Enter temporary location [Example C:\Windows\Temp]:
```
c:\Sample\HarvestMobile\temp
```
  Enter host name of the webserver where Web applications need to be deployed:
```
anega01
```
  Note: Ensure to have the Web server host name same as the value provided in Harvest Web Server system variable.
  
  Enter port number on which webserver is running :
```
8080
```
3. Select one of the application configuration types–HTTP or HTTPS.
4. Type 1 for HTTP or 2 for HTTPS.
  The WAR files are packaged in the provided temporary location. You can use these files to deploy in the Application / Web Servers.
If you have want to package and deploy your WAR files, follow these steps:
1. Type 2.
2. Provide the temporary location, web server host name, web server port number when prompted.
  Enter temporary location [Example C:\Windows\Temp]:
```
c:\Sample\HarvestMobile\temp
```
  Enter host name of the webserver where Web applications need to be deployed:
```
anega01
```
  Note: Ensure to have the Web server host name same as the value provided in Harvest Web Server system variable.
  
  Enter port number on which webserver is running :
```
8080
```
3. Select one of the application configuration types–HTTP or HTTPS.
4. Type 1 for HTTP or 2 for HTTPS.
  The WAR files are packaged in the provided temporary location.
5. Select one of the listed server options:
  - Tomcat
  - JBoss
  - WebSphere
- If you have want to deploy your WAR files on Tomcat and JBoss, follow these steps:
  1. Type 1 for Tomcat or 2 for JBoss.
  2. Provide the deployment folder location when prompted.
    Enter deployment folder location
    
    [example C:\apache-tomcat-7.0.47\webapps]:
  Note: When you have Apache Tomcat webserver, provide the following deployment path:
```
CATALINA_HOME\webapps
```
  Note: When you have JBoss webserver, provide the following deployment path:
```
JBOSS_HOME\standalone\deployments
```
  The WAR files are deployed in the specified location for Tomcat and JBoss.
- If you have want to deploy your WAR files on Websphere, follow these steps:
  1. Type 3.
  2. Provide the WebSphere home location when prompted.
    Enter WebSphere home location:
    
    [C:\Program Files (x86)\IBM\WebSphere\AppServer]
    
    Enter WebSphere Node location:
    
    [C:\Program Files (x86)\IBM\WebSphere\AppServer\profiles\AppSrv01\installedApps\Node01Cell]

After you complete the installation procedure for your platform, the HarvestMobile Web Interface Installation performs the following tasks:

For Packing option only:

Creates a subdirectory named HARVEST in the temporary directory. This directory gets deleted automatically after successful deployment.
Creates or updates the harconfig.js to specify the HarvestRestService details.
Packages the HarvestSCMMobile.war file and HarvestSCMRestService.war files in the specified temporary location.

For Packing and Deployment option:

Creates a subdirectory named HARVEST in the temporary directory. This directory gets deleted automatically after successful deployment.
Creates or updates the harconfig.js to specify the HarvestRestService details.
Packages the HarvestSCMMobile.war file and HarvestSCMRestService.war files in the specified temporary location.
Automatically deploys the HarvestSCMMobile.war, HarvestSCMRestService.war files to your web server.

Install the HarvestMobile Web Interface (Linux)

Follow these steps:

Insert the HarvestMobile Web Interface installation media in the drive of your Linux machine.
Open a terminal and change directories to the HarvestMobile Web Interface directory on the Web Interface installation media.
For example: cd home/HarvestMobileSupport
Type the following command to start the HarvestMobile Web Interface:
```
./install.sh
```
Select one of the packaging options.

Package WAR files

This option lets you to package the WAR files. Go to Step 5.

Package and Deploy WAR files

This option lets you to package the WAR files and deploys the same. Go to Step 6.
If you have want to package your WAR files only, follow these steps:
1. Type 1.
2. Provide the temporary location, web server host name, web server port number when prompted.
  Enter temporary location [Example /home/harvest/temp]:
```
/home/anega01/temp
```
  Enter host name of the webserver where Web applications need to be deployed:
```
anega01
```
  Note: Ensure to have the Web server host name same as the value provided in Harvest Web Server system variable.
  
  Enter port number on which webserver is running :
```
8080
```
3. Select one of the application configuration types–HTTP or HTTPS.
4. Type 1 for HTTP or 2 for HTTPS.
  The WAR files are packaged in the provided temporary location. You can use these files to deploy in the Application / Web Servers.
If you have want to package and deploy your WAR files, follow these steps:
1. Type 2.
2. Provide the temporary location, web server host name, web server port number when prompted.
  Enter temporary location [Example /home/harvest/temp]:
```
/home/anega01/temp
```
  Enter host name of the webserver where Web applications need to be deployed:
```
anega01
```
  Note: Ensure to have the Web server host name same as the value provided in Harvest Web Server system variable.
  
  Enter port number on which webserver is running :
```
8080
```
3. Select one of the application configuration types–HTTP or HTTPS.
4. Type 1 for HTTP or 2 for HTTPS.
  The WAR files are packaged in the provided temporary location.
5. Select one of the listed server options:
  - Tomcat
  - JBoss
  - WebSphere
- If you have want to deploy your WAR files on Tomcat and JBoss, follow these steps:
  1. Type 1 for Tomcat or 2 for JBoss.
  2. Provide the deployment folder location when prompted.
    Enter deployment folder location
    
    [example /home/apache-tomcat/webapps]:
  Note: When you have Apache Tomcat webserver, provide the following deployment path:
```
CATALINA_HOME/webapps
```
  Note: When you have JBoss webserver, provide the following deployment path:
```
JBOSS_HOME/standalone/deployments
```
  The WAR files are deployed in the specified location for Tomcat and JBoss.
- If you have want to deploy your WAR files on Websphere, follow these steps:
  1. Type 3.
  2. Provide the WebSphere home location when prompted.
    Enter WebSphere home location:
    
    [example /opt/IBM/WebSphere/AppServer]
    
    Enter WebSphere Node location:
    
    [example /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/installedApps/Node01Cell]

After you complete the installation procedure for your platform, the HarvestMobile Web Interface Installation performs the following tasks:

For Packing option only:

Creates a subdirectory named HARVEST in the temporary directory. This directory gets deleted automatically after successful deployment.
Creates or updates the harconfig.js to specify the HarvestRestService details.
Packages the HarvestSCMMobile.war file and HarvestSCMRestService.war files in the specified temporary location.

For Packing and Deployment option:

Creates a subdirectory named HARVEST in the temporary directory. This directory gets deleted automatically after successful deployment.
Creates or updates the harconfig.js to specify the HarvestRestService details.
Packages the HarvestSCMMobile.war file and HarvestSCMRestService.war files in the specified temporary location.
Automatically deploys the HarvestSCMMobile.war, HarvestSCMRestService.war files to your web server.

Deploy Harweb and HarvestRestService in a Workstation

Since both Harweb and HarvestRestService depend on loading of harvest native binaries, you cannot have both of the Web applications run in a single JVM process.

Configure Harweb and HarvestRestService in Two Application / Web Servers

Deploy Harweb and HarvestRestService on two different servers.

Configure Harweb and HarvestRestService in a Single Application / Web Server

You can configure multiple instances of the respective servers and can run Harweb on one instance and HarvestRestService on another. Configuring this way avoids the problem.

The following servers are supported for the HarvestRestService services deployment:

Apache Tomcat
JBoss
WebSphere Application Server

Note: For more information about configuring multiple instances, see the Apache Tomcat, JBoss, and WebSphere sites.

The following examples provide information on configuring multiple instances on respective servers.

Apache Tomcat

When you run Tomcat, it uses the following two environment variables, which can be configured for multiple instances:

CATALINA_HOME
CATALINA_BASE

CATALINA_HOME: Specifies the environment variable and must point to the Tomcat base folder, where tomcat binaries are installed/extracted. This defines the CATALINA_HOME bin and lib folder.
CATALINA_BASE: Specifies the environment variable. If you do not specify any value, then the CATALINA_HOME value is set to this variable. This variable points to the configuration and webapps folder. Based on this variable, server uses conf, logs, temp, webapps, and work folders.

To run multiple Tomcat instances in a single machine:

Change the CATALINA_BASE value before starting /shutting down of Tomcat.
Create a folder that is named “tomcat-instance1” and copy conf, logs, temp, webapps, work folder from CATALINA_HOME folder.
Change the conf/server.xml file in tomcat-instance1.
Change the following ports:
- Shutdown port
- Connector port
- Ajp port
- Redirect port

JBoss

You can set up multiple instances of JBoss server on a single local machine.

You can set the Port offset on runtime by the directive jboss.socket.binding.port-offset. The jboss.server.base.dir directive is also used to set the custom base folder.

Follow these steps:

Install JBoss EAP 6
1. Create a folder that is named dev on your home directory. (e.g. /home/grg021/dev )
2. Unzip your JBoss EAP 6 installer on this folder.
3. Make the following changes:
  - root_folder = /home/grg021/dev/
  - eap_home = root_folder/jboss-eap-6.0/
Set up the following Standalone Server Instances
- instance_1 – root_folder/ins1
- instance_2 – root_folder/ins2
1. Copy the standalone folder and its contents in instance_1 and instance_2
Run
1. Open a 2 terminal instances on the bin directory of eap_home. (term_1 andterm_2)
2. On term_1 – run standalone server on instance_1
  - [grg021@localhost ~]$ cd dev/jboss-eap-6.0/bin
  - [grg021@localhost bin]$ ./standalone.sh -Djboss.server.base.dir=/home/grg021/dev/ins1/standalone/
3. On term_2 – run standalone server on instance_2 with port offset 10000
  [grg021@localhost bin]$ ./standalone.sh -Djboss.server.base.dir=/home/grg021/dev/ins2/standalone/ -Djboss.socket.binding.port-offset=10000

WebSphere Application Server

Deploy Harweb and HarvestRestService on two different application server profiles of WebSphere.

Note: For more information about the application server profile creation, see the WebSphere documentation.