> For the complete documentation index, see [llms.txt](https://docs.migration-center.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.migration-center.com/jobserver-administrators-guide.md).

# 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.

{% hint style="warning" %}
Before starting the Jobserver in console mode ensure the service is not already running.
{% endhint %}

## 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.

{% hint style="warning" %}
In some environments you might need to run the scripts with **Run As Administrator**.
{% endhint %}

## 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](#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](#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**.

## Add Certificates to the Java Keystore

When connecting to a source or target system over HTTPS, a scanner or importer may fail with an error containing:

```
PKIX path building failed
SunCertPathBuilderException: unable to find valid certification path to requested target
```

This can occur when the Java runtime used by the **Jobserver** does not trust the certificate authority that issued the remote server's certificate.

To add the required certificate to the Java keystore:

1. Obtain the certificate from the system administrator, or export it using **Microsoft Edge**:
   * Open the system's HTTPS URL using the hostname and port configured in the adaptor. Click the **site information** icon, select **Connection is secure**, then click **Certificate is valid**.

     ![Microsoft Edge security panel for my-system.company.com showing Certificate is valid](https://2446182955-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCVvDKbYG9vH4BupFiUOn%2Fuploads%2FOW45ZeylkzUypDT4O8Ua%2Fedge-certificate-security-example.png?alt=media)

     *Click **Certificate is valid** to open the certificate viewer.*
   * On the **Details** tab, select the **root CA** at the top of **Certificate Hierarchy** and click **Export**. For a self-signed server certificate, select that certificate instead.

     ![Certificate viewer for my-system.company.com showing Company Root CA, Company Issuing CA, and the Export button](https://2446182955-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCVvDKbYG9vH4BupFiUOn%2Fuploads%2F0ezGD826KQwPw9wfpbJO%2Fedge-certificate-details-example.png?alt=media)

     *In this example, select **Company Root CA** at the top, then click **Export**.*
   * Save as **Base64-encoded ASCII, single certificate** and copy the file to the **Jobserver** machine.
2. Identify the Java installation used by the **Jobserver service**. The Jobserver uses **JAVA\_HOME** if defined, otherwise **JRE\_HOME**, or the **java** command from **PATH** if neither is defined.

   The default Java keystore is located at:

   ```
   <Java runtime home>\lib\security\cacerts
   ```
3. Confirm that the keystore file exists at the selected location and create a backup copy before modifying it.
4. Open a **Command Prompt** with permission to modify the keystore. Run the following command on **one line**, replacing the example paths and alias with the values for your environment:

   ```bat
   "C:\Path\To\Java\bin\keytool.exe" -importcert -alias "company-root-ca" -keystore "C:\Path\To\Java\lib\security\cacerts" -file "C:\Certificates\company-root-ca.cer"
   ```

   Use a unique, descriptive alias for each certificate.
5. Enter the keystore password when prompted. The initial password for Java's standard **cacerts** keystore is **changeit**, unless it has been changed.

   Verify the displayed certificate details and confirm its **SHA-256 fingerprint** with the administrator who supplied the certificate. Enter **yes** at the **Trust this certificate?** prompt to import it.

   A successful import displays:

   ```
   Certificate was added to keystore
   ```
6. Verify the imported certificate using the same Java installation, keystore path, and alias:

   ```bat
   "C:\Path\To\Java\bin\keytool.exe" -list -v -alias "company-root-ca" -keystore "C:\Path\To\Java\lib\security\cacerts"
   ```
7. Stop any running jobs and restart the **Jobserver**.

Repeat these steps on every **Jobserver** that may execute the affected adaptor. After upgrading or replacing Java, verify that the required certificates are available in the keystore used by the Jobserver.

If the error persists, confirm that the correct Java keystore was updated and ask the source or target system administrator to check that the remote server presents a complete, valid certificate chain.

## 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.

{% hint style="danger" %}
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.
{% endhint %}

{% hint style="info" %}
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.
{% endhint %}

### 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**.

{% hint style="warning" %}
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.
{% endhint %}

## Configure number of DB connections

The **minimum and maximum number of Database connections** made by the Jobserver alongside **timeout and idle durations** can be configured from the "...\migration-center Server Components\lib\mc-core\\**server-config.properties**" file.

```
#max number of database connections in a session
db.max.connection-pool.size=64

#min number of database connections in a session
db.min.connection-pool.size=5

#max number of seconds to wait when trying to acquire a new database connection from the pool
db.connection.wait.timeout=10

#max number of seconds that a connection is allowed to remain idle in the pool
db.connection.idle.timeout=600
```

## Access Network Shares

See: [Access Network Shares](https://docs.migration-center.com/installation-guide/access-network-shares.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.migration-center.com/jobserver-administrators-guide.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
