UPSTREAM Installation
The UPSTREAM Installation Process
The UPSTREAM installation wizard guides the user through the process of installing the UPSTREAMClient and its optional features. Using the wizard, the install can be performed on a local computer or the command line (silent mode) feature can be used to push-install to a remote computer using third party products or services. Additionally, the UPSTREAMDirector can be installed; the Director lets you manage and administer the UPSTREAMclients from a remote server or workstation.
After the UPSTREAMClient is installed, additional features and options can be installed or removed by a simple rerun of the install wizard.
Installation from a command line, also known as silent mode installation, is also available. The silent mode installation uses the windows installer.exe program for windows or platform specific installer.run file for other supported platforms such as x86 Linux, Linux OS on IBMZ, and other supported UNIX platforms.
The UPSTREAMClient installation wizard may install the following additional products during the process:
- Microsoft .NET 4
- Microsoft Visual C++ Redistributable package
UPSTREAM Client Pre-installation and Considerations
Check the security settings to make sure the account used for installation has proper administrator authority.
Windows Security Requirement
For Windows, the installation must run under a local administrator or Domain Administrator account.
UNIX and Linux Security Requirement
In order to access all files on all volumes and disks, the UPSTREAM Client requires “root” access. The UPSTREAM Client installation must be performed as “root”’. Following the install, the UPSTREAM Client daemon runs as “root”.
Alternate Security Requirements
There are exceptions where the UPSTREAM Client must use an alternate ID to properly process network file systems or databases.
This can be accomplished by defining a secondary task or daemon.
Network Connectivity
- An installed network must support TCP/IP (IP v4).
- Editing of required port numbers can be done during the UPSTREAM Client installation or later using the provided configurator.
- By default, the UPSTREAM Client starts an “inbound” listening port of 1972. That port, by default, is bound to any (or all) adapters present on the client’s host.
- By default, the UPSTREAM Client uses “status” ports for communication with other UPSTREAM components. Those ports (there is a pair of each) start listening at port 2033. As new Client “child” processes start, a new port pair is used. These port pairs must be opened through the firewall to allow communication with both the UPSTREAM Director and optionally, the UPSTREAM Web Portal.
Multiple Installations
It is no longer supported having more that one UPSTREAM installation per computer.
For best practices refer to Configuration and Settings for instructions on how to configure the system to run with multiple Windows Services or Client daemon services and how to convert from multiple installations over to a single install image.
UPSTREAM Client System Requirements
The following are the minimum requirements to run the UPSTREAM Client:
Operating System
- Windows 2008 R2 and above
- AIX 7.1
- SPARC Solaris 10 or above
- Intel Solaris 10 or above
- Red Hat Linux 6 or above, SuSE v11 SP4 or above, Centos 6 or above, Ubuntu 14.04 and 16.04 LTS,, VMware 5.x or above, and a number of other distributions for Intel x86 systems
- z/OS UNIX Systems Services z⁄OS v1.5 or above
- RedHat and SuSE for Linux OS on IBMZ
Disk and Volume Requirements
Disk and File System Requirements:
- 50 MB for originally installed binaries and 100MB of additional disk space for data files (configuration files and parameter files), output files (log and report files) and temporary work files (used during backup and restore). More may be required if you are backing up a lot of files. Those types of files are typically kept in the installation data path.
- The native file system types are supported (ext2, ext3, ext4, btrfs for Linux, JFS for AIX, and so on) as well as NFS or CIFS (when requested). File systems not included in the list below typically should be certified for use by UPSTREAM but they are included in backups (and a message logged).
As of this version of UPSTREAM, the Client supports the following native file systems:
– Linux – ext2, ext3, ext4, Reiser, btrfs, XFS, JFS, GFS, VxFS (Veritas file system), MapFS (Levanta), PVFS, GPFS, DevFS, NSS, OCFS2, CIFS (when you specify NFS)
– AIX – JFS, JFS2, GPFS, AFS (use the environment variable USAIXUSERFS to specify the magic number, in hex, of a file system to support)
– Solaris – UFS, VxFS (Veritas file system), SAMFS, ZFS, LOFS (as described above)
– z/OS UNIX(USS) – HFS, ZFS
– Windows – FAT32, FAT, EXFAT, NTFS, ReFS
UPSTREAM Client Software Distribution
Distribution of the UPSTREAM Client software is accomplished using an electronic distribution provided by BMC.
The distribution is provided as a zip file.
- UNIX-Client-4.1.nn.zip
For example: UNIX-Client-v4.1.00.nnnn.zip
Contains installers for each of the primary platforms:
– AIX – Use for all AIX implementations
– SOLARIS – Use for all SPARC Solaris implementations
– SOLX86 – Use for all Intel Solaris implementation
- Linux-Client-4.1.nn.zip
For example: Linux-Client-v4.1.nn.nnnn.zip
– Contains the installers for x86 Linux. For Example:
– client-4.1.nn.nnnn-linux-installer.run
– client-4.1.nn.nnnn-linux-x64-installer.run
- Linux on Z Client: s390_linux-4.1.nn.nnnn.zip
Contains subdirectories for the Linux OS on IBMZ platforms. Example:
– s390_linux-4.1.nn.nnnn-linux-s390x-installer.run
Use for all 64-bit Linux OS on IBMZ implementations.
- windows-4.1.nn.nnnn.zip
Contains windows installer.
Installing UPSTREAM Clients with the Installation Wizard
Installing an UPSTREAM Windows Client Using the Installation Wizard
Follow these steps to install a typical UPSTREAM Client.
From the installation media or location, double click on the provided Windows Client installer.exe file.
Welcome Panel
On the Welcome panel, read the license agreement, and then select “I accept the agreement”.
License Agreement
Click Next.
On the Select Components panel, select “UPSTREAM Client” (the default), and then click Next.
Select Components
Administrative tools contains the client configuration GUI, and the legacy UPSTREAM local interface.
Disaster Recovery Manager
The UPSTREAM Windows Disaster Recovery Manager component installs the services required to create a boot-able bare metal Disaster Recovery DVD ISO. See Disaster Recovery for further details.
Configuration
The next step in the install is to configure the UPSTREAM Client. For the most part, that configuration can use the defaults.
Client Configuration
After selecting the UPSTREAM components to install, you must accept or change the Install Path or Data Path.
The Data path is also used to store .dat files, log files, and configuration files.
Click Next.
However, there are two key pieces of configuration information that the UPSTREAM Client needs:
- The UPSTREAM Storage Server IP Host Name or IP Address
- The UPSTREAM Storage Server “listening” port number (most users use the default of 1972).
Client Configuration #2
The screen where the client configuration parameters are defined such as client port, and the address of the UPSTREAM Storage server, WebPortal and port to communicate over is defined and stored here.
Click Next when the installation is complete.
The UPSTREAM Windows Client is now installed and running.
Installing an UPSTREAM UNIX/Linux Client Using the Installation Wizard
Follow these steps to install a typical UPSTREAM client on Unix or Linux platforms.
From the installation media or location double click on the provided Client installer.run file.
Client Setup
On the Welcome panel, read the license agreement, and then click “I accept the agreement”.
License Agreement
Click Next.
On the Select Components panel, select “UPSTREAM Client” (the default), and click Next.
Select Components
Configuration
The next step in the install is to configure the UPSTREAM Client. Then, the next step is to define the Install path and Data Path.
Client Configuration
Click Next.
For the most part, that configuration can use the defaults. However, there are two key pieces of configuration information that the UPSTREAM Client needs:
- 28_List1_Bullet_1235979 • The UPSTREAM Storage Server IP Host Name or IP Address
- 28_List1_Bullet_1121120 • The UPSTREAM Storage Server “listening” port number (most users use the default of 1972).
Client Configuration
Click Finish when installation is complete.
The UPSTREAM Client is now installed and Running.
Install UPSTREAM Using the Command Line (Silent Install)
As an alternate method, installing UPSTREAM using the command line can be automated or interactive. This mode of installation is most frequently used on Non Windows platforms, but it is supported on Core Windows installations as well.
UNIX/Linux Command Line Install
From the attached installation media or download location invoke the appropriate .run file.
Invoke .run File
Read the License Agreement and accept the terms before continuing.
License Agreement
Select the components you want to install.
Select Components
Verify that the selection of components is valid.
Verify that the Install Path is correct; if not provide an alternate install path. Enter the IP address of the UPSTREAM Storage Server and optionally override the port numbers allocated for the UPSTREAM Storage Server and Client communication.
Verify Install Path, IP Address, and Port Number
Enter “Y” to continue the installation.
Continue Installation Prompt
Enter “Y” to continue the installation.
The UPSTREAM Daemon is now installed and running.
Windows Command Line Install
From the attached installation media or download location invoke the appropriate .exe installation member in a Windows Command prompt with administrator authority.
Invoke .exe Installation Member
This activates the standard Windows Install Wizard and allows the administrator to proceed with the Windows Installation as described previously.
Command Line Switches for Silent Mode Installation
The command line switches used for silent mode installation of the UPSTREAM Client on all platforms are as follows:
--help
Display the list of valid options.
--version
Display product information.
--unattendedmodeui <unattendedmodeui>
Unattended Mode UI
Default: none
Allowed: none, minimal, minimalWithDialogs
--optionfile <optionfile>
Installation option file.
Default:
--debuglevel <debuglevel>
Debug information level of verbosity.
Default: 2
Allowed: 0, 1, 2, 3, 4
--mode <mode>
Installation mode.
Default: win32
Allowed: win32, unattended
--debugtrace <debugtrace>
Debug filename.
Default:
--enable-components <enable-components>
Comma-separated list of components.
Default: usClient
Allowed: usClient, vmwareMgr, usbmr, win_cluster
--disable-components <disable-components>
Comma-separated list of components.
Default: vmwareMgr,usbmr,win_cluster
Allowed: usClient, vmwareMgr, usbmr, win_cluster
--installer-language <installer-language>
Language selection.
Default: en
Allowed: en, ar, bg, ca, da, nl, et, fr, fi, de, el, es, es_AR, he, hr, hu, it, ja, lt, ko, pl, pt_BR, pt, ro, ru, no, sl, sk, sq, sv, sr, tr, zh_TW, zh_CN, va, cy, cs, th
--installdir_client <installdir_client>
The directory where the component is to be installed.
Default:
--host_ip <host_ip>
Storage Server (Host) IP address.
Default: 111.111.111.111
--host_port <host_port>
Storage Server (Host) port.
Default: 1972
--client_port <client_port>
UPSTREAM Client port.
Default: 1972
--dirm_user <dirm_user>
Rescuer: dirmaint user name (optional)
Default:
--win_firewall_exception <win_firewall_exception>
Allow Windows Firewall Exception.
Default: 1
The Installation Log#
The install process creates an installation log file named install.log. This log file provides details about the installation. A failed install creates a file called bitrock_installer.log into the system temp directory.
The install.log file defaults to one of the following locations:
- Unix or Linux Platforms:
or
- Windows Platforms:
Upgrading from Previous Versions of UPSTREAM Client
The UPSTREAM Client install process can be used to upgrade from most current installations.
One recommended method is to deploy the client upgrade using the provided UPSTREAM Web Portal Interface.
Some exceptions to this requiring an initial manual upgrade/installation process include systems having separate installs of different versions of UPSTREAM Client on the same computer.
In the case where advanced configuration is required, such as having multiple individual services tasks and demons running, its recommended to follow the steps documented elsewhere in this manual.
Uninstall UPSTREAM Client
Windows Uninstall
Use Microsoft’s Add or Remove Programs options to remove the UPSTREAM Client from a computer. Uninstalling the UPSTREAM Client from a Windows Cluster automatically removes the product from all connected Windows Nodes.
For additional information on add or Remove Programs, refer to your Microsoft documentation.
UNIX/Linux Uninstall
Locate the directory where UPSTREAM was installed into and switch to the Uninstall directory at that location. This is typically located at:
or
Invoke the “Uninstall Upstream” executable at that location.
Install / Uninstall
Select the type of uninstall that is required and press Next.
Windows Uninstall
Verify that an uninstall is wanted and proceed.
The UPSTREAM Client is now uninstalled.
Uninstalling UPSTREAM Client Using the Command Line
Windows Uninstall
From a command prompt with administrative authority switch to the UPSTREAM installation directory.
Select the uninstall sub directory. This is typically located at:
Invoke the uninstall process with UninstallUpstream.exe.
The uninstall process begins and the administrator is prompted using the same dialog as the standard non command line uninstaller.
UNIX / Linux Uninstall
Switch to the location of the UPSTREAM uninstall directory. This is typically located at:
Invoke the uninstall process:
UNIX / Linux Uninstall
Verify this is a final uninstall.
The UPSTREAM Client is now uninstalled.
Installing UPSTREAM Director Interface
Follow these steps to install a typical UPSTREAM Director Interface
Windows Install
From the installation media or location, double click on the provided UPSTREAM Director installer.exe file.
Install UPSTREAM Director
License Agreement
Click Next.
The UPSTREAM Director interface is now installed.
Director Configuration
Ready to Install
Installing
Install Completed
Linux Install
The UPSTREAM Director for Linux is installed and configured in a similar manner as Windows.
Installing Web Portal on z/OS UNIX Systems Services
Overview
The UPSTREAM Web Portal provides Data Protection Storage administrators and more technically savvy end users a web hosted environment to manage elements of the backup process and also perform restore operations.
The traditional approach to backups in UPSTREAM focuses on the concept of Backup Profiles and the data stored in backup versions stored under those profiles. Traditional security is based on these same profiles controlling the data a specific user can access and restore, etc. With the introduction of the UPSTREAM Web Portal, an alternative model is introduced that focuses on Client Systems (workstation/server). The rules determining what an end user can perform is controlled in the Web Portal as well.
The Web Portal, using an application server and external database, provides a single web hosted environment that has the ability to monitor, control, and perform UPSTREAM actions against multiple storage servers. The UPSTREAM Web Portal operates as a web application, deployed as a z⁄OS started task. It provides the following major features:
- UPSTREAM Client upgrades
- Client Configuration
- Reporting
- File Level Restores
Product Download
- Create a directory in your z⁄OS UNIX file system. The following is an example using the TSO OMVS command:
TSO OMVS
mkdir /usr/lpp/fdrupstreamweb - For the install, sign in to the BMC Support Center and download the installation package. Once downloaded, FTP this file onto your OMVS system.
- Unpack the newly downloaded file to your dedicated install library (still in OMVS mode):
tar -xvoSf /path/to/fdrupstreamweb.tar -C /usr/lpp/fdrupstreamweb/
The UPSTREAM Web Portal supports deployment to existing Web Servers such as IBM WebSphere and/or Apache Tomcat.
After the product has been installed using the above, a few directories are created that contain files needed for deployment.
- /usr/lpp/fdrupstreamweb/deployable/ - contains the files “fdrupstreamweb.ear” and “fdrupstreamweb.war” required for the Tomcat and/or WebSphere administrator to install and deploy the Web Portal.
- /usr/lpp/fdrupstreamweb/conf - contains the “wpProfile.properties” files required to deploy the internal Derby database. If an external Derby Database is required, this file should be edited per the instructions in that file.
Product Configuration
The UPSTREAM Web Portal supports deployment to existing Web Servers such as IBM WebSphere and/or Apache Tomcat. Chose one of the following web portal installation platforms:
- Existing customer supplied IBM WebSphere Server (<red>Section)
- Existing customer supplied Apache Tomcat Server (<red>Section)
- Using the Apache Tomcat Server shipped with the UPSTREAM Web Portal (<red>Section)
Using the Apache Tomcat Server Shipped with the UPSTREAM Web Portal
- Define a CAACF2, IBMRACF, or CATopSecret userid/acid with an OMVS segment. Specify the following OMVS attributes for it. You may need to customize for your shop or security system:
OMVS INFORMATION
----------------
UID=0000000000
HOME=/usr/lpp/fdrupstreamweb
PROGRAM=/bin/sh
CPUTIMEMAX=NONE
ASSIZEMAX=NONE
FILEPROCMAX=NONE
PROCUSERMAX=NONE
THREADSMAX=NONE
MMAPAREAMAX=NONE
MEMLIMIT=8G The Apache Tomcat server delivered with the product uses port 8080 as its default. If this port is already used by another Web Server, modify the file called server.xml in the /uss/lpp/fdrupstreamweb/apache-tomcat-8.5.14/conf/ directory to a free port.
The Netstat command can be used to list ports that are currently in use: TSO option 6: netstat conn server modify command: d tcpip,,netstat,conn,server
- To start the UPSTREAM Web Portal, the following are needed:
– (2) PROCs, samples are provided in Step 6 and Step 7
– (1) IBMRACF/CAACF2/CATopSecret Userid/Acid as outlined previously
– (1) IBMRACF/CAACF2/CATopSecret STARTED class entry for the Started Task, see next step. - Create an IBMRACF STARTED class entry for your WPORTAL Started Task PROC. Here is an example of a RACF RDEFINE command to do this. Please consult with your system security personnel for alterations to this or for CAACF2 or CATopSecret instructions and procedures.
RDEFINE STARTED WPORTL.* UACC(NONE) STDATA(USER(xx…xx)
GROUP(STCGRP) TRUSTED(YES) PRIVLEDGED(NO) TRACE(NO)) - Refresh the RACF Started Class Profiles via the SETROPTS command, again consult your system security personnel for CAACF2 or CATopSecret command syntax:
SETROPTS RACLIST(STARTED) REFRESH - Create the first STC PROC (WPORTAL) as follows. It is used to get the Started Task running:
//WPORTAL PROC
//*
//* PROC FOR UPSTREAM WEB PORTAL STARTED TASK
//*
//WPORTL EXEC WEBPORTL
//*
//STDENV DD DISP=SHR,DSN=USTEST.WPORTAL.CNTL(WPORTL) - Create the second started task (WEBPORTL) as follows, it invokes the JAVA Run Time Environment to get the TOMCAT web server started and prepare the Web Portal for user logins
//*
//* JVM PROC CALLED BY THE UPSTREAM WEB PORTAL STARTED TASK
//*
//WEBPORTL PROC ARGS=,LEPARM='',
// JAVACLS='org.apache.catalina.startup.Bootstrap',
// ARGS='start',
// LEPARM='TERMTHDACT(UADUMP)',
// VERSION='86',
// LOGLVL='+I',
// OUT=X
//*//WEBPORTL EXEC PGM=JVMLDM&VERSION,REGION=0M,
// PARM='&LEPARM/&LOGLVL &JAVACLS &ARGS'
//SYSPRINT DD SYSOUT=&OUT
//SYSOUT DD SYSOUT=&OUT
//STDMSG DD SYSOUT=&OUT
//STDOUT DD SYSOUT=&OUT
//STDERR DD SYSOUT=&OUT
//CEEDUMP DD SYSOUT=&OUT
//SYSUDUMP DD SYSOUT=&OUT
//ABNLIGNR DD DUMMY
//*//WEBPORTL PEND Determine the your currently installed version of JAVA; if you are running the IBM /bin/sh shell, issue the TSO command “oshell whence java” from the ISPF option 6 command line or from the TSO/E READY prompt. The UPSTREAM Web Portal is designed and tested to work with the 64 bit Java 8 JVM. Here is what the output would look like if you executed it from ISPF option 6 and you are running 64 bit Java 8.0:
oshell whence java/usr/lpp/java/J8.0_64/bin/java
***Build and update the data set member pointed to by the STDENV DD statement in the example WPORTAL Started Task PROC to customize the supplied values to reflect your installation specific choices. The following lines are the most likely to need customization:
export JAVA_HOME=/usr/lpp/java/J8.0_64
export TOMCAT_HOME=/usr/lpp/fdrupstreamweb/apache-tomcat-8.5.14
export IDP_WP_HOME=/usr/lpp/fdrupstreamwebHere is a sample of a complete STDENV data set member:
# This is a shell script which configures
# any environment variables for the Java JVM.
# Variables must be exported to be seen by the launcher.
export JAVA_HOME=/usr/lpp/java/J8.0_64
export TOMCAT_HOME=/usr/lpp/fdrupstreamweb/apache-tomcat-8.5.14
export IDP_WP_HOME=/usr/lpp/fdrupstreamweb
LIBPATH=/lib:/usr/lib:"${JAVA_HOME}"/bin
LIBPATH="$LIBPATH":"${JAVA_HOME}"/bin/classic
LIBPATH="$LIBPATH":"${TOMCAT_HOME}"/libexport LIBPATH="$LIBPATH":
CATALINA_HOME="${TOMCAT_HOME}"
export CATALINA_HOME="$CATALINA_HOME":
CATALINA_BASE="${TOMCAT_HOME}"
export CATALINA_BASE="$CATALINA_BASE":CLASSPATH="${JAVA_HOME}/lib/tools.jar"
CLASSPATH="$CLASSPATH":"${TOMCAT_HOME}/bin/bootstrap.jar"
CLASSPATH="$CLASSPATH":"${TOMCAT_HOME}/bin/tomcat-juli.jar"
CLASSPATH="$CLASSPATH":"${TOMCAT_HOME}"/lib
export CLASSPATH="$CLASSPATH":# Configure JVM options
IJO="-Xms256m -Xmx1024m"
IJO="$IJO -Dibm.serversocket.recover=true"
IJO="$IJO -Dsun.lang.ClassLoader.allowArraySyntax=true"
# IJO="$IJO -Dfile.encoding=ISO8859-1"IJO="$IJO -Dcatalina.base=${TOMCAT_HOME}"
IJO="$IJO -Dcatalina.home=${TOMCAT_HOME}"
IJO="$IJO -Djava.io.tmpdir=${TOMCAT_HOME}/temp"
IJO="$IJO -Dactivate.saf.manager=false"
export IBM_JAVA_OPTIONS="$IJO "export JAVA_DUMP_HEAP=false
export JAVA_PROPAGATE=NO
export IBM_JAVA_ZOS_TDUMP=NO- Start your UPSTREAM Web Portal Started Task:
S WPORTAL
- Any errors will be reflected in TOMCAT installation LOGS directory files catalina.out or catalina.log.
Existing WebSphere Web Server Deployment#
Start a Web browser and go to the administrative console of your z⁄OS system WebSphere Application Server. The Web address is:
http://x.xx.xxx.xxx:pppp/adminwhere:
x.xx.xxx.xxx is the IP address, and
pppp is the port that the server is running on.
- Login and select Enterprise Applications, then select Install New Application.
- Select Server Path and enter the location of the EAR file in the z/OS file system directory: /usr/lpp/fdrupstreamweb/fdrupstream.ear
- Click Next.
- Select Generate Default Bindings and click Next. Enter the Application Name you want your application to use and click Next. Select Web Module and click Next. Select Module and click Next. Finally, click Finish. You should see the message, Application xxxxxxx installed successfully. Select Yes to Save to Master Configuration.
After you saved the configuration, select Enterprise Applications. In the list of applications, find UPSTREAM Web Portal you just installed and select the box in front of it. Click Start. When the status symbol indicates that your UPSTREAM Web application has been started, your UPSTREAM Web application is available.
- Set the following environment variable:
export IDP_WP_HOME=/usr/lpp/fdrupstreamweb
Existing Tomcat Web Server Deployment#
- Copy the /uss/lpp/fdrupstreamweb/deployable/fdrupstream.war file into the directory used by your existing Apache Tomcat server for Application deployment.
- Set the following environment variable:
export IDP_WP_HOME=/usr/lpp/fdrupstreamweb - Verify that $JAVE_HOME variable is set to the actual Java home directory and that $PATH variable contains $JAVA_HOME/bin. $LIBPATH must contain $JAVA_HOME/bin and $JAVA_HOME/bin/classic.
- Deploy the application using the Tomcat Manager Application
http:\\dns.name:8080\manager - Start the Web Portal application after the deployment.
- For WebSphere 8.5.x which currently recognizes and Supports only JPA 1.0 and 2.0, there is an option to enable and configure a third-party persistence provider or application-managed persistence (e.g. EclipseLink) that implements JPA 2.1.
The JVM System Property "com.ibm.websphere.persistence.ApplicationsExcludedFromJpaProcesssing" has been created to allow customers to disable WebSphere Application Server JPA initialization when it is not needed. Use the following instructions to enable this property:
– Open the administrative console.
– Select Servers -> Server Types -> WebSphere application servers.
– Select the server you want to configure.
– In the Server Infrastructure area, select Java and Process Management -> Process definition.
– In the Server Infrastructure area, select Process Definition.
– In the Additional Properties area, select Java Virtual Machine.
– In the Additional Properties area, select Custom Properties.
– Select the New box.
– In the Name entry field, type: com.ibm.websphere.persistence.ApplicationsExcludedFromJpaProcessing
– In the Value entry field, type the names of the applications to be excluded from JPA processing. If there are multiple applications separate each with the “:” character. If you wish to specify all applications simply type the “*” character.
– Select OK.
– Restart the server. - Review the Tomcat Log Files in Tomcat.
Installing UPSTREAM Web Portal on Windows
Overview
The UPSTREAM Web Portal operates as a web application implemented as a Windows Service. It provides the following major features:
- UPSTREAMClient upgrades
- Configuration
- Reporting
- Restores
Product Download
For the install, log into the BMC Support and download the installation package to a location on your Windows Server.
Product Configuration
Decide if UPSTREAM Web Portal will be used from an existing IBM WebSphere Server, an existing Apache Tomcat Server, or using the Apache Tomcat Server shipped with the product. See Existing Web Server Deployment.
Installing an UPSTREAM Windows Web Portal Using the Installation Wizard
Follow these steps to install a typical UPSTREAM Web Portal from the installation media or location, double click on the provided Windows Web Portal installer.exe file.
Setup Wizard
Read the license agreement on the Welcome panel and select “I accept the agreement”.
License Agreement
Press the Next button.
Web Configuration
Press the Next button.
Internal Tomcat Configuration
Select the Install directory. Decide whether the Tomcat server shipped with the product should be used and determine what ports the Tomcat server should use for the Web Portal Application. Click Next
Configure User Authentication
If you wish to use SSL you will need an LDAP server and check the Use LDAP SSL connection for user authentication checkbox. You can then decide to require externally signed certificates or use self-signed certificates.
If you are using self-signed certificates, check the Use self-signed certificate check-box and specify a path to the certificate. Click Next.
Database Configuration
Decide if an Embedded Derby Database should be used, or if the product should point to an external database.
Press the Next button.
External Database Configuration
Press the Next button.
Ready to Install
Press the Next button to perform the Install.
Install Complete
Test Web Portal Deployment
The UPSTREAM Web Portal can now be accessed using the following URL:
where:
x.xx.xxx.xxx is the IP address, and
pppp is the port that the Tomcat Server is running on. (Default 8080)
Existing Web Server Deployment#
The UPSTREAM Web Portal supports deployment to existing Web Servers such as IBM WebSphere and/or Apache Tomcat as well.
After the product has been installed using the above, a few directories are created that contain files needed for deployment.
- c:/program files/Innovation Data Processing/fdrupstreamweb/deployable - contains the files “fdrupstreamweb.ear” and “fdrupstreamweb.war” required for the Tomcat and/or WebSphere administrator to install and deploy the Web Portal.
Use of an External Derby Database
- c:/program files/Innovation Data Processing/fdrupstreamweb/conf - contains the “wpProfile.properties” files required to deploy the internal Derby database. If an external Derby Database is required then this file should be edited. Uncomment the first section and make changes to connect to the running Derby DB Instance. Edit the section that is currently uncommented.
WebSphere Instructions
If installing into an existing WebSphere application server, follow the steps outlined below:
Start a web browser and go to the administrative console of your choice of system WebSphere Application Server. The web address is:
http://x.xx.xxx.xxx:pppp/adminwhere:
x.xx.xxx.xxx is the IP address, and
pppp is the port that the server is running on.
- Login and select Enterprise Applications, then select Install New Application.
Select Server Path and enter the location of the EAR file in the file system directory:
c:/program files/Innovation Data Processing/fdrupstreamweb/deployableClick Next.
- Select Generate Default Bindings and click Next. Enter the Application Name you want your application to use and click Next. Select Web Module and click Next. Select Module and click Next. Finally, click Finish. You should see the message, Application xxxxxxx installed successfully. Select Yes to Save to Master Configuration.
- After you saved the configuration, select Enterprise Applications. In the list of applications, find UPSTREAM Web Portal you just installed and select the box in front of it. Click Start. When the status symbol indicates that your UPSTREAM Web application has been started, your UPSTREAM Web application is available.
Tomcat Instructions
If installing into an existing Tomcat application server, follow the steps outlined below:
Copy the fdrupstream.war file from
c:/program files/Innovation Data Processing/fdrupstreamweb/deployableinto the directory used by your existing Apache Tomcat server for Application deployment.
- Set the following environment variable:
Verify that the %JAVA_HOME% variable is set to the actual Java home directory and that the PATH variable contains %JAVA_HOME%. LIBPATH must contain %JAVA_HOME/bin% and %JAVA_HOME/bin/classic%.