The GIOP marshaler is configured by an SstGiopMarshalerConfiguration. There are a number of configuration options:
When setting up a local space for use with IIOP, the space configuration must use SstGiopRemoteReference for its remoteReferenceClass setting. You can use the instance method giopProxyConfiguration in SstSpaceConfiguration to create and return a suitable space configuration.
Additionally, you can use the iiopConfiguration method in SstInvocationConfiguration to get a copy of the default configuration settings for IIOP method invocation. You modify the result of this method, rather than build invocation configurations explicitly.
You can modify most of the invocation configuration options. There are, however, two options which must have IIOP-specific settings: marshaler and replyFutureClass. The marshaler option must be set to SstGiopMarshalerConfiguration (for example, SstGiopMarshaler defaultConfiguration) and the replyFutureClass option set to SstGiopReplyFuture. You will rarely need to alter the default settings for IIOP invocation. SST provides a pre-defined invocation configuration scheme called iiop. You can vary the settings for an option in this configuration, but you should always use the SstGiopReplyFuture setting as an SstGiopMarshalerConfiguration.
In certain situations, SST needs a configuration scheme while building references to remote CORBA objects. There are cases in which the system knows very little about the machine hosting the remote object (when there is no existing connection to, or space definition for, the machine). In such cases, SST uses information supplied in the application context. In particular, the IIOP infrastructure needs to know the scheme name to use when building a URL to the remote machine. You can specify the default scheme using the SstApplicationContext protocol shown below. If the value is not set then the default of iiop is used.
If the default IIOP configuration settings are not appropriate in your environment, you can overwrite them in the scheme registry by storing your own IIOP invocation configuration. Be careful, however, as all users use this default IIOP scheme if they do not specify an iiopInvocationScheme setting for their application context.
See SstPingPongIiop for example configurations.