Jobserver Administrator's Guide

This section contains advanced guides for the configuration and administration of a migration-center Jobserver.

Start the Jobserver in Console Mode

You can start your Jobserver in Console Mode by going to the Server Components installation folder and running the runConsole.bat file. By default, this Jobserver will run on port 9701.

This can be useful if a full Jobserver installation cannot be done as the runConsole.bat file can be ran directly from the installation kit.

Before starting the Jobserver in console mode ensure the service is not already running.

Uninstall and reinstall the Service manually

The Migration Center Job Server service is installed by the Server Components installer.

To manually uninstall and reinstall the service you need to:

  1. Go to your migration-center Server Components installation folder.

  2. Run UninstallWinNTService.bat to uninstall the service.

  3. Run InstallAsWinNTService.bat to reinstall the service.

In some environments you might need to run the scripts with Run As Administrator.

Change the Port

To change the port used by the Jobserver you need to:

  1. Go to your ...\migration-center Server Components\lib\mc-core folder.

  2. Open server-config.properties using a text editor.

  3. Edit the server.port= parameter to your desired port.

  4. Restart your Jobserver.

Change the Service and Display Name

To change the Service and Display Name and of your Jobserver you need to:

  1. Go to your migration-center Server Components installation folder.

  2. Uninstall the Migration Center Job Server service. See: Uninstall and reinstall the Service manually

  3. Open the wrapper.conf file using a text editor.

  4. Edit the wrapper.ntservice.name= parameter to change the Service Name.

  5. Edit the wrapper.ntservice.displayname= parameter to change the Service Display Name.

  6. Reinstall the newlly renamed service. See: Uninstall and reinstall the Service manually

Increase Java Heap Space

To increase the Maximum Java Heap Space used by the Jobserver you need to:

  1. Go to your migration-center Server Components installation folder.

  2. Open the wrapper.conf file using a text editor.

  3. Edit the wrapper.java.maxmemory= parameter and increase the heap size.

  4. Restart the Jobserver.

Enable Jobserver Debug

Setting your Jobserver logging level to DEBUG provides detailed logging information that is used by the Support Team to troubleshoot your issues.

To enable Jobserver Debug you need to:

  1. Go to your ...\migration-center Server Components\lib\mc-core folder.

  2. Open the logback.xml file using a text editor.

  3. Change the line <property name="LOGGING_LEVEL" value="ERROR"/> to <property name="LOGGING_LEVEL" value="DEBUG"/>.

  4. Wait 30 seconds for the new change to take effect, or restart the jobserver.

After running your scanner/importer with Jobserver Debug enabled please send the following log files to the Support Team:

  1. Your scan / import run log.

  2. The mc-adapters.log, mc-server.log, and wrapper.log files found under the ...\migration-center Server Components\logs folder.

You should only ever enable this when directed by the Support Team and you should set the logging back to ERROR after troubleshooting.

Leaving the logging level on DEBUG during production runs can result in large logs taking up disk space and performance issues.

Please note that Jobserver Debug and the loggingLevel parameter on a scanner or importer are different.

The loggingLevel parameter will only change logging for the scan/import run log.

Enabling Jobserver Debug will provide a lot more detailed logs besides the run log.

Alfresco adaptors debug

The Alfresco Scanner and Alfresco Importer are installed as a disctinct Jobserver inside the Alfresco's tomcat. Therefore the steps to enabling jobserver debug are different:

  1. Navigate to this folder inside Alfresco's Tomcat: webapps\alfresco\WEB-INF\classes\alfresco\module\fmeMcJobServer

  2. Open the log4j.properties file

  3. Change the following line to DEBUG and save the file: logging.level.adapters=ERROR

  4. Restart the Alfresco Tomcat

  5. After re-running the scan or import to reproduce the issue, the logs can be found under the tomcat\logs folder. Files: mc-alfresco.log and mc-jobserver.log.

Noe that if you still have the WAR file for the Alfresco in the webapps folder, it might overwrite your change when you restart Tomcat. So either modify the file in the WAR directly or do not keep it in the webapps folder.

Access Network Shares

See: Access Network Shares

Last updated

Was this helpful?