Method for specifying the component common UOC class is as follows:

• When you specify the class to be invoked only with specific components
  Specify UOC class for individual components.
  Set reception ID of reception and service ID of service adapter in (UOC class invoking source). In this case, even if you have specified UOC class in the reception type or adapter type, only the UOC class specified in individual component is invoked.
  
• When you want to invoke the same UOC class in the specified component type
  Specify UOC class in the reception type or adapter type.
  Specify invoking source type ID in the invoking source of UOC class.
  Following table describes the invoking source type ID of reception.
  

  Table H-1 TableInvoking source type ID list (reception)

  Reception		Invoking source type ID
  Standard reception	Standard reception (Web service)	reception.standard.soap
  	Standard reception (SessionBean)	reception.standard.ejb
  	Standard reception(MDB(WS-R))	reception.standard.wsr
  	Standard reception (MDB(DB queue))	reception.standard.dbq
  User-defined reception	SOAP reception	reception.urecp.soap
  	TP1/RPC reception	reception.urecp.tp1
  	FTP reception	reception.urecp.ftp
  	HTTP reception	reception.urecp.http
  	Message Queue reception	reception.urecp.mq
  	Custom reception	reception.urecp.rcpfw

  Following table describes the invoking source type ID of the service adapter.
  

  Table H-2 TableInvoking source type ID list (service adapter)

  Service adapter	Invoking source type ID
  SOAP adapter	adapter.soap
  SessionBean adapter	adapter.ejb
  MDB (WS-R) adapter	adapter.wsr
  MDB (DB queue) adapter	adapter.dbq
  DB adapter	adapter.db
  TP1 adapter	adapter.tp1
  File adapter	adapter.ff
  Object Access adapter	adapter.oa
  Message Queue adapter	adapter.mq
  FTP adapter	adapter.ftp
  File operation adapter	adapter.fop
  Mail adapter	adapter.mail
  HTTP adapter	adapter.http
  General custom adapter	adapter.custom

• When UOC class is specified in reception type or adapter type, but UOC class is not invoked from a specific service
  Makes the class path of the specific service as blank. UOC class is not invoked from that service.
  Example) ADP3=
  

Operations regarding description of property file for component common UOC are as follows:

• You must use ISO-8859-1 character coding.
• Data till linefeed is considered as value.
• Lines starting with # are considered as comments.
• Leading and trailing spaces of class path are ignored.
• You cannot add character string such as comment, after the class path. If you add, entire text including the added comment is parsed as the class path and this may lead to occurrence of exception such as class is not found.
• If you specify multiple class paths for 1 invoking source, only one of the class paths is activated.
• When you set a single class path for multiple invoking sources, single class instance is used in the concerned invoking source.
• UOC is not invoked for the component for which class path of UOC has not been set.
• If class corresponding to the already set class path does not exist, UOC is not invoked.
• As component dependency existence is not checked, instances of UOC class are created, even when you specify service ID or reception ID of non-existing service adapter.
• Changes in property file are reflected after you restart HCSC server.