The following describes what might cause deployment of a General custom adapter to fail, how to identify the cause of the failure, and what action you need to take.

(a) Causes

The following are the most likely causes of a General custom adapter failing to deploy:

1. The format or content of the HITACHI Application Integrated Property File for the custom adapter is invalid.
2. An invalid EAR file is registered because the correct procedure in 3.3.14 Defining custom adapters was not followed.

(b) Identifying the cause

Check the console log displayed during deployment:

• If the following message is displayed:
  

  KEOS50007-E An exception occurred during the operation. (Cosminexus Manager name = manager-ID, object name = jp.co.Hitachi.soft.csc.msg:type= CSCMsgAdapterBuilder, operation = setup, details = The application attributes file is invalid. (detailed-information) ErrorCode=KDEC10031-E)

  The cause might be 1 or 2 above.
  View detailed-information for the specific cause.
  

(c) Action to take

Take the following action:

• Check whether the format and content of the HITACHI Application Integrated Property File for the custom adapter are valid. If the format or content is invalid, create the file again. For details on the HITACHI Application Integrated Property File, see B.2(3) HITACHI Application Integrated Property File for custom adapter.
• Check whether the format and content of the EAR file you are using are valid. If the format or content is invalid, create the file again. For details on how to create an EAR file, see 3.3.14(6) Creating an EAR file.

The following describes what might cause a General custom adapter to fail to start, how to identify the cause of the failure, and what action you can take to resolve it.

(a) Causes

The following are the most likely causes of a General custom adapter failing to start:

1. The custom adapter development framework action definition file has not been placed in the root folder of all registered JAR files.
2. The format of the custom adapter development framework action definition file is invalid.
3. The format of the custom adapter property file is invalid.
4. The protocol converter JAR file does not include the class file for the protocol converter.
5. The protocol converter is specified incorrectly in the custom adapter development framework action definition file, or the specified protocol converter does not exist.
6. The protocol converter does not have a public default constructor.
7. An exception occurred in the start method of the protocol converter.

(b) Identifying the cause

Check the message log file.

• If a message like the following is recorded in the message log:
  

  KDEC02513-E An attempt to read the file has failed. (adapter name = adapter-name, file name =file-name, information =detailed-information)

  The following table shows the correspondence between the characters in the error message and the cause of the error:
  

  Table B-5 Causes of KDEC02513-E

  File name	Detailed information	Cause
  framework_properties.xml	InputStream is null	The cause might be 1.
  	InvalidPropertiesFormatException	The cause might be 2.
  defs/customadapter_properties.xml	InvalidPropertiesFormatException	The cause might be 3.

• If a message like the following is recorded in the message log:
  

  KDEC03015-E An initialization error occurred in the protocol converter. (adapter name = adapter-name, information =exception-that-caused-error)

  The following table shows the correspondence between the characters in the error message and the cause of the error:
  

  Table B-6 Causes of KDEC03015-E

  Exception that caused error	Cause
  ClassNotFoundException	The cause might be 4 or 5.
  IllegalAccessException	The cause might be 6.
  CSCMsgCustomAdapterException	The cause might be 7.

(c) Action to be taken

If the cause is 1 or 2, take the following action:

• Check whether the format and content of the custom adapter development framework action definition file are valid. If the format or content is invalid, create the file again. For details on the custom adapter development framework action definition file, see B.2(1) Custom adapter development framework action definition file.
• Check whether the custom adapter development framework action definition file is in the location specified in the JAR file for the protocol converter. If the file is not in this location, place it in the correct location.

If the cause is 3, take the following action:

• Check whether the format and content of the operation definition file for the custom adapter development framework are valid. If the format or content is invalid, create the file again. For details on the custom adapter property file, see B.2(2) Custom adapter property file.

If the cause is 4 or 5, take the following action:

• Check whether the protocol converter JAR file includes the class file for the protocol converter. If it does not include the class file, use the jar command to archive the protocol converter class file, the class files used by the protocol converter class file, and the custom adapter development framework action definition file in the JAR file. For details on how to create the protocol converter JAR file, see 3.3.14(5)(a) Creating protocol converter JAR files.
• Check that the package name is specified together with the protocol converter name in the custom adapter development framework action definition file. If the name is invalid, specify the protocol converter name and package name correctly.
• Check whether classname is specified as the value of the key attribute of the entry element that specifies the protocol converter name in the custom adapter development framework action definition file. If this is not the case, enter the class name of the protocol converter in the entry tag whose key attribute is classname.

If the cause is 6, take the following action:

• Check whether a public default constructor is defined for the protocol converter. If none is defined, define a public default constructor.

If the cause is 7, take the following action:

• Check the processing of the start method of the protocol converter. If the processing is invalid, review its implementation. For details on the format of the start method, see B.1(2)(a) CSCMsgCustomAdapterContext interface.
• Make sure that the environment and preferences you are using permit the protocol converter to start.

This section describes what might cause a java.security.AccessControlException exception to occur when you attempt to perform file operations from the protocol converter, how to identify the cause, and what action to take.

(a) Cause

A Java security feature might have prevented file access.

(b) Identifying the cause

Make sure that java.security.AccessControlException is thrown in the protocol converter during file access.

(c) Action to be taken

Take the following action:

• Use the container extension library
  For details on how to use the container extension library, see 14.2 Using the container extension library in the manual Application Server Common Container Functionality Guide. For details on how to implement the container extension library, see 14.3.2 Procedure of creating and using the container extension library in the manual Application Server Common Container Functionality Guide.
  
• Edit the settings in the security policy file
  For details on the settings in the security policy, see 9.8.2 Setting security policy in the manual Application Server Expansion Guide.
  
• Use the user log functionality (if the purpose of the file access is log output)
  For details on the user log functionality, see 9.12 Notes for using the user log functionality in the manual Application Server Expansion Guide.