uCosminexus Service Platform, Overview
Index
[Numbers]
[A][B][C][D][E][F][G][H][I][J][L][M][N][O][P][R][S][T][U][V][W][X]
- (Numbers)
- 1-to-1 node switching system
- (A)
- accessing database using DB adapters
- access to message queues using Message Queue adapter
- activity
- activity (functionality for creating business processes)
- add (write mode)
- Arranging business processes in a hierarchy
- asynchronous execution of activity that is defined after reply activity
- authentication when sending email messages from mail adapter
- (B)
- basic structure (invoking service components)
- batch (read mode)
- business process access control
- business process flow
- business process functionality
- business process, managing execution status of
- business processes that are not to be made persistent
- business processes that are to be made persistent
- business processes, (functionality for creating business processes)
- (C)
- Cache functionality for XML messages
- catching fault by using SOAP fault operation definition file
- changing connection destination of service components
- changing timeout value of service components
- Changing value of user message wherein UOC is used
- checking file size after sending and receiving files
- checking file size after sending and receiving files
- checking operation status from application
- cluster software
- combination of variables (message type) when data is not transformed
- commands supported in FTP integration
- communication model of business process
- communication model and business processes that can be used with FTP receptions
- communication through proxy servers
- communication using chunk transmission
- communication using connection continuity (Keep-Alive)
- complementing name space prefixes specified in attribute values of XML messages
- compressing and extracting HTTP body
- configuration pattern of operating environment in cluster configuration
- configuring cluster of HCSC server
- connecting to a system by using a general custom adapter
- connecting to database
- connecting to mail server
- connecting to OpenTP1
- connecting to services by using database queue
- connecting to services by using Web Services (SOAP communication)
- connecting to services using Session Beans
- connecting to services using WS-R (WS-Reliability)
- connecting to system by using custom reception
- connecting to client using HTTP communication
- connecting to FTP client and FTP server
- connecting to message queues
- connecting to services using HTTP communication
- connecting to system handling file
- connection with Object Wrapper system
- cookie information in (Web service (SOAP communications))
- correlation set (functionality for creating business processes)
- corresponding relation between request message (header) and HTTP adapter execution environment (common) property file
- creating service requester
- creatingservice adapters (functionality for creating service adapters)
- creating work folder and intermediate files
- CTM (redundant configuration of HCSC server)
- custom adapter
- (D)
- data transformation definition (functionality for creating data transformation definition)
- databases that can be connected
- data compression function (TP1/Client/J)
- data trace (TP1/Client/J)
- data transformation (business process)
- data validation functionality
- dead message queue (MDB (DB queue))
- dead message queue (MDB (WS-R)
- debug trace (TP1/Client/J)
- defined exception
- defining message format of any format
- deployment definition (functionality for defining deployment)
- deployment of HCSC components
- design for troubleshooting
- detailed information of process instance execution log, referencing
- detecting failure by linking with JP1/IM
- development environment, functional overview of
- dynamically change in connection destination information for DB adapter
- dynamic change in connection destination in Web service (SOAP communication)
- (E)
- element
- encoding and / decoding HTTP requests and HTTP responses (HTTP reception)
- error trace (TP1/Client/J)
- example of system using HTTP adapter
- example of file adapter operation
- example of HTTP reception configuration
- example of Message Queue reception configuration
- example of online system using HTTP reception
- example of sending GET method request (HTTP reception)
- example of sending POST method request (HTTP reception)
- examples of file transfer patterns using FTP integration
- exclusive control while reading and writing files
- exclusive reference
- exclusive update
- executing LIST and NLST commands by specifying list command options
- executing FTP commands
- execution environment, functional overview of
- (F)
- failure analysis functionality
- file compression operation
- file expansion operation
- file or folder deletion operation
- file replication operation
- file access using common folder
- file access using work folder
- file access using work folder and common folder
- file conversion operation
- file conversion using character code conversion UOC
- file format handled as binary data in file adapter
- file format handled as XML data in file adapter
- file formats that can be used in adapters
- file operations adapter
- file operations adapter functionality
- fixed length format
- flow of checking operation status
- flow of identifying location of system exception by using general fault
- flow of invoking service component with message format different from service component side
- flow for distributed development using import component function
- flow of development in FTP integration system
- flow of FTP adapter processing
- flow of process when any format is set
- folder specification used for sending and receiving files
- FTP adapter
- FTP adapter functionality
- FTP command reply timeout (FTP adapter)
- FTP inbound adapter
- FTP inbound adapter functionality
- FTP reception
- FTP reception functionality
- function (functionality for creating data transformation definition)
- functionality for connecting to various types of systems
- functionality for creating business processes
- functionality for creating data transformation definitions
- functionality for creating message format
- functionality for creating user-defined reception
- functionality for debugging business processes
- functionality for defining deployment
- functionality for distributing services
- functionality for executing business processes
- functionality for managing execution logs
- functionality for setting up execution environment
- functionality of Cosminexus Service Platform
- functionality used by linking with other products
- functionality for acquiring failure information
- functionality for deploying HCSC components
- functionality for deploying to starting or stopping to deleting HCSC components, in a batch
- functionality for Failure Checking
- functionality for invoking various services
- functionality for managing operations
- functionality to transfer files by integrating with FTP (FTP integration)
- function for changing dynamic definition (TP1/Client/J)
- function for connecting to DCCM3 (TP1/Client/J)
- function for fixing reception port (TP1/Client/J)
- function for receiving one-way communication from server (TP1/Client/J)
- (G)
- general faults for converting system exceptions to faults
- generating request ID
- glossary
- (H)
- HA monitor (redundant configuration of HCSC server)
- HCSC component validation
- host switching function (TP1/Client/J)
- HTTP client and Web server supported by HTTP reception
- HTTP reception request process
- HTTP reception response process
- HTTP request body process (HTTP request)
- HTTP request header process (HTTP reception)
- HTTP response body process (HTTP reception)
- HTTP response header process (HTTP reception)
- (I)
- identification information
- idle timeout (FTP inbound adapter)
- Importing the BPEL created in BPMN tool
- importing repositories at time of distributed development
- inheriting Cookie information using HTTP adapter
- inheriting HTTP header in (Web service (SOAP communication))
- invoking service components (Basic procedure)
- invoking service components (flow of messages (MDB (DB queue)))
- invoking service components (flow of messages (MDB (WS-R)))
- invoking service components (handling response message (MDB (DB queue)))
- invoking service components (handling response message (MDB (WS-R)))
- invoking service components (relationship between user messages and stubs)
- invoking service components (relationship between user messages and WSDL)
- invoking service components using HTTP adapter
- invoking service components using Message Queue reception
- invoking service component using HTTP reception
- (J)
- Java invocation (business process)
- (L)
- length tag format
- linkage with JP1
- Listen timeout (FTP adapter)
- load balancer
- load-balancing functionality (redundant configuration of HCSC server)
- (M)
- mail information that can be set on mail adapter
- management of execution logs by linking with HiRDB
- managing files and folders used for each operation
- managing the mail adapter timer
- managing FTP commands executed before and after transfer and list
- managing HTTP adapter timer
- managing HTTP reception timer
- managing HTTP request files
- mapping (functionality for creating data transformation definition)
- mapping between general fault messages and message log
- mechanism of business process
- message tracking functionality
- message format (functionality for creating message format)
- message log
- method trace (TP1/Client/J)
- modes for file operations
- monitoring processes through JP1
- monitoring timeout [FTP inbound adapter]
- monitoring timeout [FTP reception]
- multiplicity
- Multiplicity of the HCSC server
- Multiplicity related to database access
- Multiplicity related to Web Services (SOAP communication)
- multiplicity related to XML analysis process
- (N)
- names and number of queues (MDB (DB queue))
- names and number of queues (MDB (WS-R))
- new (write mode)
- node switching when error occurs
- (O)
- Object Access adapter
- obtaining file list from FTP server
- operations and FTP commands supported in FTP reception
- operations supported by file operations adapter
- output contents of trace file (TP1/Client/J)
- overview of business processes
- overview of data validation functionality
- overview of component-common UOC
- overview of error design
- overview of FTP integration
- overview of TP1/Client/J definition
- overview of WebSphere MQ
- (P)
- packaging
- packaging
- partitioning storage of execution logs
- performance analysis trace
- performance analysis trace (TP1/Client/J)
- performance upgrade function
- points to be considered for distributed development
- points to be considered on using FTP integration
- points to be considered when using HTTP reception
- points to be considered (when using SessionBean adapter)
- pre-cache function of business process
- precautions on checking operation status
- precautions on using user message trace functionality
- preconditions (connecting to mail server)
- preconditions (connecting to services using HTTP communication)
- preventing duplicate message delivery
- procedure for invoking service components
- procedure of file transfer from FTP client to FTP server (when asynchronous business processes are used)
- procedure of file transfer from FTP client to FTP server (when synchronous business processes are used)
- process instance execution log, deleting
- process instance execution log, managing
- process instance execution log, searching
- process instance, re-executing
- process instances (operating with business processes)
- (R)
- re-executing business processes (commands)
- re-executing business processes (service requesters (Session Bean))
- re-executing business processes (service requesters (SOAP communication))
- re-executing business processes (windows in operation environment)
- re-executing business process
- reading and writing files using adapter
- read mode
- reception and response (business process)
- redundant configuration of HCSC server (cluster software)
- redundant configuration of HCSC server (load-balancing functionality)
- redundant configuration of HCSC server (N-to-1 cluster configuration)
- relation between HTTP requests and request messages
- relation between HTTP responses and response messages
- relation between Message Queue reception and business processes
- relation between Message Queue reception and MQ resource adapter
- relation between Message Queue reception and queues
- relationship with application server (EJB containers)
- relationship with Reliable Messaging (MDB (DB queue))
- relationship with Reliable Messaging (MDB (WS-R))
- Relationship with the Communication Infrastructure for Web Services
- remote procedure call (TP1/Client/J)
- repetition (business process)
- request trace
- request and response messages for each operation
- request line process (HTTP reception)
- role of correlation set
- roles of variables
- (S)
- scope of FTP integration
- scoping of data validation function
- secure connection using WWW authentication
- send option of Message Queue reception
- separator format
- service invocation (business process)
- service adapter
- service requester
- setting up cluster
- setting up data validation functionality
- setting up HCSC server (functionality for setting up execution environment)
- setting up user message trace functionality
- setting message rollback frequency (Message Queue reception)
- setting up timer
- setting up timer for HCSC Server
- simultaneous conversion of multiple data records
- SOAP message configuration in (Web service (SOAP communication))
- source host specification function (TP1/Client/J)
- specification method for transfer commands
- standby processing (business process)
- standby processing using business processes
- status codes (HTTP reception)
- status line process (HTTP reception)
- system using mail adapter
- system configuration for using FTP integration
- (T)
- TCP/IP communication function(TP1/Client/J)
- TCP/IP connection establishment monitoring function (TP1/Client/J)
- timeout in data reception (FTP inbound adapter)
- timeout in data transfer or acquisition (FTP adapter)
- timeout in data transmission (FTP inbound adapter)
- timeout in establishing control connection (FTP adapter)
- timeout in establishing data connection (FTP inbound adapter)
- timeout in establishing data connection (FTP adapter)
- timeout in obtaining lock (FTP adapter)
- timer design
- timer management
- timers that can be set up on an HCSC server
- TP1/Client/J definition
- TP1/Client/Jenvironment definition details
- TP1/Client/J function
- TP1/Web connection function (TP1/Client/J)
- transaction (MDB (DB queue))
- transaction (MDB (WS-R))
- transaction (Session Bean)
- transaction (Web Services (SOAP communication))
- transaction design
- transaction of business process
- transaction of scope activity
- transactions when OFF is specified for compatibility with business process status and ON is specified for compatibility with invoke service activity status
- transactions when OFF is specified in both compatibility with business process status and compatibility with invoke service activity status
- transactions when on is specified in compatibility with business process status
- transactions when using mail adapter
- transactions of invoke service activity
- transactions of reply activity
- transactions performed while using Message Queue reception
- transactions to be performed while using HTTP reception
- transactions when FTP reception is used
- transaction when you select settings to commit at start time and end time of scope
- transaction control (TP1/Client/J)
- transfer of files from FTP client to another FTP client
- transfer of files from FTP server to FTP client
- transfer of files from FTP client to FTP server
- troubleshooting design
- troubleshooting function (TP1/Client/J)
- troubleshooting functionality
- troubleshooting of TP1/Client/J
- types of variables
- (U)
- UAP trace (TP1/Client/J)
- usage example of component-common UOC
- user-defined reception (functionality for creating user-defined reception)
- user message trace functionality
- (V)
- variable
- (W)
- while using message queue reception
- Windows Server Failover Cluster (redundant configuration of HCSC server)
- write mode
- (X)
- XA resource services function (TP1/Client/J)
- XML format
- XML parser pool function of data transformation process
All Rights Reserved. Copyright (C) 2015, Hitachi, Ltd.