Installing Maintenix¶

The IFS Cloud installer installs the IFSApps database schema, IFS Cloud application, Maintenix application, and the Maintenix Reporting application.

The Maintenix and Maintenix Reporting database schemas are installed manually.

These are the high-level steps and information sources you use to install IFS Cloud and Maintenix:

Installing the co-deployed databases¶

You start by installing the IFSApp database schema using the IFS installer. See IFS Installation Guide for information on prerequisites and the IFS Build home that contains scripts and artifacts required for the installation.

Prepare servers. See Preparing Servers.
Read about how the installer works and about installing the IFSApps database with the dbinstaller action. See Deploying IFS Cloud.
Go to the <build_home location > ifsinstaller folder and edit the ifscloud-values.yaml file. Note the following:
- The values file also requires middle tier parameter values which you can provide now. See Installation Parameters, and note the Maintenix-specific tables, IFSMAINTENIXAPPSERVER and IFSMAINTENIXREPORTSERVER for the middle tier.
- Your edited values file must be referenced by the deployment.
Run the installer in the dbinstaller action mode with the following command to install the IFSApps database schema to the database server: Run the installer in the dbinstaller action mode. Follow the IFS Cloud DB deployment instructions here.

Below is an example of a command used to install the IFSApps database schema to the database server:
```
.\installer.cmd --set logFileLocation=<log file location> --values <yaml file location>/ifscloud-values.yaml --set action=dbInstaller --set dbInstaller.deliveryPath=<Build_Home location> --set dbInstaller.sysPassword=<DB sys pwd>
```
Install the version of the Maintenix Database Tools that corresponds with the IFS Cloud version you are using. See the Maintenix Database Installation Guide here.

mport Maintenix Schema Objects to the same database server that the IFSApps schema is installed on.

Required Oracle privileges for the SYSTEM user.

The installation scripts automatically grants the Maintenix database schema privileges to the Oracle SYS user and the SYSTEM user.

GRANT EXECUTE ON DBMS_LOCK TO SYSTEM WITH GRANT OPTION;
GRANT EXECUTE ON DBMS_SCHEDULER TO SYSTEM WITH GRANT OPTION;
GRANT SELECT ON sys.dba_pending_transactions TO SYSTEM WITH GRANT OPTION;
GRANT SELECT ON sys.pending_trans$ TO SYSTEM WITH GRANT OPTION;
GRANT SELECT ON sys.dba_2pc_pending TO SYSTEM WITH GRANT OPTION;
GRANT EXECUTE ON sys.dbms_xa TO SYSTEM WITH GRANT OPTION;

In addition, the installation script creates this user automatically, using the name you configure, and grants the user GRANT EXECUTE ON UTL_FILE TO ${username};

Edit the <DB_SCRIPTS_LOC>\install\build.properties file and fill out the following values

oracle.connect.host=<The host should be the DB server's IP address.>

oracle.connect.port=<Oracle db listener port>

oracle.connect.service=<Oracle db service name>

oracle system account information
system.username=
system.password=

oracle sys account information
sys.username=
sys.password=

maintenix.username=maintenix

maintenix.password=<This should be the value for 'ifscore.passwords.ifsmtxappPassword.data' set in the Installation Parameters*>

maintenix.import.filename=<File name of the Oracle Datapump Import file>

maintenix.import.directory=<This needs to be the Oracle Directory Object name, which has the property of a full path to where the above file is located on the DB server>

maintenix.database.id=<Database identifier (DBID) supplied by IFS, a customer can operate five production instances, each instance with a unique ID>

Save the file.
Execute the datapump-clean-user.bat script.
Check the log file for errors.

Import Jasper Schema Objects to the same database server that the IFSApps schema is installed on.

Edit the <DB_SCRIPTS_LOC>\install\jasper.properties file and fill out the following values

oracle.connect.host=<The host should be the DB server's IP address.>

oracle.connect.port=<Oracle db listener port>

oracle.connect.service=<Oracle db service name>

oracle system account information
system.username=
system.password=

oracle sys account information
sys.username=
sys.password=

jasper.username=jasper

jasper.password=<This should be the value for 'ifscore.passwords.ifsmtxreportPassword.data' as defined in the Installation Parameters*>

jasper.import.filename=<Likely JASPERSOFT-DATABASE.DMPX, but could be a customer generated name if they have exported their Jasper schema from an on-prem installation>

If they are using the default, they will need to move the file from the <DB_SCRIPTS_LOC>\export folder to the <DB server>

jasper.import.directory=<This needs to be the Oracle Directory Object name, which has the property of a full path to where the above file is located on the DB server>

Save the file.
Execute the datapump-clean-jasper-user.bat script.
The installation script creates this user automatically, using the name you configure, and grants the user GRANT EXECUTE ON UTL_FILE TO ${username};
Check the log file for errors.

In the Maintenix <database_install>/install folder, open and edit the co-deployed.properties file:

Section	Property	Default value and notes
Ifsapp account information	ifsapp.username	= No default set in properties file. This is the name of the IFSApps database schema user/owner. Set it to IFSAPP unless you specified a different name for this user in the ifscloud-values.yaml file for theifscore.users.ifsappUser.data parameter. The name used in this properties file must match the value used for the IFSApp database installation.
	ifsapp.password	= No default set in properties file. This is the password of the IFSApps database schema user/owner. Enter the same value that you specified in the ifscloud-values.yaml file for the dbInstaller.ifsappPassword parameter. The password used in this properties file must match the value used for the IFSApp database installation.
Common properties	ifs.codeployed.entity.sync.mode	= ASYNC Default value in properties file is the recommended setting.
	enforce.signatures	= TRUE Default in properties file is FALSE and must be FALSE to ensure that the value in the Maintenix database is set to false.

In the same location, run the codeployed-configure-schemas.bat script. This script applies the values you specified in the co-deployed.properties file.

Installing the middle tier¶

In IFS Cloud, when customers only use Maintenix, the following IFS Cloud platform containers should be enabled:

For IFS Cloud basic operations and Maintenix
ifsdbinit
ifsappproxy
ifsappiam 
ifsappclient
ifsappclientservices
ifsappodata
ifsmaintenix-appserver
ifs-maintenix-reportserver
ifsappdoc

If the customers use the IFS Cloud Mobile Maintenance solution as well, the additional IFS Cloud platform containers should be enabled:

ifsdbinit
ifsappproxy
ifsapp-iam 
ifsappclient
ifsappclientservices
ifsappclientnotification
ifsappodata
ifsmaintenix-appserver
ifs-maintenix-reportserver
ifsappnativeserver
ifsappnativeexecutor
ifsappconnect
ifsappsigningservice
ifsapprem
ifsappconnect
ifsappdoc
# Required for FSS 
ifsvirusscanner
ifsfilestorage

If you did not edit the ifscloud-values.yaml file in an earlier step to include the IFSMAINTENIXAPPSERVER and IFSMAINTENIXREPORTSERVER parameter values, you must do so now.

Go to the <build_home location > ifsinstaller folder and run the installer in the mtinstaller action mode with the following command to install the middle tier applications:

installer.cmd --set logFileLocation=<log file location> --values <yaml file location>/ifscloud-values.yaml --set action=mtinstaller

Note: Jaspersoft Report Server only supports IFS Maintenix in a single-server configuration. It does not support High Availability (HA).

Maintenix License Features¶

The Maintenix license file no longer manages license features, user quotas, aircraft quotas, or expiry data in IFS Cloud. Instead, Maintenix licensing in IFS Cloud follows the IFS Cloud licensing model. License features are generated and validated based on the selected Global Price List (GPL), which allows for the configuration of specific components. These components determine the Maintenix features activated within the solution set.