Flexera Software is changing hands again after Teachers’ Private Capital, the private investment department of the Ontario Teachers’ Pension Plan, has agreed to acquire a majority stake in Flexera Software from Thoma Bravo, LLC.
Flexera is the manufacture of the FLEXnet software also known as FLEXlm.
About three years ago Thoma Bravo, LLC acquired it from Macrovision, as we published in OpenLM website.
ESRI solved this issue in Data Interoperability Extension for ArcGIS 10 Service Pack 2 published this week. Please install the patch on your earliest convenience.
OpenLM Server uses Firebird Embedded Server by default. By purchasing the External DB support extension, the user is licensed to use external DB such as Oracle, MS SQL Server or Firebird Server.
This document describes a backup procedure to OpenLM Server. The suggested backup procedure must be tuned in order to accommodate different computing environments.
This article only describes a procedure for cold backup. This method requires the system to be halted in order to assure a consistent backup file.
Hot backup is recommended for critical systems and requires the support of a professional DBA. This configuration will not be discussed in this article.
OpenLM uses an embedded DB by default. The database file is located by default in C:\Program Files\OpenLM\OpenLM Server\db\. The DB file name is OPENLM_DB.GDB or OPENLM_DB.FDB in new versions.
OpenLM Server supports external databases such as Oracle, MS SQL Server, MySQL or Firebird Server. When using external DB, the backup is done using the DB tools, usually by a DBA.
A script that implements the backup including stopping the service is recommended.
Tesera Systems OpenLM WhitePaper
Tesera Systems – a customer of OpenLM has implemented an advanced cloud based computing & licensing system. FLEXlm (FLEXnet) licensed software such an ESRI Desktop software (ArcInfo, ArcEditor & ArcView) and Safe FME software is used by cloud instances or end user workstations over the cloud. The licensing system is managed and enhanced by OpenLM software ensuring the high availability and effective usage of licenses.
Tesera Systems is an employee-owned company that provides a wide range of quality services related to resource planning, analysis, information systems and environmental management. Our innovative IT and collaboration and infrastructure allow us to effectively manage and operate high performing distributed teams (required to provide the best solution). Tesera has branch offices throughout western Canada, specifically: Victoria, Penticton, and Prince George (British Columbia) and Cochrane, and Calgary (Alberta). Tesera’s staff have access to virtual desktops and secure, redundant and centralized data storage allowing them to operate as though they were in the office regardless of where they work from.
General
The purpose of OpenLM Data Migration Tool is to allow OpenLM customers to transfer OpenLM information between different databases. The tool supports four types of databases and allows the migration of OpenLM information between them.
For elaborate examples of the Database migration tool’s functionality, please refer to these documents:
Application note 1008: OpenLM database migration, from Firebird 1.7 to MS-SQL 1.7
Application Note 2008a: OpenLM database migration, from Firebird 1.7 to MS-SQL 1.8
Application Note 2008b: OpenLM database migration, from Firebird 1.7 to Oracle 1.8
Supported databases: Oracle, MS SQL Server, Firebird Server, Firebird embedded (OpenLM default storage).
System requirements: Microsoft Windows XP, Vista, Server 2003, Server 2008. Microsoft .NET Framework 3.5.
How to get it? Contact OpenLM sales department sales@openlm.com.
Installation: Install OpenLM Data Migration Tool using the supplied EXE file.
Preparations
Prepare the source database:
Prepare the destination database:
Operation
Launch the tool from Start->All Programs->OpenLM Data Migration tool
We will demonstrate the operation by doing an Embedded Firebird (Default OpenLM DB) to MS SQL Server migration.
Select the Firebird database by clicking the radio button. A dialog will open:
Select the database file from the disk (*.GDB), use OpenLM username and password and mark the embedded check box (Contact OpenLM support for full connection string).
Then click OK, the tool will try to connect to the database and will pop a message with the connection status.
Then specify the destination database type. In this example – MS SQL Server:
In this example we used the “Integrated Security” option (for using “Windows Authentication”). If you use “SQL Server Authentication”, uncheck the “Integrated Security” and enter UserID and Password. After clicking “Test Connection”, the application will populate the Databases combo box. Select the destination database from the list and click OK. OpenLM will pop a message that will indicate if the application managed to connect to the database.
After that, click “Transfer”. The application will transfer all the information from the source database to the destination database.
After the data was migrated, use OpenLM configuration form to set OpenLM Server to use your new database.
follow: RSS
