J.3 List of changes in specifications from earlier versions
This appendix describes the changes in the specifications of Service Platform from version 09-71 to version 11-00.
- Organization of this subsection
(1) Changes in specifications about the log data output destination
- Amendments:
-
The log data output destinations of the HCSC components in the following table have been changed.
Table J‒1: Changes of log data output destinations Category
Summary of the change
Section to see
TP1 adapter
The output destinations of the following types of log data were changed:
-
Exception log
-
Method trace
-
Data trace
Object Access adapter
The output destinations of the following types of log data were changed:
-
Exception log
-
Method trace
-
Data trace
Message Queue adapter
The output destinations of the following types of log data were changed:
-
Exception log
-
Method trace
-
Data trace
7.4.7 and
FTP inbound adapter
The output destinations of the following types of log data were changed:
-
Message log
-
Maintenance log
-
FTP protocol trace
-
Transfer history log
-
Common log for resource adapters
FTP adapter
The output destination of the following log data was changed:
-
FTP protocol trace
-
- Tasks required for migration to a system in which compatibility is important:
-
Specify the log data output destinations that are indicated in the Changes of log data output destinations table and were enabled before migration.
- Tasks required for migration to a system that uses recommended functions:
-
None
- Impact:
-
If the tasks shown in Tasks required for migration to a system in which compatibility is important are not performed, the log data output destinations indicated in the Changes of log data output destinations table will be changed.
(2) Changes in specifications about user-defined receptions
- Amendments:
-
A user-defined reception that can invoke any business processes of the user's choice was supported. With this change, the name of the user-defined reception that was supported in version 09-87 or earlier was changed.
The following two types of user-defined receptions are currently available:
-
User-defined reception (invocation target fixed): User-defined reception that was supported in version 09-87 or earlier
-
User-defined reception (invocation target selected): User-defined reception that was added in version 11-00
In Service Platform products and manuals, the term user-defined reception generically refers to the preceding two types of user-defined reception.
-
- Tasks required for migration to a system in which compatibility is important:
-
None
- Tasks required for migration to a system that uses recommended functions:
-
None
- Impact:
-
There is no impact on the operation of the existing business applications.
(3) Changes in specifications about the NonCustom Standard Editor of the Service adapter definition window
- Amendments:
-
The item Format ID was deleted from the NonCustom Standard Editor of the Service adapter definition window. A unique identification number is now automatically assigned as the format ID when the settings specified in the Service adapter definition window are saved.
- Tasks required for migration to a system in which compatibility is important:
-
None
- Tasks required for migration to a system that uses recommended functions:
-
None
- Impact:
-
None
(4) Changes in specifications about the KEOS52272-I message
- Amendments:
-
Which SOAP mode (SOAP 1.1 mode or SOAP 1.1/1.2 combined mode) was set is now output in the KEOS52272-I message.
- Tasks required for migration to a system in which compatibility is important:
-
None
- Tasks required for migration to a system that uses recommended functions:
-
None
- Impact:
-
None