When you start the connector, the init() method reads the configuration properties that were set using System Manager's Connector Configurator Express. For proper functioning, be sure not to disable connector polling (connector polling is enabled by default). The sections below describe what occurs.
If you specify the ProxyServer connector-specific property, the connector sets up the proxy system properties. A proxy server is used with the SOAP/HTTP-HTTPS protocol handler for request processing only. The connector also traces each of the system properties it sets up. For more on the ProxyServer property, see Connector-specific configuration properties.
The connector-specific property JNDI specifies the JNDI to be used by the connector. The connector uses JNDI to lookup the JMS Connection Factory object. If JNDI " LookupQueuesUsingJNDI is set to true, the connector looks up JMS queue objects using JNDI.
If you do not want to use SOAP/JMS (the SOAP/JMS protocol listener and SOAP/JMS protocol handler), you need not specify JNDI properties. If you specify JNDI properties and the connector cannot initialize JNDI, the connector terminates. Note that the connector will not initialize JNDI unless all of the following connector-specific JNDI properties are specified:
During startup the connector instantiates the protocol listener framework and initializes it. This framework reads the connector-specific property ProtocolListenerFramework, The connector then reads the value of WorkerThreads and RequestPoolSize connector properties. If the ProtocolListenerFramework property is unspecified or missing, the connector cannot receive requests from web service clients and logs a warning.
The connector next reads the ProtocolListenerFramework " ProtocolListeners property. All the first-level properties of the ProtocolListeners property represent protocol listeners. The protocol listener framework attempts to load and initialize each of the listeners and traces them. If persistent event capable, the listener attempts an event recovery.
The connector reads the connector-specific property ProtocolHandlerFramework and instantiates and initializes the protocol handler framework. If this property is missing or not set properly, the connector cannot perform request processing and logs a warning. Next the connector reads all the ProtocolHandlerFramework " ProtocolHandlers properties, which correspond to protocol handlers, and attempts to load, initialize, and trace them. Note that the protocol handlers are loaded during connector initialization and are not instantiated when a collaboration makes a service request. The protocol handlers are multi-thread safe.