Contents

• Notices

• Preface

• 1. Overview of System Operations Based on SOA

  • 1.1 Procedures for system operations based on SOA

    • 1.1.1 Flow from development to actual operations

  • 1.2 Relationship of the operating environment and the execution environment with the entire system

    • 1.2.1 Positioning in operations

    • 1.2.2 Positioning on the network

    • 1.2.3 Configuration of the operating environment and the execution environment

  • 1.3 Relationship between Test Environment and Production Environment

    • 1.3.1 Case 1: When configuring with the same settings of the database and Reliable Messaging, in the test environment and the production environment

    • 1.3.2 Case 2: When configuring with different settings of the database and Reliable Messaging, in the test environment and the production environment (When repository can be moved as it is)

    • 1.3.3 Case 3: When configuring with the different settings of the database and Reliable Messaging, in the test environment and in the production environment (When re-creating a repository)

  • 1.4 Determining the operations policy

    • 1.4.1 Operations Using a Single HCSC Server

    • 1.4.2 Operations Using Multiple HCSC Servers

    • 1.4.3 Operations Using a Load-balancing Cluster Consisting of Multiple HCSC Servers

    • 1.4.4 Operations to configure High availability clusterin multiple HCSC servers

    • 1.4.5 Operations that build N-to-1 clusterin multiple HCSC servers

• 2. System Configuration

  • 2.1 Installing and Uninstalling

    • 2.1.1 Installation flow

    • 2.1.2 Installing Service Platform

    • 2.1.3 Environment settings

    • 2.1.4 Installing Eclipse

    • 2.1.5 Embedding HCSC-Manager plug-in in Eclipse

    • 2.1.6 Management Server settings for using HCSC-Manager

    • 2.1.7 Uninstalling

  • 2.2 Selecting configuration types and SOAP modes

    • 2.2.1 Existence of usage of database and Reliable Messaging

    • 2.2.2 Existence of usage of table partition functionality

    • 2.2.3 Used SOAP mode

  • 2.3 Settings related to execution environment

    • 2.3.1 Setting HCSC server configuration definition file

    • 2.3.2 Setting HCSC server setup definition file

    • 2.3.3 Setting HCSC server runtime definition file

    • 2.3.4 Setting the definition file for user-defined reception runtime

    • 2.3.5 Estimating database table capacity

    • 2.3.6 Estimating the number of exclusive requests of the database (HiRDB)

    • 2.3.7 Designing mapping in database areas

    • 2.3.8 Storing JAR files that are used for custom functions

    • 2.3.9 Setting up the user property file for the J2EE server (usrconf.properties)

  • 2.4 Settings Related to the Operating Environment

    • 2.4.1 Customizing operating environment

    • 2.4.2 Setting user information

    • 2.4.3 Setting common items of HCSC-Manager command

  • 2.5 Environment setup to change HCSC server to load balancing cluster configuration

    • 2.5.1 Environment setup during load balancing cluster configuration

    • 2.5.2 Setup of execution environment in load balance cluster configuration

  • 2.6 Environment setup to change HCSC Server to HA class configuration

    • 2.6.1 Environment setup in HA class configuration

    • 2.6.2 Execution environment setup in HA cluster configuration

  • 2.7 Environment setup when executing node machine and standby node machine are in 1 to N configuration because load balancing cluster configuration and HA cluster configuration are combined

    • 2.7.1 Environment setup in 1 to N cluster configuration

    • 2.7.2 Execution environment setup in 1 to N cluster configuration

  • 2.8 Environment setup while using JP1 integrated functionality

    • 2.8.1 Flow of JP1 integrated settings

    • 2.8.2 Setting JP1 event execution for Service Platform

    • 2.8.3 Setting JP1/Base event server name

    • 2.8.4 Creating JP1/Base configuration definitions

    • 2.8.5 Editing message mapping files

  • 2.9 Environment configuration for multiple operating environments and execution environments on one machine

    • 2.9.1 Example of system configuration when multiple environments are configured on one machine

    • 2.9.2 Procedure for configuring multiple environments on one machine

• 3. System Setup and Unsetup

  • 3.1 Setting Up the System

    • 3.1.1 Flow of systemsetup

    • 3.1.2 Setting up the software required for the execution environment

    • 3.1.3 Setting up an HCSC server

    • 3.1.4 Setting up the HCSC server definition information

    • 3.1.5 Checking the contents defined in the HCSC server

    • 3.1.6 Changing the service information

    • 3.1.7 Checking the service information

    • 3.1.8 Deploying a service adapter

    • 3.1.9 Importing the HCSC component definition files into the operating environment

    • 3.1.10 Setting and updating the HCSC component definition files in the operating environment

    • 3.1.11 Deleting the HCSC component definition files from the operating environment

    • 3.1.12 Checking the status of the operating environment definition file

    • 3.1.13 Deploying a business process

    • 3.1.14 Deploying a user-defined reception

    • 3.1.15 Setting the definition information for user-defined receptions

    • 3.1.16 Checking the definition information of the user-defined receptions

    • 3.1.17 Checking or changing the set contents

  • 3.2 System setup (For FTP integration)

    • 3.2.1 Flow of setup for an FTP-integrated system

    • 3.2.2 Setting up the common folders and work folders

    • 3.2.3 Setting up the FTP inbound adapter

    • 3.2.4 Allocating the definition files for the FTP reception, FTP adapter, and File operations adapter

    • 3.2.5 Importing a repository

    • 3.2.6 Obtaining the FTP reception definition file

    • 3.2.7 Setting up the definition information of the FTP reception definition file

    • 3.2.8 Deploying the HCSC components

    • 3.2.9 Obtaining the HITACHI Application Integrated Property File for FTP receptions

    • 3.2.10 Setting up the definition information of the HITACHI Application Integrated Property File for FTP receptions

  • 3.3 Cancelling System Setup

    • 3.3.1 Deleting a service adapter

    • 3.3.2 Deleting a business process

    • 3.3.3 Deleting a user-defined reception

    • 3.3.4 Unsetting up an FTP-integrated system

    • 3.3.5 Unsetting up an HCSC server

  • 3.4 Procedure for Moving from Test Environment to Production Environment

    • 3.4.1 Procedure of migration when the existence of usage of the database and Reliable Messaging in the test and production environments is the same

    • 3.4.2 Procedure of migration from an environment where both database and Reliable Messaging are used to an environment where both are not used

    • 3.4.3 Procedure of migration from an environment where both database and Reliable Messaging are not used to an environment where both are used

    • 3.4.4 Procedure of migration from an environment where both database and Reliable Messaging are used to an environment where database is used and Reliable Messaging is not used

    • 3.4.5 Procedure of migration from an environment where both database and Reliable Messaging are not used to an environment where database is used and Reliable Messaging is not used

    • 3.4.6 Procedure of migration from an environment where database is used and Reliable Messaging is not used to an environment where both are not used

    • 3.4.7 Procedure of migration from an environment where the database is used and Reliable Messaging is not used to an environment where both are used

  • 3.5 Easy Setup of production environment

    • 3.5.1 Environment that can be set up with the Easy Setup functionality for the HCSC production environment

    • 3.5.2 Flow of system setup using Easy Setup functionality for the HCSC production environment

    • 3.5.3 Executing the Easy Setup functionality for the HCSC production environment

    • 3.5.4 Operating the production environment that was set up with the Easy Setup functionality for the HCSC production environment

    • 3.5.5 Definition files used with the Easy Setup functionality for the HCSC production environment

• 4. Repository Management

  • 4.1 Overview of a repository

    • 4.1.1 Repository information

    • 4.1.2 Directory used as repository

    • 4.1.3 Repository exclusion

    • 4.1.4 Points to be considered

  • 4.2 Exporting Repository Information

  • 4.3 Importing a repository

    • 4.3.1 Import method

    • 4.3.2 Auto-backup at the time of import

    • 4.3.3 Import at the time of version upgrade

  • 4.4 Referencing the repository information

  • 4.5 Referencing difference information of repositories

    • 4.5.1 Preconditions

    • 4.5.2 Display method

    • 4.5.3 Display contents of the difference

  • 4.6 Adding, updating, and deleting a repository using component as a unit

    • 4.6.1 Adding and updating a repository using component as a unit

    • 4.6.2 Deleting a repository using component as a unit

  • 4.7 Updating the repository

• 5. System Operations

  • 5.1 Preparation for HCSC server operations

    • 5.1.1 Logging In

    • 5.1.2 Logging Out

  • 5.2 Points to be noted at the timeofsystem operations

  • 5.3 HCSC Server Operations

    • 5.3.1 Flow of operations

    • 5.3.2 Starting a Database

    • 5.3.3 Starting PRF

    • 5.3.4 Starting HCSC server

    • 5.3.5 Starting HTTP Server

    • 5.3.6 Starting Service Adapters

    • 5.3.7 Starting Business Processes

    • 5.3.8 Starting user-defined receptions

    • 5.3.9 Starting standard receptions

    • 5.3.10 Checking the Database Status

    • 5.3.11 Checking the PRF Status

    • 5.3.12 Checking the HTTP Server Status

    • 5.3.13 Checking the Manager status

    • 5.3.14 Checking the HCSC server setup information

    • 5.3.15 Checking the HCSC server information

    • 5.3.16 Checking Resource Operation Information of the HCSC Server

    • 5.3.17 Checking the service adapter information

    • 5.3.18 Checking the business process information

    • 5.3.19 Checking the information of user-defined reception

    • 5.3.20 Performing cache of the definition information of the business process

    • 5.3.21 Changing HCSC Server Definitions

    • 5.3.22 Changing the definition information of user-defined reception

    • 5.3.23 Changing the configuration of HCSC components

    • 5.3.24 Changing the Component Service Connection Point

    • 5.3.25 Changing the Flow Control Value

    • 5.3.26 Changing the Communication Timeout Value for Invoking Service Modules

    • 5.3.27 Changing resource adapter properties

    • 5.3.28 Changing the definition information of HCSC components

    • 5.3.29 Viewing a list of work folders

    • 5.3.30 Deleting the work folder

    • 5.3.31 Viewing the information about a common folder

    • 5.3.32 Deleting the files in a common folder

    • 5.3.33 Terminating the Standard Reception

    • 5.3.34 Stopping the user -defined reception

    • 5.3.35 Terminating the Service Adapter

    • 5.3.36 Terminating the Business Process

    • 5.3.37 Terminating the HTTP Server

    • 5.3.38 Terminating the HCSC Server

    • 5.3.39 Terminating PRF

    • 5.3.40 Terminating a Database

  • 5.4 HCSC server operations (for FTP linkage)

    • 5.4.1 Flow of FTP linkage system operations

    • 5.4.2 Starting the HCSC server

    • 5.4.3 Starting FTP inbound adapters

    • 5.4.4 Starting HCSC components

    • 5.4.5 Starting the standard reception

    • 5.4.6 Starting the FTP reception

    • 5.4.7 Checking the information of the HCSC server

    • 5.4.8 Checking the information of FTP inbound adapter

    • 5.4.9 Checking the information of HCSC components

    • 5.4.10 Changing the definition information of the HCSC server

    • 5.4.11 Changing the definition information of the FTP inbound adapter

    • 5.4.12 Changing and confirming the user information of the FTP inbound adapter

    • 5.4.13 Changing the definition information of the FTP adapter

    • 5.4.14 Checking and changing the user information of the FTP adapter

    • 5.4.15 Changing the definition information of the file operations adapter

    • 5.4.16 Changing the definition information of FTP reception

    • 5.4.17 Modifying repositories

    • 5.4.18 Acquiring the transfer history

    • 5.4.19 Referencing the work folder

    • 5.4.20 Deleting the work folder

    • 5.4.21 Referencing the information of the common folder

    • 5.4.22 Deleting files in the common folder

    • 5.4.23 Stopping the FTP reception

    • 5.4.24 Stopping the standard reception

    • 5.4.25 Stopping HCSC components

    • 5.4.26 Stopping FTP inbound adapters

    • 5.4.27 Stopping HCSC servers

  • 5.5 Additional operations required for email linkage

    • 5.5.1 Managing the user information

    • 5.5.2 Starting and stopping the mail adapter

    • 5.5.3 Performance tuning ofthe mail adapter

  • 5.6 Operations required to use the JSON-XML transformation function for HTTP communication

    • 5.6.1 Deploying the HTTP reception or HTTP adapter

    • 5.6.2 Checking and setting the definition information

  • 5.7 Operations with a Cluster Configuration

    • 5.7.1 Operations in the load-balancing cluster configuration

    • 5.7.2 Operations Using a High Availability Cluster Configuration

    • 5.7.3 Operations in N-to-1cluster configuration

    • 5.7.4 Notes at the time of cluster configuration

  • 5.8 Operations when you change the IP addressorthe host name after building the environment

    • 5.8.1 When you change the IP address and the host nameof the database operating machine

    • 5.8.2 When you change the IP address or the host name of Web server of the standard reception (synchronous reception (Web service)) and the standard reception (asynchronous reception (MDB(WS-R))

  • 5.9 Operations to suppress Full GC at the time of executing the operation command

    • 5.9.1 When you replace HCSC components by stopping online

    • 5.9.2 When you replace HCSC components online

• 6. Management of Execution Log

  • 6.1 Management of execution log of process instances

    • 6.1.1 Using the Process Instance Execution Log

    • 6.1.2 Searching the execution log of a process instance

    • 6.1.3 Acquiring detailed information from the process instance execution logs

    • 6.1.4 Deleting process instance execution logs

    • 6.1.5 Re-executing process instances

  • 6.2 Managing execution log information table

    • 6.2.1 Acquiring a Backup of the Execution Log Information Table

    • 6.2.2 Operations involving a backup of the execution log information table

• 7. Troubleshooting

  • 7.1 Troubleshooting Procedures

  • 7.2 Failure types and failure information

    • 7.2.1 Information required for investigating errors

    • 7.2.2 Information required to contact the system administrator or the maintenance service

  • 7.3 Acquiring failure information

    • 7.3.1 Output modes and notes for log files and trace files

    • 7.3.2 How to acquire failure information (service platform)

    • 7.3.3 Collecting failure information (for prerequisite products other than a service platform)

  • 7.4 Viewing the failure information that has been output

    • 7.4.1 Message log

    • 7.4.2 Request trace

    • 7.4.3 Performance Analysis Trace

    • 7.4.4 User message trace

    • 7.4.5 Activity trace

    • 7.4.6 Debug information

    • 7.4.7 Maintenance log and trace

    • 7.4.8 Message log for user-authentication information management commands

  • 7.5 Troubleshooting During System Setup and Unsetup

    • 7.5.1 Investigating failures that occur during software setup in the execution environment

    • 7.5.2 Failure investigations when executing setup and unsetup

    • 7.5.3 How to recover when executing HCSC server setup and unsetup

    • 7.5.4 How to recover when deploying and deleting HCSC Components

  • 7.6 Troubleshooting a failure that occurred when an operation was performed

    • 7.6.1 Investigating failures in screen operations of operating environment and command operations

    • 7.6.2 How to perform recovery when file input and output has failed

  • 7.7 Troubleshooting during service component invocation request

    • 7.7.1 Troubleshooting when executing Web service (SOAP communication)

    • 7.7.2 Troubleshooting when executing SessionBean

    • 7.7.3 Troubleshooting when executing MDB (WS-R)

    • 7.7.4 Troubleshooting when executing MDB (DB queue)

    • 7.7.5 INTENTIONALLY DELETED

    • 7.7.6 INTENTIONALLY DELETED

    • 7.7.7 Troubleshooting when executing file adapter

    • 7.7.8 INTENTIONALLY DELETED

    • 7.7.9 Troubleshootingwhen executing Message Queue reception

    • 7.7.10 Troubleshootingwhen executing Message Queue

    • 7.7.11 Troubleshooting in FTP linkage system

    • 7.7.12 Troubleshooting in a system that uses file event linkage

    • 7.7.13 Troubleshooting when executing the mail adapter

    • 7.7.14 Troubleshooting when executing the HTTP reception

    • 7.7.15 Troubleshooting when executing the HTTP adapter

    • 7.7.16 Troubleshooting when the JSON-XML transformation function is used for HTTP linkage

    • 7.7.17 Troubleshooting when the command adapter is executed

    • 7.7.18 Troubleshooting when the SFTP adapter is executed

    • 7.7.19 Troubleshooting when there is a mistake in user message

    • 7.7.20 Analyzing failure in entire system

    • 7.7.21 Troubleshooting when executing the business process

    • 7.7.22 Troubleshootingwhen executing the data transformation

  • 7.8 Monitoring and reporting failures (JP1 linkage function)

    • 7.8.1 Monitoring errors using the JP1 linkage functionality

    • 7.8.2 JP1 event detail information notified from Service platform

  • 7.9 Restoration methods when HCSC server error occurred

    • 7.9.1 Restoration methods when system operations of HCSC server cannot be executed

    • 7.9.2 How to recover during cluster configuration

    • 7.9.3 Backup and recovery of operating environment

    • 7.9.4 How to restore when deadlock occurs

  • 7.10 Error analysis using message tracking

    • 7.10.1 Examples applicable for message tracking functionality

    • 7.10.2 Starting message tracking

    • 7.10.3 Displaying performance analysis trace

    • 7.10.4 List display of root application information

    • 7.10.5 Sorting performance analysis trace

    • 7.10.6 Displaying performance analysis trace collection points

  • 7.11 Handling of an exception that occurs in the service adapter

    • 7.11.1 Settings for converting an exception into a fault message

    • 7.11.2 Schema file defining the fault messages

  • 7.12 Failure analysis using faults

    • 7.12.1 Schema file for defining fault messages

    • 7.12.2 Settings to output user message trace

  • 7.13 Operation when OutOfMemoryError occurs

    • 7.13.1 Function to suppress the effect on business

    • 7.13.2 Points to be considered during UOC execution

• Appendixes

  • A. Changing the Service Coordinator administrator (in UNIX)

    • A.1 Change procedure

    • A.2 Notes

  • B. Operations that can be performed from the GUI and CLI (in the operating environment)

  • C. Database Table Information

    • C.1 Table information about process instance execution log management

    • C.2 Table Information About Message Execution Log Management

    • C.3 Table information about execution environment setup

    • C.4 Precautions to be taken when user creates his own table or index

  • D. Setting up the SQL Script File

    • D.1 Types and storage destinations of SQL script files

    • D.2 Method of setting SQL script file

    • D.3 Points to be considered when setting up SQL script file

  • E. Statistical Information of Resource Statistics for HCSC Server

    • E.1 Statistics file output

    • E.2 Viewing statistics

    • E.3 Types of statistics for resources

  • F. Messages that Notify JP1 Event

    • F.1 Messages from KDEC00001 to KDEC19999 (Messaging infrastructure related messages)

    • F.2 Messages from KDEC20000 to KDEC39999 (Business process infrastructure related messages)

    • F.3 Messages from KDEC40000 to KDEC59999 (Data transformation infrastructure related messages)

    • F.4 Messages from KDEC60000 to KDEC79999 (DB adapter related messages)

    • F.5 Messages from KDEC80000 to KDEC80399 (File operations adapter related messages)

    • F.6 Messages from KDEC80400 to KDEC80499 (HTTP reception related messages)

    • F.7 Messages from KDEC80500 to KDEC80999 (Mail adapter related messages)

    • F.8 Messages from KDEC81000 to KDEC81499 (HTTP adapter related messages)

    • F.9 Messages from KDEC81500 to KDEC81799 (command adapter related messages)

    • F.10 Messages from KDEC82000 to KDEC82399 (SFTP adapter related messages)

    • F.11 Messages from KDEE10000 to KDEE13999 (TP1 adapter related messages)

    • F.12 Messages from KDEF10000 to KDEF30999 (Object Access adapter related messages)

    • F.13 Messages from KDEG20000 to KDEG30999 (File adapter related messages)

    • F.14 Messages from KDEH20000 to KDEH30999 (Message Queue adapter related messages)

    • F.15 Messages from KDEK20000 to KDEK30999 (FTP adapter related messages)

    • F.16 Messages from KECK31794 to KECK31799 (messages related to SOAP mode settings)

    • F.17 Messages from KECK72001 to KECK74999 and KECT01001 to KECT91999 (messages related to the binary format definition, data transformation, and message dialog boxes)

    • F.18 Messages from KEOS50000 to KEOS59999 (HCSC-Manager related messages)

  • G. Migration from an Old Version

    • G.1 Versions supporting repository migration

    • G.2 Migration procedure for a new installation

    • G.3 Migration procedure for an update installation

    • G.4 Migration procedure for a rolling update

    • G.5 Setup after an update (in the case of an update from a version earlier than 07-50)

  • H. Performing Repository Migration from an Old Version in the Operating Environment

    • H.1 Versions supporting repository migration

    • H.2 Repository migration procedure in the operating environment during a new installation

    • H.3 Repository migration procedure in the operating environment during update installation

    • H.4 Repository migration procedure in the operating environment during rolling update

    • H.5 Setup after update

  • I. Estimating resource requirements

    • I.1 Estimating the required number of file descriptors

    • I.2 Estimating the number of threads

  • J. Version changes

    • J.1 Changes in the specifications of Service Platform from version 09-71

    • J.2 Changes in the specifications of Service Platform from version 09-87

    • J.3 List of changes in specifications from earlier versions

  • K. Glossary

• Index

To Page Top