uCosminexus Service Platform, Overview
The following figure shows the timers that can be set up on an HCSC server.
Figure 4-1 Timers that can be set up
Each number in Figure 4-1 Timers that can be set up indicates the following timers:
The method for setting up a timer differs depending on the connection destination and the protocol.
When connecting to a service component (Web Services), you can set up timers used for writing, reading, and establishing a connection.
The methods for setting up a timeout value are different depending on whether you are using the SOAP Communication Infrastructure or the JAX-WS engine. The following describes the setup method for each case.
This subsection describes how to set up a timeout value when using the SOAP Communication Infrastructure. You can set up the timeout value for the entire HCSC server or separately for each service adapter.
Table 4-1 Timer (Web Services) settings for the entire HCSC server (SOAP Communication Infrastructure)
Value | Key name | Default value (seconds) |
---|---|---|
Write timeout value for the socket of a server client | c4web.application.identifier.socket_write_timeout | 60 |
Read timeout value for the socket of a server client | c4web.application.identifier.socket_read_timeout | 300 |
Connection timeout value for the socket of a server client | c4web.application.identifier.socket_connect_timeout | 60 |
Table 4-2 Timer (Web Services) settings for each service adapter (SOAP Communication Infrastructure)
Value | Key name | Default value (seconds) |
---|---|---|
Write timeout value for the socket of a client | c4web.application.socket_write_timeout | 60 |
Read timeout value for the socket of a client | c4web.application.socket_read_timeout | 300 |
Connection timeout value for the socket of a client | c4web.application.socket_connect_timeout | 60 |
To define the timeout value in the operating environment for the service adapter that is already deployed on the HCSC server, use the cscsvcctl command to change the communication timeout value of the service component invocation. For details about how to change a timeout value, see 5.3.26 Changing the communication timeout value for invoking a service component in the Service Platform Setup and Operation Guide. For details about how to use the cscsvcctl command, see cscsvcctl (Managing the service information) in the Service Platform Reference Guide.
Table 4-3 Changing the set value of the timer (Web Services) (SOAP Communication Infrastructure)
Value | Key name |
---|---|
Write timeout value | cluster-name.service-ID.WebService.c4web.application.socket_write_timeout |
Read timeout value | cluster-name.service-ID.WebService.c4web.application.socket_read_timeout |
Connection timeout value | cluster-name.service-ID.WebService.c4web.application.socket_connect_timeout |
This subsection describes how to set up a timeout value when using the JAX-WS engine. You can set up the timeout value for the entire HCSC server or separately for each service adapter.
Table 4-4 Timer (Web Services) settings for the entire HCSC server (JAX-WS engine)
Value | Key name | Default value (milliseconds) |
---|---|---|
Read timeout value for the socket of a server client | com.cosminexus.jaxws.request.timeout | 300000 |
Connection timeout value for the socket of a server client | com.cosminexus.jaxws.connect.timeout | 60000 |
Table 4-5 Timer (Web Services) settings for each service adapter (JAX-WS engine)
Value | Key name | Default value (seconds) |
---|---|---|
Read timeout value for the socket of a client | com.cosminexus.csc.request.timeout | 300 |
Connection timeout value for the socket of a client | com.cosminexus.csc.connect.timeout | 60 |
To define the timeout value in the operating environment for the service adapter that is already deployed on the HCSC server, use the cscsvcctl command to change the communication timeout value of the service component invocation. For details about how to change a timeout value, see 5.3.26 Changing the communication timeout value for invoking a service component in the Service Platform Setup and Operation Guide. For details about how to use the cscsvcctl command, see cscsvcctl (Managing the service information) in the Service Platform Reference Guide.
Table 4-6 Changing the set value of the timer (Web Services) (JAX-WS engine)
Value | Key name |
---|---|
Read timeout value | cluster-name.service-ID.WebService.com.cosminexus.csc.request.timeout |
Connection timeout value | cluster-name.service-ID.WebService.com.cosminexus.csc.connect.timeout |
The timer (Session Bean) used when connecting to a service component can be set up for the entire HCSC server or separately for service adapters. The following describes the setup methods.
Table 4-7 Timer (Session Bean) settings for the entire HCSC server
Value | File to be set up | Key name | Default value (seconds) |
---|---|---|---|
Timeout value enabled for all RMI-IIOP communications | User property file for a J2EE server (usrconf.properties) | ejbserver.rmi.request.timeout | 0 (A timeout will not occur.) |
Timeout value for communication with the CORBA Naming Service component | ejbserver.jndi.request.timeout | 0 (A timeout will not occur.) |
Table 4-8 Timer (Session Bean) settings for each service adapter
Value | Key name | Default value (seconds) |
---|---|---|
Invocation timeout value | c4web.application.ejb_timeout | 0 (A timeout will not occur.) |
To define the timeout value in the operating environment for the service adapter that is already deployed on the HCSC server, use the cscsvcctl command to change the communication timeout value of the service component invocation. For details about how to change a timeout value, see 5.3.26 Changing the communication timeout value for invoking a service component in the Service Platform Setup and Operation Guide. For details about the cscsvcctl command, see cscsvcctl (Managing the service information) in the Service Platform Reference Guide.
Table 4-9 Changing the set value of the timer (Session Bean)
Value | Key name |
---|---|
Invocation timeout value | cluster-name.service-ID.SessionBean.c4web.application.ejb_timeout |
The timer (Web Services) used when connecting to the HCSC server is set up on the service requester machine. You can set up the timer for the entire machine on which the service requester is running or separately for service requesters.
The setup method is described separately for the cases where you use the SOAP Communication Infrastructure and where you use JAX-WS engine.
This subsection describes how to set up a timeout value when using the SOAP Communication Infrastructure. You can set up the timeout value for the entire service requester machine or separately for each service requester.
This subsection describes how to set up a timeout value when using the JAX-WS engine. You can set up the timeout value for the entire service requester machine or separately for each service requester.
The timer (Session Bean) used when connecting to the HCSC server can be set up for the entire machine on which the service requester is running or separately for service requesters. The following describes the setup methods:
The timer for transactions within the HCSC server is set up for the entire HCSC server. Set up the timeout value in the EJB container of Application Server on the machine running the HCSC server. For details about parameters to be set up, see 2.4 usrconf.properties (User property file for Java applications) in the Application Server Definition Reference Guide.
Table 4-10 Timer settings for transactions within the HCSC server
Value | File to be set up | Key name | Default value (seconds) |
---|---|---|---|
Transaction timeout value of transactions started on the J2EE server | User property file for a J2EE server (usrconf.properties) | ejbserver.jta.TransactionManager.defaultTimeOut | 180 |
All Rights Reserved. Copyright (C) 2015, Hitachi, Ltd.