When viewing the server status, a table is shown with information about each server in the system. The Status column indicates whether the server is online, offline, or has a communication problem. A yellow exclamation mark appears beside the status when the server is offline, and a red X appears to indicate a communication problem.
A green arrow beside the server address indicates the server that hosts the LMC session.
From LMC, click the System tab.
From the System section, select System Status.
Do any of the following:
To change the online status of a server, select a server, and then click Set Online or Set Offline.
To remove a server that is not communicating, select a server, and then click Remove Server(s). If the server later reestablishes communication, then it automatically reappears in the server list.
The LDD system lets you view and manage the schedule of the following tasks:
Discovery
Policy Update
Script
Report
Backup & Restore
From LMC, click the System tab.
From the System section, select Schedule.
Do either of the following:
To add a task, click Add, and then select a task to schedule.
To edit a task, select a task, and then click Edit.
If necessary, create a description for the task, and then click Next.
Configure the settings. Do one of the following:
To schedule a Discovery task or a Policy Update task, select a device group, and then click Next.
To schedule a Report task, select a report, and then configure its parameters. Click Next. For more information, see Scheduling a report.
To schedule a Backup & Restore task, type the path of the backup share and the credentials required to access the specified share, and then click Next. For more information, see Scheduling automatic backups.
To schedule a Script task, select a group type, and then click Next. For more information, see Scheduling scripts.
Configure the date, time, and frequency for the task.
Click Finish.
When a job is completed, a confirmation is automatically delivered unless it is disabled within a particular solution.
From LMC, click the Services tab.
From the Services section, select Confirm.
From the Tasks section, select Parameters.
Select the lowest level of messages to include in confirmations:
debug—Includes detailed messages that are used to diagnose problems, and other message levels lower than this level
info—Includes messages that indicate successful job activities, and other message levels lower than this level
warn—Includes messages that indicate potential problems, and other message levels lower than this level
error—Includes messages that indicate unsuccessful job activities, and other message levels lower than this level
fatal—Includes only messages that indicate complete failure of jobs
Type a title for the confirmation page or message.
Select the task used to deliver the confirmation page:
confirm.printPS—Prints a confirmation page in PostScript format
confirm.printPDF—Prints a confirmation page in PDF format
confirm.emailAdmin—Sends a message to the administrator e-mail address with a PDF confirmation page attached
confirm.emailAdminTextOnly—Sends a message containing the confirmation information to the administrator e-mail address with no attachments
If you are using e-mail confirmations, then in the "Admin email address" field, type the address where e-mail confirmations are sent.
If necessary, configure the remaining parameters.
Click Apply.
New servers may be added to an existing system to increase capacity, or servers may be replaced without reinstalling other components. When a new server is installed on a system that has existing solutions, the solutions and all associated settings must be added to the new server. If the new server does not have the same services as existing servers, then jobs that use the solution with missing services fail.
Add the computer where you are going to install the new server.
Using an NTP server, synchronize the time on all computers that are used in the LDD system.
Install the server. For more information, see Installing servers.
On the new server, install any third-party services that the existing solutions require.
From LMC, click the System tab.
Set the new server online. For more information, see Viewing and changing server status.
The following allow the IP address of the components to be changed without reinstallation:
An incorrect IP address or FQDN is used when installing a configuration 1 system.
The IP address of the computer on which the components of a configuration 1 system are installed changes.
From the command line on the computer where all components are installed, navigate to the Lexmark\Solutions\InstallHelper folder in the location where the components are installed.
Do either of the following:
To use the IP address of the local computer, type , and then press Enter.
To use the FQDN of the local computer, type , and then press Enter.
Change the LMC desktop shortcut to the new IP address or host name. Do the following:
On the desktop of the computer where the components are installed, right-click the LMC shortcut, and then click Properties.
Click the Shortcut tab, and then click Find Target or Open File Location.
Right-click the LMC shortcut, and then click Properties.
In the URL field, type the new IP address or host name of the local computer. The complete URL must be , where is the host name or IP address of the computer where the components are installed.
In an enterprise environment, an error may occur when the following are installed in three different computers and their IP addresses change:
Database server (Firebird or Microsoft SQL Server)
Load balancer
LDD application server
From your computer, navigate to the C:\ProgramFiles\Lexmark\Solutions\InstallHelper folder.
Run Update-addr.bat, and then enter , where is the new database server IP address.
From the Framework DB section, make sure that the LOADBALANCER and SERVER tables are blank.
From your computer, navigate to the C:\ProgramFiles\Lexmark\Solutions\InstallHelper folder.
Run lpm-update-address.bat, and then enter , where is the new load balancer server IP address.
Stop all LDD services and Apache 3.
From the registry, do either of the following:
Update to the following:
Params [REG_MULTI_SZ] = "start <DB_IPaddress> <LB_IPaddress> 9705 C:\Program Files\Lexmark\Solutions Firebird"
Update to the following:
Params [REG_MULTI_SZ] = "start <DB_IPaddress> <LB_IPaddress> 9705 C:\Program Files\Lexmark\Solutions MSSQL"
Where:
is the new database server IP address.
is the new load balancer server IP address.
From your computer, navigate to the C:\ProgramFiles\Lexmark\Solutions\InstallHelper folder.
Run lpm-update-address.bat, and then enter , where is the new load balancer server IP address.
Navigate to the C:/Program Files/Lexmark/Solutions/apps/wf-ldss/WEB-INF/classes/adaptor.properties file, and then update the following:
Where is the new load balancer server IP address.
Navigate to the C:/Program Files/Lexmark/Solutions/apps/wf-ldss/WEB-INF/classes/dbProduct.properties file, and then update the following:
Where is the new database server IP address.
Navigate to the C:/Program Files/Lexmark/Solutions/apps/wf-ldss/lmc.url file, and then update the following:
Where is the new load balancer server IP address.
Restart all LDD services.
Open LMC using the new load balancer IP address.
From LMC, click the System tab.
From the System section, select System Status.
Set all servers offline. For more information, see Viewing and changing server status.
Turn off all server computers, load balancer computers, and database computers.
Turn on all database computers, load balancer computers, and server computers.
From LMC, click the System tab.
From the System section, select System Status.
Set all servers online. For more information, see Viewing and changing server status.
When installing a workflow solution that includes a component, restart the Lexmark Solutions Application Server.
Restarting the Lexmark Solutions Application Server reverts the solution-related files of the following folders to the default version that is stored with the solution package:
\Lexmark\Solutions\apps\wf-ldss\
\Lexmark\Solutions\apps\wf-ldss\solutions
From LMC, click the System tab.
From the System section, select System Status.
Set all servers offline. For more information, see Viewing and changing server status.
From the Windows Services control panel, restart the Lexmark Solutions Application Server.
From LMC, click the System tab.
From the System section, select System Status.
Set all servers offline. For more information, see Viewing and changing server status.
If the database or load balancer is installed on a failover cluster, then do the following:
On the primary node of each cluster, close all applications that are using the shared drive where LDD components are installed.
From Failover Cluster Manager, move all cluster resources to the primary node where the LDD components are originally installed.
Stop the cluster service on standby nodes.
Before continuing the upgrade, wait for confirmation that the standby nodes are disabled.
From the computer where the components are installed, navigate to the Lexmark folder, and then uninstall LDD.
Follow the instructions on the screen.
The AP Bundle is an eSF application that LDD installs on X642 printers and e-Task 5, e-Task 4, e-Task 3, e-Task 2+, and e-Task 2 MFPs and SFPs. This application is required for LDD support and provides prompting capabilities, application profiles or held jobs support, and security support for printers with LDD.
From LMC, click the System tab.
From the System section, select AP Bundle.
Browse to the AP Bundle application file (.fls), and then browse to the AP Bundle descriptor file (.xml).
Notes:
Click Upload.
During the next policy update, LDD updates the AP Bundle on printers where it has not been installed or when an older version is installed.
Using a text editor, open the httpd.conf file from the <install-Dir>/Lexmark/Solutions/Apache2/conf directory, where <install-Dir> is the installation folder of LDD.
From the section, uncomment the module.
#LoadModule evasive2_module modules/mod_evasive2.so
From the white list section, add the appropriate IP addresses.
DOSWhitelist 127.0.0.1 DOSWhitelist 127.0.0.*
Save the file.