user manual

46 BES Developer’s Guide
Apache to Borland web container connectivity
Additional Apache IIOP directives
The following optional additional directives are available for you to use to
further customize your Apache IIOP configuration.
Table 5.3 Additional Apache IIOP directives
Directive default Description
IIopChunkedUploading (commented
out) false
Controls whether Apache attempts "chunked"
uploads to the Borland web container IIOP
connector. To enable Apache to "chunk" large
size data that is greater than the
IIopUploadBufferSize value, uncomment and set
to true. Note: "Chunked" upload must also be
enabled on the web container by setting the
server.xml attribute enablechunking="true".
If you want Apache to wait until it has collected
all data before invoking the CORBA RPC to
send the large size data to the Borland web
container, leave commented out or set to false.
For more information, go to “Implementing
chunked download” on page 50.
IIopUploadBufferSize (commented
out) 4096
Defines the "chunked" buffer size employed
when IIopChunkedUploading is set to true. This
directive accepts a numeric value >0.
Essentially, the larger the number of bytes you
set this directive to, the less the number of
CORBA RPCs that are required to send the
data to the Borland web container. However,
the larger you set this directive, the more
memory will be consumed in servicing the
transaction. Tuning this parameter allows you
to fine-tune the performance charactistics. This
enables the administrator to weigh the RPC
costs against memory resource usage to
optimize uploading on their system. Note: If an
invalid value is presented (non numeric/
negative number) then the default 4096 value is
employed. For more information, go to
“Implementing chunked upload” on page 52.
IIopSessionAffinity true Controls whether Apache employs "session
affinity" in it's request handling. When
uncommented and set to true, Apache ensures
that all requests associated with a particular
session id are routed to the Borland web
container from which the request originated. To
disable this mechanism and have all requests
be subject to the round-robin model configured
for the particular cluster, set to false. Note: If
session affinity is disabled (=false), it is crucial
to ensure that the Borland web container's
shared session store is correctly configured;
otherwise the session data's integrity will be
compromised. For more information, go to the
Clustering of multiple Web components, Smart
session handling section.