Unable to Connect Service Layer URL Error in Datamaker
search cancel

Unable to Connect Service Layer URL Error in Datamaker

book

Article ID: 4081

calendar_today

Updated On:

Products

CA Test Data Manager (Data Finder / Grid Tools)

Issue/Introduction

When connecting to a profile in Datamaker, or connecting to another product from within Datamaker like Agile Designer or GTDiagrammer, you may encounter an 'Unable to connect Service Layer' error message.


Although at this point, you can click 'OK' and still use Datamaker, you will not be able to connect to Agile Designer from within the UI, and you will not be able to use Test Data on Demand (TDoD) either.

Environment

CA Test Data Manager (TDM)- Datamaker

Cause

This error message means that either your SOAP web service layer has not been set up correctly, meaning the services have not been started, or these services have not been configured at all. The service layer is used primarily for the Test Data on Demand (TDoD) feature, and for connecting you to other products from within Datamaker, such as Agile Designer.

Another reason you may get this message is if the service layer did not start successfully because the repository database is down or not completely started. This can be an issue when the repository is located on the same server as Datamaker.

Note: With Test Data Manager version 4.9.1 or newer, and Agile Requirements Designer 3.1 or newer, the TDoD (GTService) Service Layer is not required, and has been replaced by the native TDM Portal service: TDMService.

Resolution

Workaround:

If you do not intend to configure the service layer for your environment and would like to disable the 'Unable to connect service layer' message during startup, perform the following steps. You will need to have Administrator privileges in Datamaker to do this.

  1. Follow the error recreation steps above and click 'OK' when the 'Unable to connect service layer' message is displayed. 
  2. From the toolbar on the Datamaker homepage, click on the 'Security' tab.
  3. Choose 'Users and Groups' from the drop-down menu.
  4. Enter your Datamaker Administrator credentials on the login screen that appears in red and click the green checkmark in the bottom, right-hand corner.
  5. On the 'Maintain Security' window, click the 'Service Layer' tab. 
  6. Uncheck the box next to the 'Enable Service Layer Integration' option.
  7. Click the blue save icon that appears to the right of the option to save your setting changes.

 

Resolution #1:

The most common way to resolve this issue is to start your CA Test Data Manager, TDoD, and Remote Publish Services. 

  1. From your Windows services menu, click on the 'Control Panel' option.
  2. Click on 'System and Security' from the list.
  3. Click on 'Administrative Tools' from the list.
  4. Double-click on the 'Services' option. (Control Panel\System and Security\Administrative Tools\Services)
  5. Locate the 'CA Remote Publish' service. This is for the Datamaker Remote Publish Engine feature.
  6. Right-click on the service, and choose 'Start' from the drop-down menu.
  7. Locate the 'CA TDoD' service. This provides SOAP-based access to the Datamaker repository.
  8. Right-click on the service, and choose 'Start' from the drop-down menu.
  9. Locate the 'CA Test Data Manager Portal' service. This is for the TDM Portal that is available in release 3.5 and above versions. 
  10. Right-click on the service, and choose 'Start' from the drop-down menu.
  11. Once all the services are running, restart Datamaker and verify that you are no longer seeing the error message.

If you are seeing any error messages after trying to start the services, a best practice is to check your log files. This might give you insight as to why your services are not starting. 

  1. Go to C:\Grid-Tools\TDoD\TDoD_Service\logs
  2. Take note of any error messages in the logs. 
  3. Go to C:\Grid-Tools\RemotePublish\logs
  4. Take note of any error messages in the logs. 
  5. If you are unable to resolve the issue based on the message in the log file, please open a support case. 

Note: If you still see the error message after following these steps and relaunching Datamaker, you can change the CA TDoD Service to 'Automatic (Delayed Start). This will give the repository time to start fully before TDoD tries to connect. 

  1. From the Windows Services window, right-click on the 'CA TDoD' Service. 
  2. Choose 'Properties' from the drop-down list.
  3. From within the 'General' tab, under 'Startup type', choose 'Automatic (Delayed Start) from the drop-down list.
  4. Click the 'Apply' button.
  5. Click the 'OK' button.
  6. Restart Datamaker and verify that you are no longer seeing the error message.

Note: If you launch Datamaker immediately after a reboot, then you still might get the message as the service is still waiting to start.

 

Resolution #2:

If your services are already running, and you are still seeing the error message, then you should check to see if your Service Layer Integration is enabled and the Primary Service URL is correct.

  1. Launch Datamaker and click 'OK' when the 'Unable to connect service layer' message is displayed. 
  2. From the toolbar on the Datamaker homepage, click on the 'Security' tab.
  3. Choose 'Users and Groups' from the drop-down menu.
  4. Enter your Datamaker Administrator credentials on the login screen that appears in red, and click the green checkmark in the bottom, right-hand corner.
  5. On the 'Maintain Security' window, click the 'Service Layer' tab. 
  6. Check the box next to the 'Enable Service Layer Integration' option.
  7. Within the 'Primary Service URL' text box, edit it to point to your hostname. For example, http://localhost:8090/GTService. 
  8. Click the blue save icon that appears to the right of the option to save your setting changes.
  9. Restart Datamaker and verify that you are no longer seeing the error message.

 

Resolution #3:

If your services are running, the Service Layer Integration is enabled, the Primary Service URL in Datamaker is correct, and you are still seeing the error message, you need to make sure your TDoD and Remote Publish configurations are set up correctly.

Configure your TDoD Services:

  1. Go to your TDoD Configuration Editor folder. The default location for that is C:\Grid-Tools\TDoD\TDoD_ConfigEditor
  2. Double-click on the TDoDConfigEditor.exe to launch it.
  3. Under the 'Configure Service' tab's 'Connection String' tab, verify that your repository details are correct. 
  4. Click the 'Save' button if you made any changes.
  5. Click the 'Verify' button to make sure those connection details are correct.
  6. Under the 'Configure Portal' tab's 'Settings' tab, verify that the 'Service URL' is correct. The default is http://<<machinename>>:8090/GTService, and it needs to be configured to what your Primary Service URL is in Datamaker. (Reference Resolution 2's steps) 
  7. You will also need to configure the correct 'ALM Service URL' or erase the default URL that is there or that could cause some other issues. Consult the documentation if you have any further ALM configuration questions: Refer to section "Configure ALM Integration" in the documentation of the Test Data Manager release you are running.
  8. Click the 'Save' button if you made any changes.
  9. Click the 'Verify' button to make sure those connection details are correct.
  10. Go back to the Configure Service -> Connection String tab.
  11. Click the 'Start Service' button. 
  12. Consult the documentation if you have any further TDoD configuration questions (under 'Configure TDoD Service' section): Refer to section "Configure ALM Integration" in the documentation of the Test Data Manager release you are running.

Configure your Remote Publish Services:

  1. Go to your Remote Publish Configuration Editor folder.
  2. Double-click on the RemotePublishConfiguration.exe to launch it.
  3. Under the 'Configure' tab, verify that your 'Connection String' details are correct.
  4. Click the 'Save' button if you made any changes.
  5. Click the 'Verify' button to make sure those connection details are correct.
  6. Under the 'Status' tab, click the 'Start Service' button.
  7. Consult the documentation if you have any further Remote Publish configuration questions: Refer to section "Configure the Remote Publish Engine" in the documentation of the Test Data Manager release you are running.
  8. Restart Datamaker and verify that you are no longer seeing the error message.  

If you are seeing any error messages after trying to start the services, a best practice is to check your log files. This might give you insight as to why your services are not starting. 

  1. Go to C:\Grid-Tools\TDoD\TDoD_Service\logs
  2. Take note of any error messages in the logs. 
  3. Go to C:\Grid-Tools\RemotePublish\logs
  4. Take note of any error messages in the logs. 
  5. If you are unable to resolve the issue based on the message in the log file, please open a support case. 

Additional Information

Community Post: https://communities.ca.com/message/241747533 

If you experience any further issues, please open a support case on https://support.broadcom.com or call support at 1-800-225-5224.

Powered by Wolken Software