Understanding the database

Notes:
  • The Print Release tables are created automatically during installation.
  • It is not necessary to run the SQL scripts manually.

When using Microsoft SQL Server, make sure that:

  • The instance and database are created using the Microsoft SQL Server Management Console before running the installer.

  • The database account used when accessing the Print Release tables is a database owner.

Microsoft SQL Server and Firebird®

Firebird is the default system database that is bundled with LDD and it can also be used for LPM. Microsoft SQL Server can also be used as an alternate for Firebird. For Microsoft SQL Server, manually create the LPM database before launching the LPM Installer. During the installation, LPM populates the various LPM database properties files with the appropriate connection strings. It also automatically creates the LPM tables in the specified database. Depending on whether the installation is a non-serverless setup or a serverless setup, the data sources may vary. In a non-serverless setup, the same database is used for both LDD and LPM. In a serverless setup, Firebird is used for LDD, and Microsoft SQL Server is used for LPM.

Note: For Firebird, the tables are automatically put in the SOLUTIONSINFO database. For Microsoft SQL Server, we recommend using the customer name as the PRINTRELEASE database.

LPM references the following three database properties files:

  • <Install-Dir> \Lexmark\Solutions\apps\printrelease\WEB-INF\classes\database.properties—Contains the database configuration that is referenced by the PrintReleasev2 solution during execution.

  • <Install-Dir> \Lexmark\Solutions\apps\lpm\WEB-INF\classes\database-production-config.properties—Contains the database configuration for the LPM Admin Portal.

  • <Install-Dir> \Lexmark\Solutions\apps\idm\WEB-INF\classes\database-production-config.properties—Contains the database configuration for the Identity Management Service.

For example, the database configuration for the LPM Admin Portal, contains a default and secondary datasource section. In a non-serverless setup, the default and secondary datasources point to the same database. In a serverless setup, the default datasource points to the LPM Microsoft SQL database, and the secondary datasource points to the LDD Firebird database.

Database information

During installation, LPM determines database information from the backup files and pre-populates the fields with the data. Make sure that the information is correct. If a backup file is not available, then the fields are empty.

LPM supports the following:

  • Workgroup installation for LPM and LDD on Firebird

  • Serverless installation for LDD on Firebird and LPM on Microsoft SQL Server

  • Full LDD and LPM installation on Microsoft SQL Server

Note: In LPM version 2.7 or later, installation on the load balancer requires providing database information for use by the Lexmark Solutions Aggregator service.

Instance name

When using Microsoft SQL Server, you may specify an instance name for the Print Release database. If the instance name and port number are not specified, then the default instance and port number are used. If you have changed the port number, then specify it. The most common default port number is 1433.

To use a named instance, enter the name in the Instance Name field. Specifying a port number is optional. However, when specified, make sure that the port number is correct for the specified instance name.

Security type

When using Microsoft SQL Server, select Integrated Security to use Windows authentication or Microsoft SQL Server authentication. If you select Microsoft SQL Server, then provide the user name and password.

If you select Integrated Security, then you must run the LPM installer as a user with db_owner permissions to the database. Then you must enter the credentials in the Username and Password fields.

Note: When you select Integrated Security, any LPM services that communicate directly with the database are automatically configured to use these credentials.

Updating the password

When using Microsoft SQL Server authentication and Microsoft SQL Server is used only for LPM, then do the following:

  1. Using a text editor, open the following files:

    • apps\printrelease\WEB-INF\classes\database.properties

    • apps\idm\WEB-INF\classes\database-production-config.properties

    • apps\lpm\WEB-INF\classes\database-production-config.properties

    • apps\MFPAuth\WEB-INF\classes\database.properties

  2. Update the encrypted password using plain text:

    From:

    dataSource.password = ENC(TO86KjCYKsH7XoInQ1gj/gxj9390+C/g)

    To:

    dataSource.password = newpassword
    Note: The password is automatically encrypted after the Lexmark Solutions Application Server is restarted.

  3. Restart the Lexmark Solutions Application Server service.

  4. Using a text editor, open the services\lpm-reports-service\application.properties file.

  5. Update the encrypted password using plain text:

    From:

    dataSource.password = ENC(TO86KjCYKsH7XoInQ1gj/gxj9390+C/g)

    To:

    dataSource.password = newpassword

  6. Restart the Lexmark Reports Aggregator Service.

  7. Using a text editor, open the services\lpm-user-data-management-service\config\application.properties file.

  8. Update the encrypted password using plain text:

    From:

    dataSource.password = ENC(TO86KjCYKsH7XoInQ1gj/gxj9390+C/g)

    To:

    dataSource.password = newpassword

  9. Restart the Lexmark User Data Management Service.

When using Integrated Security authentication

  1. Navigate to the Services dialog.

  2. Locate the following:

    • Lexmark Solutions Application Server

    • Lexmark Solutions Apache Agent

    • Lexmark Reports Aggregator Service

  3. Right‑click the service, and then click the Log On tab.

  4. Make sure that This Account is selected, and then type your password.

  5. Click OK.