Workday Connector > Troubleshooting > Troubleshooting Configuration Issues
  

Troubleshooting Configuration Issues

The log and exception messages thrown while configuring the synchronization tasks are captured in the log files. These log files are saved in a specific location.
For example, <Secure Agent installation directory>\apps\Data_Integration_Server\<latest version of connector>\ICS\main\tomcat\log.

Troubleshooting Synchronization Task

While creating a synchronizationtask, the NULL error message appears when a connector with invalid configuration is selected. The null error message files are saved in specific location.
For example, <Secure Agent installation directory>\apps\Data_Integration_Server\<latest version of connector>\ICS\main\tomcat\log.
The log and exception details of a failed synchronization task are captured under the Session Log. You require special permission privileges to run the application in debug mode.

Validating End Point

Visit the given URL to validate the end point:
https://Domain Name/ccx/service/Tenant Name/Financial_Management/version?wsdl
Where,
Domain Name represents the value in domain Name field. See Creating New Connection
Tenant Name represents the value in Tenant Name Field. See Creating New Connection
Version represents the current version of Connector that is v22.0

Increasing the Secure Agent memory

To increase performance and avoid runtime environment memory issues, perform the following steps:
    1In Administrator, select Runtime Environments.
    2Select the Secure Agent for which you want to increase memory from the list of available Secure Agents.
    3In the upper-right corner, click Edit.
    4In the System Configuration Details section, select the Type as DTM for the Data Integration Service.
    5Edit JVMOption1 as -Xms4056m and JVMOption2 as -Xmx4056m.
    The following image shows the Details page:
    The image shows the Agent Name.
    6In the System Configuration Details section, select the Type as TomCatJRE
    7Edit INFA_memory as -Xms256m -Xmx512m.
    The following image shows the Agent Details page:
    For the agent name, we can see the Type as Tomcat JRE.
    Note: The minimum and maximum values for the Java heap size are given as an example. Specify the size according to your requirements.
    8Restart the Secure Agent.