In some cases, processing will not be completed after a certain amount of time passed from the approval of the request, error mail will not be sent, and the log of the coordination adapter will not be output. In such cases, it is possible that the process in the coordination adapter had become error state and is aborted. Check the state of the process by the following procedure.

1. Check the status of the coordination adapter process by executing the following command. The list of the error processes is displayed as the result of the command.

   %FSCSM_HOME%\SWRBA\SWRBAM\bin\swrba_admin pi-list -user swrbaadmin -password <Password> -state error -startedafter <start date> -startedbefore <end date>

   Options	Explanations
   -user	Specify the username of the user for process control of the coordination adapter. The username is "swrbaadmin" and is fixed.
   -password	Specify the password of the user for process control of the coordination adapter. Use the value specified at the setup of the coordination adapter.
   -state	Specify the state of the process definition. "error" must be specified.
   -startedafter	Specify the start date of the period when the process was started. Specify it in the form of the following. yyyy-mm-dd
   -startedbefore	Specify the end date of the period when the process was started. Specify it in the form of the following. yyyy-mm-dd

   Example

   Here is an example to check the error state that occurred on September 1, 2015.

   %FSCSM_HOME%\SWRBA\SWRBAM\bin\swrba_admin pi-list -user swrbaadmin -password systemwalker#1 -state error -startedafter 2015-09-01 -startedbefore 2015-09-01

2. Take the following action and see if the problem is resolved in the case the trouble occurred in the request to ROR.

   • Change the setting of the communication with ROR to increase the waiting time for the responses from ROR. Refer to "Configuring the Communication Environment" in "Setup of the Coordination Adapter" in "Cloud Services Management Installation Guide" for the setup of the coordination adapter.

3. Collect the troubleshooting data and contact the Fujitsu support staff if the trouble is other than the above or the trouble cannot be resolved by the above actions.