Download

Download the CloudPortal Business Manager software.

System Preparation

All the operations listed below should be run as root.

Unarchive Install Package

To unarchive the install package tarball, run (where x.y.z is the version you have downloaded):

# tar -xvf CloudPortal-x.y.z-centos.tar.gz

Then navigate into the newly created CloudPortal-x.y.z-centos folder:

# cd CloudPortal-x.y.z-centos

Installing MySQL 5.6

1. Run the ./install.sh script and choose option "D" to install the MySQL 5.6 database server.

   Accept the license agreement before selecting the "D" option.

    # ./install.sh  Welcome to the Accelerite CloudPortal Business Manager Installer. What would you like to do?  D) Install/Upgrade the database server  I) Install & Configure CloudPortal Business Manager  C) Integrate with Accelerite CloudPlatform  Q) Quit  > D  

2. When prompted, provide a user name and password. You can set these to any desired value that is valid for a MySQL database. This step creates a new user account that CloudPortal will use to access the database.
   Note: Database password is mandatory.
3. Exit the installation setup:

   Welcome to the Accelerite CloudPortal Business Manager Installer. What would you like to do? D) Install/Upgrade the database server I) Install & Configure CloudPortal Business Manager C) Integrate with Accelerite CloudPlatform Q) Quit > Q

4. Stop mysql service:

   service mysqld stop

5. Edit the file /etc/my.cnf and add the following line under the [mysqld] section::

    max_connections=400 

    Note: To set the binary logs configuration and save disk space, see FAQ. 

6. Ensure that MySQL DB encoding format is UTF-8 MB4 Character Set (4-Byte UTF-8 Unicode Encoding) and confirm the following under the [mysqld] section:

    [mysqld]  character-set-client-handshake = FALSE  character-set-server=utf8mb4  collation-server=utf8mb4_unicode_ci 

7. Start the MySQL service.

    # service mysqld start 

   Note: Use the following command to check if the database encoding format is UTF-8 MB4:

    mysql>show variables like  "%char%";     mysql>show variables like  "%coll%"; 

Language Settings for Linux

The default language setting for CloudPortal Business Manager is English.

Installing CloudPortal Business Manager

For each CloudPortal Business Manager node, run the install.sh script from the package. Select option I:

Accept the license agreement before selecting the "I" option.

# ./install.sh  Welcome to the Accelerite CloudPortal Business Manager Installer. What would you like to do?  D) Install/Upgrade the database server  I) Install & Configure CloudPortal Business Manager  C) Integrate with Accelerite CloudPlatform  Q) Quit  > I

Enter Y to confirm that you have upgraded your mysql server before continuing.

Enter Y if you want Central Authentication Service (CAS) installed along with CloudPortal Business Manager, and N if you want to install only CloudPortal.

Would you like to install CAS with CloudPortal (Y/N)?  > Y

Installation begins. CloudPortal Business Manager checks for the Java version in the system and installs Oracle JRE 1.7. Enter Y to accept the Oracle license agreement for Java SE to download and install JRE 1.7.

Do you wish to change this server to run on the UTC timezone (y/N)?

CloudPortal Business Manager installation is complete.

The CloudPortal Business Manager Configuration Tool starts automatically once the installation is complete.

  You've successfully installed CloudPortal Business Manager.   Now proceed to configure the CloudPortal Business Manager. Welcome to the Accelerite CloudPortal Business Manager Configuration Tool.     D) Install/Upgrade the database server  G) Configure CloudPortal Business Manager  C) Integrate with Accelerite CloudPlatform  Q) Quit    > G

The initial setup of CloudPortal Business Manager is completed.

service cloud-portal start

Enabling Network Security for Administrator Login

Enabling CAS Authentication

CloudPortal supports the use of Central Authentication Service (CAS) for single sign-on, which enables access to multiple password-protected systems after logging in just once. To make this work, you need to update CAS with the location of the cloud_portal database and list the services with which CAS will be used.

1. Log in as root to the host running CloudPortal Business Manager.
2. Edit the file /usr/share/vts3/repository/prop/cloud.properties and set these parameters.
   • Un-comment the following property to enable CAS. By default, native authentication is enabled.

     vmops.authentication.service=cas

   • Replace localhost:8080 in the following lines with the <public Host name or IP>:<public host port> as shown below:

     • # URL to the CAS login page used for single sign on.  cas.login.url=http://<public Host name or IP>:<public host port>/cas  

     • # URL for CAS single sign out.  cas.logout.url=http://<public Host name or IP>:<public host port>/cas/logout  

     • # Callback URL used by CAS to redirect back to CloudPortal.  cas.service.url=http://<public Host name or IP>:<public host port>/portal/portal/j_spring_cas_security_check  

   • cas.login.url: Full public URL (including http:// or https://, hostname, optional port, and path) of the login page displayed to the user for single signon. For example, http:// mypublichostname:8080/cas.
   • cas.logout.url: Full public URL of the page where a user can log out of single sign-on. For example, http://mypublichostname:8080/cas/logout.
   • cas.service.url: Full public callback URL used by CAS to redirect back to CloudPortal Business Manager. For example, http://mypublichostname:8080/portal/j_spring_cas_security_check.
   • cas.validator.url: Full private URL used in internal calls from CloudPortal Business Manager server to CAS server to validate the CAS ticket. This should be a URL that is not accessible from outside your installation. If using HTTPS, this site must have a valid certificate issued by a trusted certificate authority. For example, http://myprivatehostname:8080/cas.
3. If any other application needs to be authenticated via CAS, then edit the /usr/share/vts3/repository/prop/deployerConfigContext.xml file. Refer to Adding a new service to CAS.
4. Restart CloudPortal Business Manager.

   # service cloud-portal restart

Integration with CloudPlatform

To integrate CloudPortal with CloudPlatform, run the ./install.sh script on each CloudPlatform server, and then select Integrate with Accelerite CloudPlatform from the menu. This will place files within CloudPlatform that are required for single sign-on integration with CloudPortal. Note that after the files are copied over for integration, you will no longer be able to access the CloudPlatform management server using http://<hostname>:8080/client. It is recommended that you access the CloudPlatform management UI by first logging into CloudPortal and then clicking the Launch Cloud Console button on the dashboard. Alternatively, you can access the CloudPlatform management UI directly by using http://<hostname>:8080/client/?direct=true.

# ./install.sh  Welcome to the Accelerite CloudPortal Business Manager Installer. What would you like to do?    D) Install/Upgrade the database server  I) Install & Configure CloudPortal Business Manager  C) Integrate with Accelerite CloudPlatform  Q) Quit  > C

Multinode Installation

Setting up a Proxy Server

In order to add a proxy server to front CloudPortal servers, the steps given below must be followed.

The proxy server can be added in a variety of ways. The steps given below illustrate one typical technique using Apache HTTP Server running on CentOS 6.x.

• On the Apache server, install the module that provides SSL and TLS support.

   # yum install httpd mod_ssl 

• Create the file /etc/httpd/conf.d/cloud.conf, and add proxying (and, if needed, load balancing) directives

  For a two-node installation where Apache and CloudPortal are run on separate nodes, use rules like the following. Replace CloudPortalNode with the private hostname or IP of your own machines.

  HTTP Proxy configuration:

   ProxyPreserveHost on  ProxyPass /portal http://CloudPortalNode:8080/portal  ProxyPass /cas http://CloudPortalNode:8080/cas  ProxyPassReverse /cas http://CloudPortalNode:8080/cas  ProxyPass / http://CloudPortalNode:8080/portal  

  AJP Proxy configuration:

   ProxyPass /portal ajp://CloudPortalNode:20410/portal  ProxyPass /cas ajp://CloudPortalNode:20410/cas  ProxyPass / ajp://CloudPortalNode:20410/portal  

  Note: CloudPortalNode will display 8009 as the default value. Edit the file /usr/share/vts3/config/tomcat-server.xml and change the value of the port from 8009 to 20410 at this line:

   <Connector port="20410" protocol="AJP/1.3"  redirectPort="8443"  URIEncoding="UTF-8"/> 

  For a three-node installation where Apache is on one node and CloudPortal is on two additional nodes, use directives like the following. Replace the CloudPortalNode placeholders below with the private hostnames or IPs of your own machines.

   <Location /portal>   Header add Set-Cookie "rte=.%{BALANCER_WORKER_ROUTE}e; path=/portal; HttpOnly" env=BALANCER_ROUTE_CHANGED  Header edit Set-Cookie (.*) "$1; Secure" </Location>   <Proxy balancer://portalcluster>   BalancerMember ajp://CloudPortalNode1:20410 route=ps1  BalancerMember ajp://CloudPortalNode2:20410 route=ps2  </Proxy>   ProxyPass /portal balancer://portalcluster/portal stickysession=rte 

   If SSL is enabled on the proxy server, then add the below configuration to redirect all requests made over HTTP to HTTPS: 

   RewriteEngine On  RewriteCond %{HTTPS} off  RewriteRule ^/?(.*) https://%{SERVER_NAME}/$1 [R,L]  

  Recommended settings: These settings are to mitigate attacks pertaining to POODLE (Padding Oracle On Downgraded Legacy Encryption).

  You need to edit the Apache configuration located at /etc/httpd/conf.d/ssl.conf.

  1. Add the following line to your Apache configuration with other SSL directives.
     • For httpd version 2.2.23 and newer, specify all protocols except SSLv2 and SSLv3:

        SSLProtocol ALL -SSLv2 -SSLv3 

     • For httpd version 2.2.22 and older, only specify TLSv1. This is treated as a wildcard for all TLS versions:

        SSLProtocol TLSv1 

  2. Once done, restart your Apache HTTP Server:

      sudo service httpd restart 

  In order to check that the connection does not go through via SSLv3, run:

   openssl s_client -connect <ip-address>:<port> -ssl3 

• Add the following lines to configure CAS

   <Location /cas>    Header add Set-Cookie "rte=.%{BALANCER_WORKER_ROUTE}e; path=/cas; HttpOnly" env=BALANCER_ROUTE_CHANGED Header edit Set-Cookie (.*) "$1; Secure" </Location>   ProxyPass /cas ajp://CloudPortalNode:20410/cas  

• Add the following line to avoid CSRF related errors:

   ProxyPreserveHost on  

• If you modify the configuration later, such as to add more nodes, use this command to reload the configuration:

   # apachectl graceful or # service httpd restart 

  Note: If you front the Tomcat server with an Apache proxy, set the ProxyPreserveHost parameter to ON to avoid logon issues.

  Recommended settings: The KeepAlive parameter is set to ON in the /etc/httpd/conf/httpd.conf file.

• [Optional] Add the lines given below to enable compression of the response:

   SetOutputFilter DEFLATE  AddOutputFilterByType DEFLATE text/html text/css text/plain text/xml text/json application/x-javascript  

  It is recommended that you enable compression of response at reverse proxy server (web server). It improves the page load time.

Logging In

You should now be able to access CloudPortal from the Web browser. Go to http://<your IP or hostname>:8080/portal/. Use the following credentials to login:

User name: root

Password: Portal123#

Export invoice PDF

If there is a need to export the invoice pdf in Korean, Japanese, or Chinese languages, then install that particular language:

# yum install "@Japanese Support"

# yum install "@Korean Support"

# yum install "@Chinese Support"

Configuring LDAP

Refer to Integrating the Directory Server.