Debugging C++ components  Creating C++ components for multiplatform clusters

Chapter 14: Creating CORBA C++ Components

Running C++ components externally

EAServer’s C++ component model allows you incorporate legacy C and C++ business logic code into a component. However, if legacy code is unstable, it can cause the server to crash.

Beginning in version 4.0, you can configure C++ components to execute within a dedicated external process. EAServer spawns a subprocess to execute the component, and issues component invocations using interprocess communication.

NoteBeginning in EAServer 5.1, you can use the more general external model described in “Running components externally”. The C++ executable model described here is supported for backward compatibility.


Because external components execute in a different process than the host server, they cannot use the following features:

Configuring a component to run externally

To run your C++ component externally, configure the following component properties:

Building and deploying the external component executable

Before you can build an external component executable, you must generate a skeleton. The skeleton for an external component is different than for a component that runs in-process, so regenerate skeletons if you have changed the component properties to run externally. “Generating required C++ files” describes how to generate the C++ code.

The executable indicated by the component properties General / C++ Executable must be deployed in the EAServer cpplib directory, as well as the library specified by the DLL Name field. The generated Makefile builds the library and executable and copies both to the cpplib directory when you run the “all” make target.

Copyright © 2005. Sybase Inc. All rights reserved. Creating C++ components for multiplatform clusters