Web Front-end Architecture Overview HOPEX V2 EN
Contents
Deployment Types
Standalone Deployment
Horizontal scaling Deployment
Vertical scaling Deployment
Vertical scaling Deployment (detailed view)
Common deployment requirements
Web Client
Application Server
File Server
Database Server
Communication
Between Web Client and Web server (Web Application Server)
Between Environment SSP or MIK and Database server (Oracle, SQL Server)
Between Environment SSP or MIK and mail server
Between Environment SSP or MIK and file server (file access, license access)
Between Environment SSP and LDAP Server
Inside
Administration tools
Anti-virus Configuration
Authentication
Cluster, scalability and load balancing
Data access
Data storage
Document management
Error and trace logfiles
Full search and indexing
Licensing
Mail system
Multi-language
Physical backup
Redo logs and activity tracking
Regular administration tasks
Reporting
Security
Supervision
System caches
Services and running processes
FAQs
What about HTML browsers other than Edge, IE, Chrome and Firefox?
What is Mozilla Firefox ESR?
What is the list of minor restrictions for Edge / IE / Chrome / Firefox?
Is IE 9.0 still supported?
Is Windows Server 2008 R2 still supported?
Is Windows Server 2016 supported?
Is Oracle Database Server 11 still supported?
Is SQL Server 2008/2008 R2 still supported?
How can we guarantee high availability of the SSP Application Server?
Are there requirements or recommendations regarding security policies (GPOs)?
How to configure HTTPS?
It is possible to use a Must licence that is not located on the SSP Application Server?
Can the HOPEX web Front-End run on a web server other than IIS?
Can HOPEX solutions and products run on a mobile platform?
What are the web technologies used by HOPEX Platform?
What about other database servers?
What is the HOPEX2 folder?
Are there supervision tools?
Glossary
Web Front-End Installation Guide HOPEX V2 EN
Contents
Prerequisites
Operating System
.Net
Visual C++ Redistributable for Visual Studio 2015
Required roles
Desktop heap configuration
Configuration of SSL / TLS
Windows User(s) for MEGA HOPEX
Define Group permissions
Define MUST Licence Access
Define COM Access rights
MEGA HOPEX Setup
Choosing your setup type
Web Front-End Standalone Setup
Advanced Setup
Choice Screen
Advanced Parameters
Completing Installation
Define “Windows User for MEGA HOPEX” files Access Rights
Tune IIS
Configure Web Content expiration
Testing the Installation
Testing MEGA HOPEX Web Front-End
More required configuration
Word, Excel and PDF exports
Reports (MS Word)
Required options configuration
Allowing the use of verbose logs and activation
Registry update
Mega Server Supervisor: « verbose mode » activation
Disabling the verbose mode
What’s next?
Troubleshooting
Check that the Site Service Provider is running
Restarting Internet Information Services
Referencing a New Environment
Disabling Data Execution Prevention
Loosening Internet Explorer Security Settings
Windows Front-End Architecture Overview HOPEX V2 EN
Contents
Typical deployments
Standard Deployment
Citrix/TSE Deployment
Deployment requirements
Windows Client
File Server
Citrix Client/Remote Desktop Client
Application Server (Citrix Server/Terminal Server)
Database server
Communication
Between MIK and File Server (file access, license access)
Between Citrix client and Citrix Server
Between Citrix web client and Citrix Server
Between Remote Desktop Client and Remote Desktop Services
Between Remote Desktop Web Client and Remote Desktop Services
Between MIK and Database server (Oracle, SQL Server)
Between MIK and mail server
Between MIK and Document server (file access)
Between MIK and LDAP Server
Inside
Administration tools
Anti-virus Configuration
Authentication
Cluster, scalability and load balancing
Data access
Data storage
Document management
Error and trace logfiles
Licensing
Multi-language
Physical backup
Redo logs and activity tracking
Regular administration tasks
Reporting
Security
Services and running processes
Supervision
System caches
Technical documentation
FAQs
Is Windows 7.0 SP1 (32-bit or 64-bit) still supported?
Is Windows Server 2008 (32-bit or 64-bit) still supported?
Is Windows Server 2008 R2 still supported?
Is Citrix XenApp 6.x (6.0, 6.5) still supported?
Is Windows Server 2016 supported?
Is Oracle Database Server 11 still supported?
Is SQL Server 2008/2008 R2 still supported?
Is remote execution still possible?
Is .NET Framework required to install Windows Front-end?
Why is SMB 2.0 not supported for GBMS storage?
Can HOPEX Windows front-end run on Microsoft App-V?
Is GBMS storage recommended?
Glossary
Windows Front-End Installation Guide HOPEX V2 EN
Contents
Installation on stand-alone machine
General Steps
Installing on the Windows client
Post installation tests
Common configuration
Checking the HOPEX License
Creating a shared configuration folder
Copying the installation program on a network folder
Building an installation command line
Installing a test environment
Post installation scenarios
Installation on multiple machines
General Steps
Installing on the Windows client
Post installation tests
Installation in CITRIX/TSE Deployment
General Steps
Creating an installation package
Deploying a package on the server farm
Publishing the application
Post installation tests
Upgrading HOPEX Programs
Perform a backup of key configuration files
Upgrade command line
Removing HOPEX Programs
General recommendations
Unstallation command line
Uninstalling SQL Server Native client
FAQs
Why is it necessary to install a Visual C++ Redistributable package?
How to get the package Visual C++ Redistributable for Visual Studio 2015?
Why is it necessary to tinstall a Visual C++ Redistributable package?
How to track an installation error?
How to disable SMB 2.0?
How can I create a HOPEX Environment in RDBMS Storage (Oracle, SQL Server)?
After upgrade of a HOPEX installation from version X to version Y, when a user Z runs HOPEX, the version is version X (and not version Y)!
Glossary
Appendix
Recommended file permissions for the HOPEX installation
Reading table
Permissions for the license folder (Must license)
Permissions for the license folder (ELF license)
Permissions for the shared configuration folder
Permissions for HOPEX installation folders
Permissions for HOPEX Environment folders
Example of command lines for HOPEX Web Front-End
List of program features displayed in the setup wizard
Embedded Internet Explorer
Complete list of installation features
RDBMS Repository Installation Guide
Summary
Generalities
Supported Versions of RDBMS
Unsupported HOPEX Features in RDBMS Storage
Expected Advantages
Licensing
Infrastructure Requirements
RDBMS Client
Network Capability to Database Server
File Server and RDBMS local cache
Architecture Model
Database Server
Server disk size
Number of connections opened by HOPEX on the RDBMS for each HOPEX workstation
HOPEX RDBMS Diagnostic Utility
Purpose
How to run it
Oracle support
Oracle Database Requirements
Encoding
User privileges
Defining a HOPEX Oracle Connection
Creating an Environment
Creating a Repository
HOPEX Private Workspaces Cleanup
Installing the procedure
HOPEX Historical Data Cleanup
Before cleaning Historical Data
Installing the procedure
Batching Cleanup procedures for Oracle
Maintenance tasks
SQL Server support
SQL Server Requirements
Encoding
User management
Privileges for native account
Privileges for Windows accounts
Defining a HOPEX SQL Server Connection
Procedure with a native SQL account
Procedure when using Windows authentication
Creating an Environment
Creating a new SystemDb database
Using an existing SystemDb database
Creating a Repository
Creating a new SQL Server database
Using an existing SQL Server database
HOPEX Private Workspaces Cleanup
Installing the procedure
HOPEX Historical Data Cleanup
Before cleaning Historical Data
Installing the procedure
Batching Cleanup procedures for SQL Server
Maintenance tasks
HOPEX RDBMS repositories specific administration actions
Migrating Your Data from One Storage Support to Another
Restoring a HOPEX environment from formatted data
Restoring an environment (SystemDb repository)
Restoring a data repository
Handling of HOPEX RDBMS repositories specific internal format
ORACLE Case: From Test Environment to Production
The Chosen Method: Using the Data Pump Tool
How about HOPEX Then?
The Actual Export – Re-Import Phase
The Export
The Import
Finalization: Switching in HOPEX from Test to Production
What if…
Advice
Vocabulary
Appendix - FAQs
Is it possible to share user repositories and the SystemDb repository through user’s workgroups that do not share a file server?
Is it possible to have a user repository stored on a GBMS and a SystemDb repository stored on an Oracle/SQL server?
Is it possible to consult the data from an Oracle/SQL Server?
Is it possible to update the data from an Oracle/SQL Server?
Must License Installation Guide HOPEX V2 EN
Contents
Overview
Must license utility
User Interface
Select server path window
User management window
Select HOPEX installation window
Installation procedures
Communicating with MEGA Sales Administration
Choosing a machine to host the Must license folder
Creating a Must license folder
Sending the UNC address of the license folder
Installing a Must license file
Configuring the license folder in the HOPEX installation (direct reference)
Configuring the license folder in the shared configuration folder (indirect reference)
Uninstalling the Must license
Resetting the configuration files
Converting licence
Configure file permissions
Configuration and monitoring procedures
Configuring the command line (/RO /RW code)
Specifying a default licence
Declaring users
Adding a user to a license
Removing a user from a license
Configuring possible users of products
Setting a user as a possible user of a product
Removing a user as a possible user of a product
Cleaning up license tokens
Instant monitoring of license connections
Configuring several licensing modes
Configuration with concurrent mode (floating mode)
Check .Must licence
Enable extended mode in megasite.ini.
Configure command line
Configuration with dedicated mode
Check .Must licence
Enable extended mode in megasite.ini.
Configure command line
Inside
License deployment model
License execution
Windows Front-End
Web Front-End
File access
Connection process
Token distribution
Use case1: shared network licenses without configuration
Use case2: dedicated network licenses
Use case3: shared network licenses
Use case4: Windows Administration Console
Use case5: HOPEX Explorer
Use case5: configuration with several licensing modes
FAQs and Troubleshooting
Do I have to configure possible users?
How can I secure configuration of the HOPEX Must licence?
How can I prevent the dynamic declaration of possible users?
How can I get a log of license connections?
What is the Router.ini file?
How can I get the assignment of users to licenses?
How can I get the assignment of possible users to product?
When adding a user, I get an error 'Bad format with user 'XX'!
How can I get the list of logins of users?
I do not know the names of the logins. Why can't the utility provide a list of existing login?
How can I set possible users for a selection of users?
Can I mix shared and dedicated modes?
Is my license shared or dedicated?
Error message 1
Where is the latest license folder used saved?
How can I check that an HOPEX installation is part of a cluster
A message is displayed like You are not allowed to launch HOPEX V2 with your license file “xxxx.must”. It has to be upgraded for this version. Please contact your sales representative to obtain a valid license file.
How to migrate to HOPEX V2 EN
Contents
Main steps to migrate data to HOPEX V2
Prepare upgrade of data
Check metamodel, locks, workspaces and workflows
Decide format of report templates (MS Word)
Identify Solution packs used
Management of login assignments
Decide 'Definition of path of MetaAssociation'
Check licence
Upgrade data from HOPEX V1R2-V1R3
Check data upgrade pre-requisites
Upgrade environment with RDBMS storage (Oracle and SQL Server)
Upgrade environment with GBMS Storage
Running conversion tools
Update stored procedures
Complete upgrade of data
Re-import solutions packs
Review important options
Definition of path of MetaAssociation
Automatic Session Timeout
Risk modeling
MEGA Architecture modeling
Review command line parameters
Check format of report templates (MS Word)
Convert custom report templates (MS Word) to format RTF
Configure MS Word generation mode for each HOPEX environment
Check upgraded data
First control of migration
Check data modelling consistency
Other checking indications
Appendix
Conversion details
Utilities details
FAQs
Warning 'You cannot access repository "XXX". Its internal structure is not up to date. Run the menu "Technical Conversion" to perform the upgrade'
Warning 'The version of the stored procedure XX is not OK…'
Warning 'Writing access diagram is not compiled…'
How to Upgrade to CP HOPEX V2 EN
Contents
Foreword
Corrective Patch
Upgrading HOPEX programs
Upgrading Web Front-end
Upgrading Windows Front-end
Upgrading HOPEX Data
Upgrade HOPEX environments
Check Upgraded Data
Must licence conversion
Appendix
Advanced deployment
Documentation of Changes
FAQs
After a specific CP upgrade, I get the following warning: You cannot access repository "XX". Its internal structure is not up to date. Run the menu "Technical Conversion" to perform the upgrade?
I get a message 'MetaModel and/or technical data of your environement are not compiled (XXX is missing).... Please contact your administrator to perform the translation/compilation of your environment.
When running the menu 'Conversions > Environment automatic update', a warning says that transactions exist.
Why are CP provided as .EXE files from HOPEX?
The SSP Service (mgwspp.exe) keeps re-starting and therefore loads other processes (mgwspro.exe...).
What is the purpose of the menu 'Conversions > Environment automatic update > Simulate'?
Web Front-end Architecture Overview HOPEX V2 EN
FAQs