Installation DS NOC

8/17/2019 Installation DS NOC

1/19


2/19

DS-NOC Installation Guide Generated on: 1/22/15

v13 [Revision Date: January 22, 2015] Page: 2

© Asigra Inc. All Rights Reserved. Confidential.

Disclaimer

Information in this document is subject to change without notice and does not represent acommitment on the part of ASIGRA Inc.

ASIGRA Inc. makes no representation or warranty, express, implied, or statutory, with respect to,and assumes no responsibility for the accuracy, completeness, sufficiency or usefulness of theinformation contained herein.

This document may contain sample screen shots, used to demonstrate Asigra Cloud Backup™procedures. All information appearing in this document is used for illustration purposes only, and itshould be considered fictitious.

Copyright

The software described in this document is furnished under a license agreement. It is against thelaw to copy the software on any medium except as specifically allowed in the license agreement.

“Asigra”, the Asigra logo, “Asigra Cloud Backup”, “Recovery is Everything”, and “Recovery LicenseModel” are trademarks of Asigra Inc. All other brand and product names are, or may betrademarks of their respective owners.

Document Prepared by:


1120 Finch Avenue West, Suite 400

Toronto, Ontario, CANADA M3J 3H7

[email protected]

www.asigra.com


3/19


4/19

Asigra Clou d Backup™ DS-NOC




Asigra Cloud Backup™ DS-NOC

The Asigra Cloud Backup™ DS-NOC (Network Operation Control) is a J2EE (Java) applicationthat allows access to DS-Systems, BLM Archivers, DS-License Servers and DS-Billing Systemsthrough a Web-based interface.

DS-NOC is designed for three types of users: Service Providers, Sales Groups (and their SalesRepresentatives), and End Users (of the Cloud Backup service).

Service Providers can:

• use this Web site to manage and monitor all Asigra Cloud Backup products:DS-System, DS-Billing, BLM Archiver, DS-License and DS-Client

• configure DS-NOC, create and manage DS-NOC (Web site) users andpermissions

• create Accounts / DS-Clients on DS-System

• view DS-System / BLM / DS-Billing / DS-Client reports and logs

• perform specific tasks on BLM Archiver

• monitor DS-License Server / DS-System / BLM / DS-Billing / DS-Client, etc.

Sales Groups can:

• use this Web site to manage and monitor DS-System Accounts / DS-Clientsbelonging to their customers

• create, manage, and monitor their Customer Account / DS-Clients

• create a Subscription ID for their Sales Representatives

• view reports, etc.

End Users can:• use this Web site to create new DS-Clients

• download DS-Client Installation Packages and any other software provided bythe Service Provider

• login to DS-NOC and view their DS-Client status, view reports, and requestand download Restorable Images from BLM

• restore data via a web interface

This document contains instructions about installing the Asigra Cloud Backup™ DS-NOC. Itcontains brief instructions about installing third-party software that is needed by the DS-NOC and itcontains detailed instructions about how to configure the DS-NOC.

The installation instructions for third-party products is brief and this document is not intended to be

a complete installation guide for these products. For additional information about installing thethird-party applications, please consult the installation manuals for these applications.

• For Windows platform, see: “II. Installing DS-NOC on Windows” on page 6

• For Linux platform, see: “III. Installing DS-NOC on Linux (RedHat 6)” onpage 14


5/19





I. Hardware and Software Requirements

I.1 Required third-party softwareThe DS-NOC itself is a J2EE application and as such, it can be installed on other platforms likeLinux (SUSE, RedHat).

The software requires a servlet container to function. The application was developed and testedwith Tomcat. You can download Tomcat from http://www.apache.org. This document describesinstalling the program using Apache Tomcat 7.0.

Apache Tomcat requires a Java JRE in order to function correctly. You may download the JavaJRE (Java version 1.7 or above is required) from http://java.sun.com. Make sure you are using thecorrect version of Java for the Apache Tomcat server version (Apache Tomcat 7.0 works with Java1.7).

The DS-NOC uses PostgreSQL as a database back-end. You can download the PostgreSQLinstallation for your platform from http://www.postgresql.com .

I.2 Hardware Minimum RequirementsYou should use the best hardware possible to maximize Asigra Cloud Backup™ performance. If

applicable, it is strongly recommended that you use the fastest brand-name componentsavailable.You must provide sufficient hardware resources to support the number of users that willbe accessing DS-NOC.

I.3 Supported Platforms

Third-Party Software Version

Apache Tomcat (Standalone or Cluster) 7.0, 8.0

Java JRE 1.7, 1.8

PostgreSQL

• For the official list of this product’s supported Databases

and versions, refer to the Installation and Support Matrix.• 9.1 (upgrade existing installations only)

• 9.2 (new windows and upgrade linux installations)

• 9.3 (new linux installations)

Hardware x64 (64-bit) Architecture

CPU > 3 GHz

RAM > 2 GB RAM

Free disk space for application and database > 2 GB

For the official list of this product’s supported Operating Systems and versions, refer to the Installation

and Support Matrix. This can be found on the Installation DVD in the following path:• \Documentation\Release_Information

Windows Platform Version

Windows® 2012

x64 (64-bit)

• Standard / R2 (x64)

• Datacenter / R2 (x64)

UNIX Platform Version

SUSE Linux x64 (64-bit) • Enterprise Server 11 SP3 (x64)

Red Hat Linux x64 (64-bit) • Enterprise Linux 6.5 - ES/AS (x64)


6/19





II. Installing DS-NOC on Windows

II.1 Installing Java JRE 1.7The Java JRE 1.7 for your platform can be downloaded from:

ht t p: / / www. oracl e. com/ t echnetwork/ j ava/ j avase/ downl oads/ i ndex. ht ml

II.1.1 Installation stepsJava JRE 1.7: Follow the installation instructions that come with the package.

II.2 Installing PostgreSQL (Windows)1. Download the PostgreSQL installation for your platform from http://

www.postgresql.org.

TIP: It is easiest to download the “pre-built binary package” for your platform.

2. Follow the instructions that come with the PostgreSQL installation.


7/19


8/19





3. Click “Next”. Change "HTTP 1.1 Connector Port" to 80 (the default is 8080). Select apassword for the admin user name and make sure it is assigned to the “manager-gui”role.

4. Click “Next”. Select the path to the Java JRE which you installed in step 2.1.

• When you reach this screen, enter the path to the Java JRE which youinstalled in step 2.1.


9/19





5. Click “Next”. Keep the defaults for the installation folder:

• v.7.0 path is:

"C: \ Progr amFi l es ( x86) \ Apache Sof t ware Foundat i on\ Tomcat 7. 0"

6. Click "Install" to start the installation.

7. Leave "Run Apache Tomcat" selected in the final wizard page and press "Finish".


10/19





II.4 Install ing the DS-NOC (Windows)

Note: The current noc.war file is larger than the maximum default upload size supported by

Tomcat. Therefore, before deploying the WAR file, you must perform the Tomcat

configurations described in the Knowledge Base article “TROUBLESHOOTING:

Uploading WAR files larger than 50 MB” on page 17.

II.4.1 Installation contents

The DS-NOC installation (found in the installation DVD folder: \Software\DS-NOC\) contains thefollowing components:

• noc.war - The main archive containing the Asigra Cloud Backup™ DS-NOCapplication.

• nocapi.wsdl - Contains function declarations and data types to be used withDS-NOC API.

II.4.2 Installing the ASIGRA DS-NOC application:

1. Connect to the Tomcat web server (use "http://localhost/" if it is on the local computeror “http://” for a remote computer) and press "Manager

App". When prompted for the username and password, enter the administratorusername/password that you created at Section II.3.1 Step 3.


11/19





2. Scroll down in the management window until you reach "WAR file to deploy". Click"Browse" and select the "noc.war" archive. Now click "Deploy".

• Refer to the Knowledge Base article “TROUBLESHOOTING: Uploading WARfiles larger than 50 MB” on page 17.

II.4.3 Configure DS-NOC to use a PostgreSQL database:

You must configure the DS-NOC to use the PostgreSQL database you installed in step “II.2Installing PostgreSQL (Windows)” on page 6. These settings are saved on the DS-NOC server inthe file: "C:\Program Files\Apache Software Foundation\Tomcat 7.0\conf\asigraweb.cfg"

1. After deploying the DS-NOC successfully, connect to the application by opening yourWeb browser and selecting the URL "http://localhost/noc/" (if it is on the localcomputer) or “http:///noc/” (for a remote computer).

2. The configuration screen appears (only the first time you access the DS-NOC). Thisscreen is slightly different, depending on if you connect from the local computer or


12/19





from a remote computer.

DS-NOC Configu ration Password (Remote connection only):

• You can perform the configuration from a remote machine, however forsecurity purposes, you must provide a configuration password. This passwordmust already be configured for the remote DS-NOC configuration to work. It isdefined on the web server machine in the file "C:\Program Files\ApacheSoftware Foundation\Tomcat 7.0\conf\asigraweb.cfg". It will be removed fromthat file once this step is completed successfully.

PostgreSQL Database Information:• You must enter the server information where the PostgreSQL DB resides, and

the username and password for the PostgreSQL database super-user you setup at installation. (Note that PostgreSQL normally uses port 5432.)

• Click on the "Apply configuration" button. The database will be created andthe configuration settings saved.

3. A screen describing the configuration steps appears. If the message on top says theconfiguration was successful, you can click on the "start using" part of the message, oryou can open your Web browser and select the URL "http://localhost/noc/" or “http://

Connecting from a

remote computer

Connecting from the

local computer.


13/19





/noc/”.

4. Choose "Login" and use "root/root" as username/password.

• User “root” is always a super-user and cannot be deleted.

• Change the password from "root" as soon as possible by using:"User Management - >Passwor d"

- OR -

"My Prof i l e - > Password"


14/19





III. Installing DS-NOC on Linux (RedHat 6)

III.1 Installing Java JRE 1.7 (64-bit)The Java JRE 1.7 for your platform can be downloaded from:

ht t p: / / www. oracl e. com/ t echnetwork/ j ava/ j avase/ downl oads/ i ndex. ht ml

III.1.1 Installation s tepsJava JRE 1.7: Follow the installation instructions that come with the package.

III.2 Installing PostgreSQL (Linux 64-bit)1. Download the PostgreSQL installation for your platform from http://

www.postgresql.org.

TIP: It is easiest to download the “pre-built binary package” for your platform.

2. Follow the instructions that come with the PostgreSQL installation.

III.3 Installing Apache Tomcat v.7.0 (Linux 64-bit)The most recent Apache Tomcat installation can be downloaded from http://www.apache.org. Thisdocument covers the installation of Apache Tomcat 7.0 on Linux (RedHat Enterprise 6). Thissection describes a Standalone Apache Tomcat installation. For information on how to installTomcat in Cluster mode, refer to the Apache documentation.

Note: Make sure that you are not running any other Web Servers that are listening on port 80 of

the DS-NOC machine.

III.3.1 Installation s teps1. Download the Apache Tomcat v.7.0 installation for your platform.

2. If you downloaded a tar.gz archive, extract Apache Tomcat by running the followingcommands:

gunzi p apache- t omcat - 7. 0. 11. t ar. gz

t ar - xvf apache- t omcat - 7. 0. 11. t ar

3. Follow the instructions that come with the Apache Tomcat installation.

4. Point the JAVA_HOME environment variable to a JRE v.1.7 (or higher) that is runningon the DS-NOC machine (i.e. the one you installed in step “III.1 Installing Java JRE1.7 (64-bit)” on page 14).

Note: You can also point the JRE_HOME environment variable to a JDK v.1.7 (or higher) that is

running on the DS-NOC machine.

5. Start Apache Tomcat by running the following command that can be found in the$CATALINA_HOME/bin directory:

start up. sh

6. You should be able to access “http://localhost:8080” in your Web Browser.

7. Change Apache Tomcat to accept connections on Port 80:

• Edit the server.xml file that is found in $CATALINA_HOME/conf.

• Modify the connector Port to 80


15/19





8. To create a username and password, edit the tomcat_users.xml file that is found in$CATALINA_HOME/conf. Add the following lines:

Note: Make sure you un-comment the Roles section in the tomcat_users.xml file.

9. Restart Tomcat with the following commands:

. / shut down. sh

. / s tar t up. sh

10. Open a Web Browser and access Tomcat by typing "http://localhost/" or “http:///” in the Web Browser’s address bar.

11. Open “Manager App”. It will ask you for a username and password.

• Use the one created in step 8 above.

III.4 Installing the DS-NOC (Linux)Same as for Windows:

• See “II.4 Installing the DS-NOC (Windows)” on page 10.

PHP-SOAP Requirement for Linux packages:

• Newer Linux versions have expanded the PHP offerings, but have notincluded them in the default installation.

• In order for the DS-NOC API to function on Linux installations, you must makesure that “php-soap” is installed on the Linux operating system.

• Find and run the corresponding php-soap rpm package for your operatingsystem and run it to make sure it is available for the DS-NOC.

UNIX Platform php-soap RPM required

SUSE Linux Enterprise Server 11 SP2 (x64) php5-soap-5.2.14-0.7.24.1.x86_64.rpm

SUSE Linux Enterprise Server 11 SP3 (x64) php5-soap-5.3.17-0.13.7.x86_64.rpm

Red Hat Linux Enterprise Linux 6.4 - ES/AS (x64) php-soap-5.3.3-22.el6.x86_64.rpm

Red Hat Linux Enterprise Linux 6.5 - ES/AS (x64) php5-soap-5.5.3-26.el6.x86_64.rpm


16/19





Configuring different (multiple) DS-NOC ContextsCreation Date: March 24, 2010

Revision Date: September 13, 2011

Product: DS-NOC

Summary

The default deployment of DS-NOC (with the noc.war archive file) will create a DS-NOC that isaccessible through the following context:

ht t p: / / l ocal host/ noc

or f or r emote machi nes: htt p: / / / noc/

However, the DS-NOC can be deployed in multiple ‘contexts’, allowing you to create separate DS-NOC portals for use with specific customers.

Details

To deploy DS-NOC in a different context:

1. Make a copy of the noc.war archive file and rename it to the ‘context’ you want to use.

• For example: Use the context ‘newsite’, that can be accessed through theaddress “http://localhost/newsite“ (or “http:///newsite“)

2. Follow the same steps to deploy the renamed file (newsite.war) on the Web Server.

3. Connect to the application via the new context (“http://localhost/newsite“ or “http:///newsite“) and configure the Database Host andDatabase Name.

4. Continue with the same steps from the following installation section:

• See “II.4 Installing the DS-NOC (Windows)” on page 10.

• See “III.4 Installing the DS-NOC (Linux)” on page 15.

The information provided in this document is provided "AS IS", without warranty of any kind. ASIGRA Inc. (ASIGRA) disclaims all warranties, either express or implied. In noevent shall ASIGRA or its business partners be liable for any damages whatsoever, including direct, indirect, incidental, consequential, loss of business profits or special

damages, even if ASIGRA or its business partners have been advised of the possibility of such damages. © Asigra Inc. All Rights Reserved. Confidential.


17/19





TROUBLESHOOTING: Uploading WAR files larger than50 MBCreation Date: March 15, 2013

Revision Date: March 15, 2013

Product: DS-NOC

Summary

By default, the Tomcat 7 Manager has an upload file size limit of 50 MB. As of the latest revisiondate of this article, the DS-NOC WAR file has grown larger than this default limit.

Problem:

If you upload a WAR file larger than the configured limit, the Tomcat 7 Manager application reportsan error:

The ser ver encountered an i nternal er r or ( ) t hat prevent ed i t f r om

f ul f i l l i ng thi s request .exception

j ava. l ang. I l l egal Stat eExcepti on:or g. apache. t omcat . ut i l . ht t p. f i l eupl oad. Fi l eUpl oadBase$Si zeLi mi t ExceededExcept i on: t he request was r ej ected because i t s si ze ( 54010957) exceeds t heconf i gur ed maxi mum ( 52428800)

Reason:• With Tomcat 7, by default the value of 'max-file-size' and ‘max-request-size’

are set to 50 MB.

max- f i l e- si ze = 52428800

max- r equest - si ze = 52428800

• Now the size of noc.war exceeds 50 MB, therefore uploading DS-NOC usingthe Tomacat Manager will fail.

Solution:

There are two solutions if you encounter this problem.

Solution 1. Increase the value of max-file-size and the value of max-request-size.

1. Edit the file 'web.xml':

• For Windows, the file 'web.xml' can be located under the following directory:

C: \ Pr ogr am Fi l es\ Apache Sof t wareFoundat i on\ Tomcat 7. 0\ webapps\ manager\ WEB- I NF\ web. xml

• For Linux, the file 'web.xml' can be located under the following directory:

/ opt / apache- t omcat - 7. 0. 25/ webapps/ manager / WEB- I NF/ web. xml2. Increase the max-file-size and max-request-size to 100MB:

. . .

104857600

104857600

. . .


18/19





Solution 2. Upload noc.war wi thout using Tomcat Manager.

1. To manually deploy DS-NOC:

• For Windows, copy the file 'noc.war' to:

C: \ Progr amFi l es\ Apache Sof t ware Foundat i on\ Tomcat 7. 0\ webapps

• For Linux, copy the file 'noc.war' to:

/ opt / apache- t omcat- 7. 0. 25/ webapps

The information provided in this document is provided "AS IS", without warranty of any kind. ASIGRA Inc. (ASIGRA) disclaims all warranties, either express or implied. In no

event shall ASIGRA or its business partners be liable for any damages whatsoever, including direct, indirect, incidental, consequential, loss of business profits or specialdamages, even if ASIGRA or its business partners have been advised of the possibility of such damages. © Asigra Inc. All Rights Reserved. Confidential.


19/19




FAQ: How to upgrade an existing DS-NOCCreation Date: January 27, 2014

Revision Date: January 27, 2014

Product: DS-NOC

Summary

This article gives instructions on how to upgrade and existing DS-NOC installation. Although theupgrade process is simple, this FAQ may be helpful, particularly for customers performing anupgrade of a DS-NOC installation for the first time.

Details

To upgrade an existing DS-NOC:

1. In Tomcat Manager > Undeploy “DS-NOC”.

2. Restart Tomcat Manager.

3. Deploy the new “noc.war” provided on the new release / service pack DVD or ISO.

• This is described in “II.4 Installing the DS-NOC (Windows)” on page 10.

The information provided in this document is provided "AS IS", without warranty of any kind. ASIGRA Inc. (ASIGRA) disclaims all warranties, either express or implied. In noevent shall ASIGRA or its business partners be liable for any damages whatsoever, including direct, indirect, incidental, consequential, loss of business profits or special

damages, even if ASIGRA or its business partners have been advised of the possibility of such damages. © Asigra Inc. All Rights Reserved. Confidential.

Date post:	06-Jul-2018
Category:	Documents
Upload:	patrice-tano
View:	222 times
Download:	0 times

Installation DS NOC

Documents