The installation file is downloaded to your workstation. Ensure you do not rename the installation file as it contains your registration information. Renaming the file will cause registration to fail after installation.
Refer to the Oracle Fusion Middleware System Requirements and Specifications document for your product, and download a suitable JDK from the following location, before you install the Fusion Middleware software:
Download free CaseAware current version
Virtual Memory: For a Windows based database server, be sure to either: set the page file size to be managed automatically by OS
or it should be at least 3 times the memory or RAM size for the machine.
Thus, you must have more than that much free disk space (at least 3 time the amount of memory or RAM) on the drive where the page file is defined to reside. 5. Database Server Setup The MIMM Application Server requires the connection to an existing Database server for metadata storage (metadata repository) However, a quick install for tests or QA purpose can be achieved by using the bundle PostgreSQL database. See the section Metadata Management (MIMM) Application Server Setup for more details. The following database setup scripts and instructions assume the following by default: Database Name: MM Database User: MM Database Password: = MM123! The database name and user name can be changed, and the password should of course be different. After the product is fully installed and web connectivity has been made, one may connect to a different database by way of the web based user interface at Tools -> Administration -> Database. 5.1 Database on Oracle Create a user MM and a database MM with the following privileges: sqlplus.exe SYS@ as SYSDBA -- Delete previous user and database if needed -- DROP USER MM CASCADE; CREATE USER MM IDENTIFIED BY MM123!; GRANT CONNECT TO MM; GRANT CREATE TABLE TO MM; GRANT CREATE VIEW TO MM; GRANT CREATE SEQUENCE TO MM; GRANT CREATE TRIGGER TO MM; GRANT CREATE PROCEDURE TO MM; GRANT CREATE TYPE TO MM; GRANT EXECUTE ON DBMS_LOB TO MM; -- If you get the error "Database exception occurred: ORA-01950: no privileges on tablespace 'USERS'" -- ALTER USER MM QUOTA UNLIMITED ON USERS; 5.2 Database on Microsoft SQL Server 5.2.1 Database Requirement 1 - Case InsensitiveThe database must be configured to interpret SQL in a case insensitive manner.
Furthermore, the upgrade process may take several hours (on large repositories) and also need extra space for temp data during the migration. Therefore make sure the database has at least 20% free space. Finally, it is also important to understand that the software installation directory (known as $MM_HOME in this document) also contains some critical application data and application setup customizations that have to be taken into account in your backup or upgrade process, including: postgresql/data which contains the actual PostgreSQL database data only on Windows and only when configured with the Setup utility (in the "Database Server" tab).
data which contains other application data, including: download/MIMB/ contains third party download software packages
files/mimb/ contains files for upgrade of MIMBWebServices
mm/analytics/ contains the generated analytics data files (new beta feature).
backups/ contains model backups for model comparison purpose.
operations/ contains the operation execution generated files such as a troubleshooting package or a backup ready to download. As these generated files can be very large, it is critical to execute the operation "Delete operation logs and files" either manually (MANAGE > Repository, right click on at the repository root) or automatically (MANAGE > Schedules).
sessions/ contains any temporary files for user login session.
tmp/ contains other temporary files.
logs/ for the log files tomcat and mimbmimb/ contains the model import/export bridge log files.
search/ contains the search query log files.
tomcat/ contains the tomcat log files
MIMB/cache/ contains bridge execution files organized as BridgeId/ImportId/mir_Version,nativeVersion
parameters/ contains bridge execution parameter files (only for some bridges like DI/ETL with runtime variables) organized as BridgeId/ImportId/Parameters
search/ contains the lucene search engine indexes (they will be automatically fully rebuilt from scratch if the folder is empty which will take a lot of time)
temp/ for any temporarily files (including from the mimb bridges)
webapps/ for application server (tomcat) cache
Remember that the actual location of this MIMM Application Server data directory can be configured with the Setup utility (in the "Application Server" tab). conf which contains the MM configuration / customizations organized as follows: conf.properties contains file containing most customizations defined with the Setup utility (in the "Application Server" tab)
ModelBridgeList.xml contains the list of enabled bridges and their names
resources/ directory containing any User Interface Customizations, in particular MM.properties and MetadataExplorer.xml.
Template/ contains the default template files of all the above files/directories, including a potentially new updated ModelBridgeList.xml or MetadataExplorer.xml after cumulative patches.
tomcat/conf with the tomcat.properties file containing the tomcat port and memory customizations defined the Setup utility in the "Application Server" tab, and the keystore file containing the tomcat SSL certificates defined with the Setup utility (in the "Application Server" tab).
jre/lib/security which also contains some SSL customizations defined with the Setup utility (in the "Application Server" tab). It is recommended to not reuse such directory, but rather reinstall the SSL keys with the Setup utility.
6.2.2 Upgrade Process We recommend the following upgrade process: Stop your MIMM application server in the same way it was started such as stopping the Windows services / Linux daemon, stopping the desktop command windows, or using the tomcat/bin/shutdown.Remove the application server service if one was created (Windows only).
Stop your MIMM database server and ONLY if you are using the bundled PostgreSQL database on Windows then use the $MM_HOME/Setup.sh utility to remove the Database Service as follows: Go to the Database Server tab, enable disable or uncheck the database service check box, and click on the Configure button.
Backup your MIMM data including your database and data file directories as explained above.
Backup your MIMM software by copying the $MM_HOME directory as $MM_HOME_OLD.
Install the complete MIMM new software (ONLY needed for clean install of a new version) by deleting the old $MM_HOME, and then creating a new one by unzipping the new MIMM full package.
Apply the latest MIMM software cumulative patch by unzipping it from inside the new $MM_HOME directory. WARNING 1: Make sure you unzip with overwrite on Windows, and use unzip -u on linux to update files while retaining permissions.
WARNING 2: You cannot use cumulative patches for major version upgrades, you must first start from a clean install of the new major GA version.
WARNING 3: You cannot reverse / unzip an older cumulative patch, you must restart from a clean install of the original GA version.
Restore your MIMM data and software customization/setup (ONLY needed for a clean install of a new version) by copying the appropriate files and directories (as previously explained) from $MM_HOME_OLD to $MM_HOME,including at least $MM_HOME/data and $MM_HOME/conf/conf.properties but possibly more as used and customized such as $MM_HOME/conf/resources, or $MM_HOME/tomcat/conf.
Integrate the MIMM new software features in your configuration by copying potential new versions of files from $MM_HOME/conf/Template into their matching directories in $MM_HOME/conf/. For example the new $MM_HOME/conf/ModelBridgeList.xml may contain some new or updated bridges. WARNING: if you had customized some files such as $MM_HOME/conf/resources/MM.properties, you must re-apply/merge such customization starting from the new version of that file copied Template. Reconfigure your MIMM Database Server (ONLY if you are using the bundled PostgreSQL database on Windows). As the PostgresSQL server software version may have changed and the database server needs to be upgraded. Therefore, you must:Execute the (old renamed installation) $MM_HOME_OLD/Setup.sh utility to restore the old Database Service as follows: Go to the Database Server tab, enable the database service check box, and click on the Configure button.
Execute the (new installation) $MM_HOME/Setup.sh utility as follows: go to the Database Server tab, enable the database service check box, and click on the Configure button.At this point the $MM_HOME/Setup.sh utility will retrieve the existing PostgreSQL data from the old install directory (which was already running as a service), will migrate them to the new install directory, and will remove the old PostgreSQL service, before starting the new PostgreSQL service on the new directory.
Restart your MIMM database server (ONLY if you are using the bundled PostgreSQL database on Windows).
Restart your MIMM application server after which your first login as Administrator may prompt you for an upgrade of your MM database.
Redo all above steps for any other MIMM Application server configured as MIMB harvesting agent.
Update your MIMM repository content (ONLY as needed) if the upgrade contains new and improved import bridges that would require to fully re-import the model (remove incremental harvesting in such case) and this will therefore require to re-build the related Configurations.
6.2.3 Version Specific Upgrade Issues and Recommendations Upgrading to a new version may have version specific issues or recommendations that are listed at the bottom of the release notes: see Release Changes for more details. 6.2.4 Upgrade and Migration Best PracticeThe following critical steps represent the best practice in MIMM Server upgrade or migration to a new machine (on prem or cloud)BackupAs with any migration / upgrade process, it is critical to backup the underlying data:the installation data and conf directories (see Understanding the Data Locations)
the repository database. (see Database Server Backup/Restore)
Repository CleanupOne of the most critical first step is to save disk space and speed up performance by performing a major cleanup of the repository:Apply the latest MIMM and MIMB Cumulative patches (in the MIMM Server and all MIMB Harvesting Agents).
Make sure that all Configurations are NOT on auto update.
Stop any scheduled operations, including all automatic metadata harvesting and database maintenance (MANAGE > Schedules).
Delete all unused / test Directories, Configurations, Models, Mappings, etc. (MANAGE > Repository).
Delete as many versions as possible (e.g. retaining the last few versions) of the remaining critical Configurations (MANAGE > Repository).
Delete unused model versions (MANAGE > Repository: Repository object > Operations > Delete unused versions).
Run the database maintenance to purge all deleted objects from the database (MANAGE > Schedules: Run Database Maintenance).Note that each database maintenance run purges deleted models for only 2 hours,therefore the database maintenance has to run as many times as needed until the log no long shows any models to delete.
Model ImportsIn order to avoid surprises after the upgrade/migration, it is critical to make sure that you started with a stable environment.The most important aspect of that is to make sure all imports are working before any upgrade because the source may no longer be available,may not have been imported with the latest version of the bridge, or may simply not have been imported for a long time.Apply the latest MIMM and MIMB Cumulative patches (in the MIMM Server and all MIMB Harvesting Agents).
Make sure that all Configurations are NOT on auto update.
Stop any scheduled operations, including all automatic metadata harvesting and database maintenance (MANAGE > Schedules).
Delete the model import cache in $MM_HOME/data/MIMB/cache).
Manual full import (no incremental harvesting) of all Models (one by one) with clear import cache and uncheck "Create new versions only when new import has changes".
Manual force build of all Configurations (one by one) with testing (connection stitching as needed for lineage).
Repository DatabaseIf the MIMM repository database server has to be migrated to a new machine (e.g. from on prem to cloud),make sure you follow the proper the proper database vendor process (see Database Server Backup/Restore).Note that the above process works well as long as you stay with the same database technology (e.g. PostgreSQL),but such database cannot be performed between database technologies, such as Oracle or SQL Server to PostgreSQLbecause the repository database implementations are different / optimized for each database technology.In such case, one can use the MIMM Application's Backup/Restore format (directories of XML files)but there are known limitations as some content is not back up in that format.Harvesting Agents If the MIMM Application Server has to be migrated to a new machine (e.g. from on prem to cloud),Make sure to reconnect each MIMB harvesting agents to the new MIMM Application Server.Note that such MIMB harvesting agents can remain on prem, while connecting to the new MIMM Application Server on cloud. 6.3 Application Server Execution and Initialization The easiest way to start the MIMM Application Server is to execute the $MM_HOME/RestartApplicationServer.sh utility. On Windows, you must "Run as administrator" the %MM_HOME%\RestartApplicationServer.bat utility. 2ff7e9595c
Comments