Skip to Content

Task 4: To configure FAS license

FAS connects to BMC AMI Common Enterprise Services (CES) to retrieve license information. The connection to CES, which can be via a local CES server or via a cloud license, must be configured on FAS.

For Windows

  1. Select Start > Programs > BMC > File-AID Services > Configuration shortcut to invoke the utility.
  2. Follow one of these steps:
    • To use a local CES server to connect to CES, select the License Preferences tab, select the Enterprise Services radio button. Then select the Enterprise Services tab and in the Service URL field, enter the URL for the CES server. Here is an example of a CES URL: http://yourCesServer:yourCesPort/
      Local_CES.png
    • To use a cloud license to connect to CES, select the Cloud radio button in the License Preferences tab. Then set the following properties:Cloud.png
      • Service URL
      • Customer Number

      • Site ID 
        To use BMC maintained CES cloud license, contact BMC Support

         

  3. If the configuration is changed, click OK to save the settings. Restart the server for the changes to take effect.                  

For Linux

  1. In the directory containing the installed FAS, issue the shell command ./runServerConfig.sh.

  2. Follow one of these steps:

    • To use a local CES server to connect to CES, select option 5 and enter false in the License Preferences tab. Then enter option 4 and enter the URL for the Enterprise Services tab. Here is an example of a CES URL: http://yourCesServer:yourCesPort/
    • To use a cloud CES, select option 5 and enter true in the License Preferences tab. Then set the following properties:
      • CES Cloud URL (Option 6)
      • Customer Number (Option 7)
      • Site ID (Option 8)

    To use BMC maintained CES cloud license, contact BMC Support.

  3. Stop and restart FAS to apply the changes. See task Task 5: To control FAS.

To configure HTTPS CES license URL for FAS

This section explains how to configure the CES license URL to use HTTPS for File-AID Services (FAS). Using HTTPS ensures secure communication between FAS and the CES server and helps prevent certificate trust and license connectivity issues.

CES secure URL format:

https://<CES_server>:<CES_secure_port>/

Run the following following steps:

Step 1: Export the certificate from the CES keystore

Export the SSL certificate from the CES keystore (.jks file).

  1. Navigate to the CES installation directory

    cd <CES_installation_path>

  2. Run the following command:

    keytool -exportcert -alias <alias_name> -keystore <keystore_name>.jks -file <certificate_name>.cer -rfc

Notes:

  • You must provide the keystore password that was set when <keystore_name>.jks was created.
  • If you do not provide the correct password, the certificate export fails.
  • This command generates a PEM-formatted (.cer) certificate file.

Step 2: Copy the certificate to the required Java security paths

Copy the exported certificate file to the Java security directory used by FAS.

Default FAS Java security path:

<FA​​S_installation_path>/MMCServer/eclipse/jre/lib/security/

For Java 11, copy the certificate to the security directory for each Java version used by FAS.

Example paths:

  • Linux

    /usr/lib/jvm/jre-11-openjdk-11.0.25.0.9-2.el8.x86_64/lib/security/

  • Windows:
    C:\Program Files\Java\<Java_version>\lib\securityNote:     Ensure that you copy the certificate to the exact Java version used by the FAS services.

Step 3: Import the certificate into the Java truststore

Import the certificate into the Java cacerts truststore.

Run the following command:

keytool -importcert -file <certificate_name>.cer -keystore cacerts -storepass changeit -alias <alias_name>

Notes:

  • The default Java truststore password is changeit, unless your organization has changed it.
  • When prompted, type yes to trust the certificate.
  • Repeat this step for each Java installation used by FAS, if applicable.

Step 4: Restart the FAS service

Restart the FAS service to apply the certificate changes.

Service to restart: FAS

Use your standard service management commands or scripts.

Step 5: Verify CES HTTPS connectivity

After the services restart, verify HTTPS access to the CES license endpoint.

Run the following command:

curl -k https://<CES_server>:<CES_secure_port>/compuware/ws/Licenses/listLicenses/fileAid

Expected result:
The command returns a valid XML response, similar to the following example:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<AvailableLicenseInfoResponse>
  <reasonCode>0</reasonCode>
  <returnCode>0</returnCode>
  <availableLicenseInfoList>
    <availableLicenseInfo>
      <licenseCount>YourLicenseCount</licenseCount>
      <productName>YourProductName</productName>
    </availableLicenseInfo>
  </availableLicenseInfoList>
  <customerName>YourCustomerName</customerName>
  <customerNumber>YourCustomerNumber</customerNumber>
  <customerSiteId>YourCustomerSiteId</customerSiteId>
</AvailableLicenseInfoResponse>

A successful XML response confirms that:

  • HTTPS connectivity to the CES server is working.
  • The CES SSL certificate is trusted by the Java runtime.
  • License service communication is functioning correctly.

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC AMI DevX Data Studio 23.07