/
Infiterra OSS Installation

Infiterra OSS Installation

Infiterra platform - Infiterra OSS

Deployment Guide


Table of Contents



1. Document Revision History


For information about all the latest releases and updates on Infiterra platform, please visit http://kb.infiterra.com/display/ICPD/Release+Notes


2. About this Guide



This guide provides instructions that will assist you to install Infiterra OSS v2.x or higher

This guide will be regularly updated as soon as new information becomes available.


2.1. Document Conventions


Throughout this guide, specific fonts and styles are used to identify user input, computer code, and user interface elements. The following table lists conventions used in this guide.

Convention

Usage

Bold text, Arial font

Used for information you type as well as path names, file names, menus, and command keys.

Italic text, Arial font

Used for column names, field names, window names.

Bold, italic text enclosed in angle brackets

Used for variables you replace with the appropriate information.

Normal text, Courier New

Used for system messages, screen text, and code examples.

Table 1. Document conventions



3. Overview of Infiterra OSS Components


See also:



By using Infiterra OSS related components you can provide services such as Microsoft Exchange, Blackberry, Office Communications, Windows SharePoint Services and Foundation, Lync, Dynamic CRM and Web Hosting.This chapter gives us an overview of Infiterra OSS related components, servers, and services. 


Infiterra OSS platform is a centralized software application that simplifies the daily burden of the activation, configuration and management of a service provider's unified communication and collaboration infrastructure. Infiterra OSS enables service providers to centrally create, control, and deliver hosted IP and application services. It addresses critical operational challenges for provisioning, monitoring, metering, self-management, authentication and further integration into other applications in the service provider's OSS/BSS systems.


Infiterra OSS has the following components:


Infiterra OSS Provisioning Portal

It's a server that hosts the web-based control panels. Service providers can have multiple Provisioning Portal servers to balance loads and provisioning requests. Provisioning Portal servers or control panels provide easy access to task's accomplishment. These control panels enable service providers, resellers, organization administrators and users, to manage their accounts, resources, and other system settings. Provisioning Portal servers are typically placed in the Front End (internet facing) network.


Infiterra OSS Orchestration Server

The Infiterra OSS Orchestration Server coordinates the provisioning of services to customers. Service Providers can have multiple Orchestration servers to balance loads and provisioning requests. The Orchestration Server role comprises the business logic of the Infiterra OSS. Orchestration servers are typically placed in the Back End network.


Infiterra OSS Service Managers

Infiterra OSS Service Managers can be considered as provisioning assistant servers. Service Managers provide an extensive set of web services APIs that perform the actual provisioning actions as dictated by the Orchestration Servers. Service Managers are mainly installed on servers that host specific applications or services (e.g.: IIS, SQL Server), but they can also be installed on servers that have special tools to manage and control other applications or services (e.g.: Exchange servers, Lync servers, etc.). Infiterra OSS Service Managers are typically placed in the Back End network.


4. Preparing for the Installation


See also:



This chapter explains how to prepare a hosting environment for the Infiterra OSS installation.


4.1. General Server Requirements


To install Infiterra OSS platform you need to obtain the following servers:


  • An Active Directory server

    Note: Active Directory is only required if you will be providing any of the following applications as a hosted service
     

    • Exchange Server 2007/2010/2013
    • Blackberry Enterprise Server 5
    • Office Communications Server 2007 R2
    • Lync 2010/2013
    • Windows SharePoint Services 3.0
    • SharePoint Foundation 2010/2013
    • Dynamics CRM 4.0
  • A Microsoft SQL server (or cluster of Microsoft SQL servers)
  • Orchestration servers (one or more)
  • Provisioning Portal servers (one or more)
  • Service Manager servers (one or more)



Each of these servers should meet the general minimum requirements shown in the following table:

Hardware

Networking

Software

CPU: Pentium®IV 2 GHz or faster

Memory: At least 2 GB of RAM

Hard disk space: At least 40 GB

(unless otherwise specified)

At least one network adapter 100/1000 Mbps

At least one static IP address

(DHCP IP address scheme is not supported)

OS: Windows Server 2008 or

Windows Server 2008 R2 or

Windows Server 2012 or

Windows Server 2012 R2

Microsoft .Net Framework 4.0/4.5

Table 2. General server requirements


Any edition of the operating systems listed above is supported. Both 32-bit and 64-bit are supported. Microsoft Internet Information Services (IIS) version 7.x/8.x or higher must be installed on every server where the Infiterra OSS components will be installed. Microsoft SQL Server is required in order to host the internal Infiterra OSS database.


Before installation the operating system should be up to date with latest updates. Before deploying Infiterra BSS, follow the guide below in order to properly prepare your Windows Server Infrastructure:


The Infiterra OSS database can be installed on any of the following versions of SQL Server:

  • SQL Server 2008 Express edition or higher
  • SQL Server 2008 R2 Express edition or higher
  • SQL Server 2012 Express edition or higher
  • SQL Server 2014 Express edition or higher


The SQL Server Express edition is free. You can download the latest version from the following link: http://www.microsoft.com/express/sql/download/ .
Infiterra OSS components can be installed on a dedicated physical server or on a virtual machine hosted in one of the following virtualization environments:

  • Microsoft Hyper-V
  • KVM
  • Virtuozzo
  • VMware
  • XenServer


In order to access the web site pages of Infiterra OSS Components, all the latest versions of Web Browsers (Internet Explorer, Mozilla Firefox, Google Chrome, Opera, Safari etc.) are supported.


Important Notes:

  • You must have administrative access (either local or via Remote Desktop) to manage the servers, including permissions to install and configure server software, to check system logs, etc.
  • If you are planning to host and manage DNS and mail software on the same server, you should have at least two dedicated IP addresses that point to your server. In case you install and configure everything using only one IP address you'll get incorrect DNS zones and mail exchange records.
  • All servers must be connected to the Internet so that you are able to install and configure Infiterra OSS components.


4.2. Network and Domain Requirements


All network parameters will have to be configured correctly prior to installing Infiterra OSS components. These parameters include:

  • Static IP addresses for all servers that either host applications or will be used to host Infiterra OSS components.
  • Network Subnet masks
  • Default gateways
  • DNS settings


Firewall settings must be configured to allow all the servers where the Infiterra OSS components will be installed to access the following server: downloads.infiterra.com. The servers must be able to connect to this server through TCP ports 80 and 443.



5. Installing Infiterra OSS


See also:



This chapter explains how to install the individual components of Infiterra OSS.


5.1. Infiterra platform Installer


Cloud Platform Installer is the application that is responsible for installing and upgrading Infiterra OSS components. Cloud Platform Installer's main function is to connect to Infiterra platform update server in order to retrieve the latest installation packages for every available component and initiate the installation package in order to install or upgrade a specific component. In addition, Cloud Platform Installer can be used to change basic configuration settings of all the installed components on a server.


1) In order to install any Infiterra OSS component you must first install Infiterra platform Installer on the server. You can download Infiterra platform Installer installation package by clicking the button below: 



   

Fig 1. Downloading Infiterra platform Installer


Note: Infiterra platform Installer needs to be installed on every server that will host at least one Infiterra OSS component.



2) Once the download is completed, run the Infiterra platform Installer installation package to install the application on the server.

Fig 2. Running Infiterra platform Installer


Fig 3. Infiterra platform Installer Welcome page


Fig 4. Selecting Installation Folder


Fig 5. Confirming Installation


     Fig 6. Infiterra platform Installer has been successfully installed



3) Once the Infiterra platform Installer installation is completed, double click on Cloud Platform Installer shortcut on the server desktop to launch the installer.

Fig 7. Launching the Cloud Platform Installer



4) Click on View Available Components.

Fig 8. Viewing Infiterra OSS Available Components


Note: You must run the Cloud Platform Installer application as an administrator. In case the application doesn't open after double clicking on the shortcut, launch Windows Explorer, locate Cloud360.Installer.exe program, right-click on Properties, then click on Compatibility and check the Run this program as an administrator checkbox.



5.2. Installing Infiterra OSS Orchestration Server



5) In order to install Infiterra OSS Orchestration server launch Infiterra Platform Installer, click on View Available Components button and then click on the Install button next to Infiterra OSS Orchestration server.

Fig 9. Installing Infiterra OSS Orchestration Server


Fig 10. Setup Wizard is loading



6) Click on Next to proceed to Infiterra OSS Orchestration Server Setup Wizard.

  Fig 11.Infiterra OSS Orchestration Server Setup Wizard



7) Click on I Agree to accept the license terms of the product.

Fig 12. Accepting license terms



8) The Infiterra OSS Orchestration Server setup wizard will check if the minimum system requirements are met and will activate the Next button upon successful validation. Click on Next to continue.

Fig 13. Prerequisites Check



9) Select the Destination Folder by clicking on Browse or leave the default path and click on Next.

  Fig 14. Selecting Destination Folder



10) Specify the setting of the Infiterra OSS Orchestration Server Web Site. If you are not going to provide Orchestration server to external clients (3rd-party applications consuming Orchestration Server web services) and if you are going to install Infiterra OSS Provisioning Portal on the same server, it is strongly recommended to keep 127.0.0.1 as the web site IP address and 9002 as the default TCP port; otherwise you should select a different static IP address (either private or public) and – optionally – a different TCP port for the Orchestration Server web site. Once you specify the Web Settings, click on Next

Fig 15. Specifying Web Settings



11) The Security Settings Setup Wizard page allows you to specify a user account that will act as the Orchestration Server web site anonymous access and application pool identity (for IIS 7.x). The setup wizard will provide an auto-generated password for this account, specified in the Password and Confirm Password fields. Change the password value only if you are going to manually modify the web site or application pool settings after the Orchestration Server installation. If you are installing Infiterra OSS Orchestration server in an Active Directory environment, you have the option to check Create Active Directory account; otherwise a local Windows (SAM) account will be created. Once you specify the Security Settings, click on Next


   Fig 16. Specifying Security Settings


Note: The Infiterra OSS Orchestration server application pool should run under a user account without administrative privileges. By default, Infiterra OSS Orchestration Server installation creates an account which is a member of the "IIS_IUSRS" (for IIS 7.x) group only. As a best security practice, it is recommended to create a local user account for the Infiterra OSS Orchestration server.



12) In the Database Settings page, enter an existing SQL Server Express Edition (2008, 2008 R2, 2012, 2014) instance name in the SQL Server field. Select either Windows Authentication or SQL Authentication and provide a valid database name for the new Infiterra OSS Database that will be created. Once you specify the Database Settings, click on Next

Fig 17. Specifying Database Settings


Note: Database settings which are specified in the Database Settings setup wizard page, will also be used during future Infiterra OSS components upgrades, so make sure they can be used in the future in order to access the specified SQL server instance.


13) Specify a password for the serveradmin account. The serveradmin is the root administrative account you will use to access the Infiterra OSS Provisioning Portal and manage your hosting environment. Click on Next to start the installation of the Infiterra OSS Orchestration server.

    Fig 18. Specifying Administrator Password


    Fig 19. Installing Infiterra OSS Orchestration Server


14) When the installation is completed, click on Next to continue.

     Fig 20. Installation is completed



 15) Once the Orchestration Server setup is completed, you will receive the following page:

Fig 21. Setup completion page



5.2.1. Infiterra OSS Orchestration Server Post Deployment Test



16) In order to verify that the installation was successful, enter the Orchestration Server URL in a web browser.

Fig 22. Installation was successful



5.3. Installing Infiterra OSS Provisioning Portal


In the Standalone Deployment Scenario, Infiterra OSS Provisioning Portal and Infiterra OSS Orchestration Server are installed on the same server. In the Distributed Deployment Scenario, Infiterra OSS Provisioning Portal and Infiterra OSS Orchestration Server are installed on separate servers. In the Highly Available Deployment Scenario, each of Infiterra OSS Provisioning Portal and Infiterra OSS Orchestration Server, are installed on two (2) separate servers.


17) In order to install Infiterra OSS Provisioning Portal, launch the Infiterra platform Installer on a server, click on the View Available Components button and then click on the Install button next to Infiterra OSS Provisioning Portal.

Fig 23. Installing Infiterra OSS Provisioning Portal


Fig 24. Setup Wizard is loading


18) Click on Next to proceed to Infiterra OSS Provisioning Portal Setup Wizard.

  Fig 25. Infiterra OSS Provisioning Portal Setup Wizard



19) Click on I Agree to accept the license terms of the product.

Fig 26. Accepting license terms



20) The Infiterra OSS Provisioning Portal Setup Wizard will check if the minimum system requirements are met and will activate the Next button upon successful validation. Click on Next to continue.

Fig 27. Prerequisites Check



21) Specify the Destination Folder by clicking on Browse or leave the default path and click on Next.


Fig 28. Selecting Destination Folder



22) Specify the settings of the Infiterra OSS Provisioning Portal Web Site. The URL shown on this page will be used to access the control panel. Once you specify the Web Settings, click on Next to continue.

     Fig 29. Specifying Web Settings



 Important:

  • If you specify a host name, make sure that there is an appropriate A record in your DNS servers, pointing to the IP address entered above.
  • Ensure that there is a firewall rule, allowing incoming TCP traffic to the port you specified above.




23) The Security Settings setup wizard page allows you to specify a user account that will act as the Provisioning Portal web site anonymous access and application pool identity (for IIS 7.x). The setup wizard will provide an auto-generated password for this account, specified in the Password and Confirm Password fields. Change the password value only if you are going to manually modify the web site or application pool settings after the Provisioning Portal installation. If you are installing Infiterra OSS Provisioning Portal in an Active Directory environment, you have the option to check Create Active Directory account; otherwise a local Windows (SAM) account will be created. Once you specify the Security Settings, click on Next.

Fig 30. Specifying Security Settings


Note: The Infiterra OSS Provisioning Portal application pool should run under a user account without administrative privileges. By default, Infiterra OSS Provisioning Portal installation creates an account which is a member of the "IIS_IUSRS" (for IIS 7.x) group only. As a best security practice, it is recommended to create a local user account for the Infiterra OSS Provisioning Portal.



24) Enter the Orchestration Server URL. This is the URL that was specified during the installation of the Infiterra OSS Orchestration server. Click on Next to start the installation of the Infiterra OSS Provisioning Portal. 


  Fig 31. Specifying Orchestration Server URL


Important: Infiterra OSS Provisioning Portal depends on Infiterra OSS Orchestration Server. Make sure that the URL of the Orchestration Server is accessible from the Provisioning Portal server.



25) When the installation is completed, click on Next to continue.

    Fig 32. Installation is completed



26) Once the Provisioning Portal installation is completed, you will receive the following page:

Fig 33. Setup Completion Page



5.3.1. Infiterra OSS Provisioning Portal Post Deployment Test



27) To verify that the installation was successful, enter the Provisioning Portal URL in a web browser. In order to sign in, enter serveradmin and <serveradmin_password>, where <serveradmin_password> is the password you provided for the serveradmin account during  the Infiterra OSS Orchestration Server installation (step 13).

Fig 34. Signing In upon successful installation


Fig 35. Infiterra OSS Provisioning Portal Welcome Page



5.3.2. SSL encryption and SSL Certificates considerations



Cloud Platform Installer currently does not support the automatic configuration of SSL encryption during the installation of any Infiterra OSS Component. The Service Providers are responsible to complete all the necessary actions in order to configure SSL encryption as they see fit. Such actions would include the purchase of an adequate standard or wildcard SSL certificate from an external Certification Authority (CA), the installation of the SSL certificate on the servers and the re-configuration of the web site bindings on the Web Server (IIS) for the specific web application (i.e. provisioning portal web site).


 If -after the installation of the Infiterra OSS Provisioning Portal component - SSL encryption for the provisioning portal is configured by the Service Provider administrator, then in order to access Infiterra OSS Provisioning Portal, you must modify the configuration file (web.config file) of the Infiterra OSS Provisioning Portal web application, which is located at the installation folder of the application, as follows:


Search for the lines that start with the following tags:


   <pages theme="Default" validateRequest=

   <forms name=".WEBSITEPANELPORTALAUTHASPX" protection=


and replace them with the following entries, respectively:


   <pages theme="Default" validateRequest="false" controlRenderingCompatibilityVersion="3.5" clientIDMode="AutoID" enableViewStateMac = "true" viewStateEncryptionMode = "Always">

   <forms name=".WEBSITEPANELPORTALAUTHASPX" protection="All" timeout="30" path="/" requireSSL="true" slidingExpiration="false" cookieless="UseDeviceProfile" domain="" enableCrossAppRedirects="false" >



5.4. Installing Infiterra OSS Service Managers


28) In order to install the Infiterra OSS Service Managers, launch the Infiterra platform Installer, click on the View Available Components button and then click on the Install button next to Infiterra OSS Service Managers.

Fig 36. Installing Infiterra OSS Service Managers



Fig 37. Setup Wizard is loading


29) Click on Next to proceed to Infiterra OSS Service Managers Setup Wizard.

  Fig 38. Infiterra OSS Service Managers Setup Wizard



30) Click on I Agree to accept the license terms of the product.

Fig 39. Accepting license terms



31) The Infiterra OSS Service Managers Setup Wizard will check if the minimum system requirements are met and will activate the Next button upon successful validation. Click on Next to continue.

Fig 40. Prerequisites Check



32) Specify the Destination Folder by clicking on Browse or leave the default path and click on Next.

Fig 41. Selecting Destination Folder



33) Specify the settings of Infiterra OSS Service Managers Web Site. Once you specify the Web Settings, click on Next to continue. 

Fig 42. Specifying Web Settings


Important:

  • If you specify a host name, make sure that there is an appropriate A record in your DNS servers pointing to the IP address entered above.
  • Ensure that there is a firewall rule allowing incoming TCP traffic to the port you specified above.



34) The Security Settings setup wizard page allows you to specify a user account that will act as the Service Managers web site anonymous access and application pool identity (for IIS 7.x). The setup wizard will provide an auto-generated password for this account, specified in the Password and Confirm Password fields. Change the password value only if you are going to manually modify the web site or application pool settings after the Service Managers installation. If you are installing Infiterra OSS Service Managers in an Active Directory environment, you have the option to check Create Active Directory account; otherwise a local Windows (SAM) account will be created. Once you specify the Security Settings, click on Next to continue. 

Fig 43. Specifying Security Settings



Note: The Infiterra OSS Service Managers application pool must run under a "privileged" user account. By default, Infiterra OSS Service Managers installation creates an account which is a member of the "IIS_IUSRS" (for IIS 7.x) group, and also a member of the local Administrators security group and a member of Domain Admins security group (if Create Active Directory Account is checked).



35) Specify a password for the Service Managers server. You will use this password to access this Server from the Enterprise Server Component. Once you specify the password, click on Next to start the installation of the Infiterra OSS Service Managers.


Note: This password will be used later on during the configuration of the Service Managers in Infiterra OSS Provisioning Portal, so make sure you remember it.


Fig 44. Specifying Server Password



Fig 45. Installing Infiterra OSS Service Managers



36) When the installation is completed, click on Next to continue.

     Fig 46. Installation is completed



 37) Once the Service Managers setup is completed, you will receive the following page:

Fig 47. Setup completion page



5.4.1. Infiterra OSS Service Manager Post Deployment Test



38) In order to verify that the installation was successful, enter the Service Manager URL in a web browser.

Fig 48. Installation was successful




6. Configuring Infiterra OSS Components Settings


See also:



This chapter provides information about modifying the basic configuration settings of Infiterra OSS components, subsequent to their installation.


6.1. Modifying Infiterra OSS Web Site Settings


39) In order to modify the Web Site Settings (host name, listening IP address and port) for any Infiterra OSS component, launch Infiterra platform Installer and click on the desired component of the navigation tree in the left pane. Click on Settings on the component properties page in the right pane.  

Fig 49. Modifying Web Site Settings


40) The Setup Wizard for the corresponding Infiterra OSS component will launch.

  Fig 50. Setup Wizard is launching



41) Specify the new desired settings. Click on Next to save changes and continue. Skip all the rest of the steps until the end of the Setup Wizard (just click on Next in the rest of the wizard pages).

   Fig 51. Modifying Web Settings


Important: Modifying the URL of the Orchestration Server in Infiterra OSS Provisioning Portal settings, will not function correctly without a valid Orchestration Server URL. If you have changed the URL of the Orchestration Server, you must also change the corresponding Provisioning Portal settings so that they reflect those changes. In order to change the Orchestration Server URL in Provisioning Portal settings, launch the Infiterra platform Installer, click on Infiterra OSS Provisioning Portal in the navigation tree on the left and then click on Settings in the right pane of the Component Properties page. Skip all the rest of the steps in the Setup Wizard by clicking on Next, until you reach the Orchestration Server URL settings page. Specify the desired value of the Orchestration Server URL and click on Next until the Setup Wizard completes.



6.2. Modifying Orchestration server serveradmin password



42) In order to reset the password of the Serveradmin account, launch the Infiterra platform Installer and click on OSS Orchestration server in the navigation tree on the left. Click on Settings on the Component Properties page in the right pane, in order to launch the Setup Wizard.

    Fig 52. Modifying serveradmin password


43) The Setup Wizard for the corresponding Infiterra OSS component will launch.

  Fig 53. Setup Wizard is launching



44) Click on Next in order to skip the Web Settings page.

Fig 54. Skipping Web Setting page


 


45) On the Set Administrator Password page, check Reset Serveradmin Password, and then specify the new password. Click on Next to save changes and continue.

Fig 55. Resetting Serveradmin Password



46) Click on Next to continue.

Fig 56. Setup is completed



47) You have successfully reset Serveradmin Password.

   Fig 57. Serveradmin password is updated



6.3. Modifying Server Access Password



If you are trying to register a new Infiterra OSS Service Manager instance on the Provisioning Portal server's configuration page, and you forgot the password set during Infiterra OSS Service Manager installation, you can reset it using the Infiterra platform Installer.


48) In order to reset the server access password, launch Infiterra platform Installer on the server where the Infiterra OSS Service Manager component is installed and click on Infiterra OSS Service Managers in the navigation tree on the left. Click on Settings on the component properties page in the right pane.

Fig 58. Modifying Server Access Password


 

49) Click on Next in order to skip the Web Settings page.

Fig 59. Skipping Web Setting page



50) On the Set Server Password Setup Wizard page, check Reset Server Password and then specify the new password. Click on Next to save changes.

Fig 60. Resetting Server Password



51) Click on Next to continue.

Fig 61. Setup is completed



52) You have successfully reset Server Password.

   Fig 62. Server password is updated


 

7. Upgrading Infiterra OSS Components


See also:



This chapter provides information about upgrading existing Infiterra OSS components.


53) If you want to upgrade any Infiterra OSS component, launch Infiterra platform Installer, select the desired component in the navigation tree on the left and then click on the Check For Updates button on the Properties page in the right pane.

Fig 63. Checking for Updates



54) If there are no available updates, the following window will pop up. Click on OK to close the window. If there are available updates, click on Yes to download and launch the Update Setup Wizard. Follow the wizard's instructions to complete the upgrade operation.

  

Fig 64. Closing the pop-up window


Note: The Infiterra platform Installer will upgrade the Infiterra OSS components to the next available version based on the currently installed version of the corresponding component. This means that, if for example the currently installed version of a component is 2.1.0 and versions 2.1.1 and 2.1.2 were released after that version, the installer will upgrade the component to version 2.1.1 first. To install the latest version you will have to check for updates and perform the upgrade operation again.







8. Uninstalling Infiterra OSS Components


See also:



This chapter provides information on how to uninstall Infiterra OSS Components.



55) Launch Infiterra platform Installer. Select the component you want to uninstall from the navigation tree on the left and click on Uninstall.

Fig 65. Uninstalling Infiterra OSS Components



56) Follow the Setup Wizard instructions to uninstall the selected component. 

Fig 66. Setup Wizard is launching



57) Click on Next to continue. 

Fig 67. Setup Wizard welcome page



58) Click on Next in order to uninstall the selected Infiterra OSS Component. Repeat the same procedure for all the Infiterra OSS components you wish to uninstall.

Fig 68. Uninstalling the selected Infiterra OSS Component




9. APPENDIX: Troubleshooting


See also:



This appendix provides information that will help you troubleshoot installation issues with Infiterra OSS platform.


9.1. Troubleshooting Installation Issues


ISSUE 1

Could not start Infiterra platform Installer on Windows 2008


Answer:

This might occur due to enabled User Account Control (UAC). As a solution, you could disable UAC or run Infiterra platform Installer in "elevated" mode by right clicking its shortcut and selecting "Run as Administrator".



ISSUE 2

Viewing Infiterra platform Installer Error Log


Answer:

To view the Infiterra platform Installer application log, click on Application Settings in the navigation tree on the left and then click on View System Log. The Infiterra platform Installer log file will be opened with the default editor application (e.g.: Notepad).

   

Fig 69. Viewing System Log                                                                        Fig 70. Infiterra platform Installer log file



ISSUE 3

Switching ASP.NET to 32-bit mode on Windows 2008 x64


Answer:

a) Launch Internet Information Services management console.

b) Click on Application Pools in the navigation tree on the left and then open the Advanced Settings dialog of the Infiterra OSS Service Manager Pool.

c) Set the Enable 32-bit Applications value to True and click on OK to save changes.


9.2. Troubleshooting Upgrade Issues


If you experience any issues right after an Infiterra OSS Component upgrade, try the following basic troubleshooting steps:

a) Make sure all Infiterra OSS components were upgraded to the same version.

b) Reset Infiterra OSS components application pools in IIS Manager


See also:

Related content