Deployment Problems

During deployment, the Agent verifies connections to the defined services and the package metadata; therefore, the service configuration must be complete and correct before business processing can occur.

The following are necessary for deployment:

The directory services ASA must be running.
The Agent must be running.
Services must be fully defined, including operations and ports.

Use the agent.log file to troubleshoot specific problems.

Receive configuration error


Error	All required configuration is not completed.
Resolution	Verify that all runtime instance transports have correctly assigned values.

Error	GenerateOhioConfiguration failed to generate configuration properties
Resolution	This error can be an indication of the following: That a deployed package has been bound to an input transport that has been deleted from the Endpoint Manager. If a transport endpoint has been deleted from the Endpoint Manager, but is still defined as an input transport for a runtime instance, the package cannot be deployed and run. To correct this problem, do the following: 1. Create a Messaging transport in Endpoint Manager with the same name and transport type as the deleted transport. For example, if the deleted endpoint was a JMS transport named JMS_IN, you need to create a JMS transport named JMS_IN. 2. In the Server Explorer, open the Properties for the runtime instance. 3. Expand the Input Transports node. 4. De-select the transport from the list of defined input transports for the runtime instance. 5. Go back to the Endpoint Manager and delete the Messaging Transport definition. That the input transport defined for a runtime instance has been changed and the package redeployed to the runtime instance. In this case, the wsdl for the messaging services shows only the recently selected transport (versus the originally defined transport) and the Server Explorer shows both the old transport and new transport defined for the runtime instance. To correct this problem, do the following: 1. In the Server Explorer, open the Properties for the runtime instance. 2. Expand the Input Transports node. 3. De-select the transport from the list of defined input transports for the runtime instance. 4. Go back to the Endpoint Manager and delete the Messaging Transport definition if necessary.