Chapter 2. Configuring the Migration Toolkit for Applications instance environment

Procedure

1. In Administration view, click Credentials.
2. Click Create new.

3. Enter the following information:

   • Name
   • Description (Optional)
4. In the Type list, select Source Control.

5. In the User credentials list, select Credential Type and enter the requested information:

   • Username/Password

     • Username
     • Password (hidden)

   • SCM Private Key/Passphrase

     • SCM Private Key

     • Private Key Passphrase (hidden)

       Note

       Type-specific credential information such as keys and passphrases is either hidden or shown as [Encrypted].

6. Optional: If you want to set source control credentials as default, enable the Use as the source control credential if an application does not have any assigned? switch.

7. Click Create.

   Note

   MTA validates the input and creates a new credential. SCM keys must be parsed and checked for validity. If the validation fails, the following error message is displayed: “not a valid key/XML file”.

Procedure

1. In Administration view, click Credentials.
2. Click Create new.

3. Enter the following information:

   • Name
   • Description (Optional)
4. In the Type list, select Maven Settings File.
5. Upload the settings.xml settings file or paste its contents.

6. Optional: If you want to set Maven credentials as default, enable the Use as the source control credential if an application does not have any assigned? switch. These credentials will be used by default for all applications that do not have any assigned credentials.

   Important

   If you do not set Maven credentials as default, you must assign these credentials to the application manually before running an analysis. Otherwise, credentials will not be picked up by the application, which might result in the analysis running longer.

7. Click Create.

   Note

   MTA validates the input and creates a new credential. The Maven settings.xml file must be parsed and checked for validity. If the validation fails, the following error message is displayed: “not a valid key/XML file”.

Procedure

1. In Administration view, click Credentials.
2. Click Create new.

3. Enter the following information:

   • Name
   • Description (Optional)
4. In the Type list, select Proxy.

5. Enter the following information.

   • Username

   • Password

     Note

     Type-specific credential information such as keys and passphrases is either hidden or shown as [Encrypted].

6. Click Create.

   MTA validates the input and creates a new credential.

Procedure

1. In Administration view, click Repositories and then click Git.
2. Enable the Consume insecure Git repositories switch.

Procedure

1. In Administration view, click Repositories and then click Subversion.
2. Enable the Consume insecure Subversion repositories switch.

Procedure

1. In Administration view, click Repositories and then click Maven.
2. Enable the Consume insecure artifact repositories switch.

3. Optional:To reduce the size of the Maven repository, click the Clear repository link.

   Note

   Depending on the size of the Maven repository, the size change might not be evident.