Sample backing map configuration needed

Question

Hi,
I want to persist a substantial amount of data into coherence cache. The number of entity objects (all POF enabled) that need to go into the cache is appx 4 million. I am trying to load the whole data set into my server which is having 4 coherence nodes , each running on 2 GB memory, but that is falling short. I have pasted my cache configuration below.
<?xml version="1.0"?>
<!DOCTYPE cache-config SYSTEM "cache-config.dtd">
<cache-config>
     <defaults>
          <serializer>pof</serializer>
     </defaults>
     <caching-scheme-mapping>
          <cache-mapping>
               <cache-name>SALES-*</cache-name>
               <scheme-name>default-partitioned</scheme-name>
          </cache-mapping>
     </caching-scheme-mapping>
     <caching-schemes>
          <distributed-scheme>
               <scheme-name>default-partitioned</scheme-name>
               <service-name>DefaultPartitioned</service-name>
               <backing-map-scheme>
                    <local-scheme />
               </backing-map-scheme>
               <autostart>true</autostart>
          </distributed-scheme>
     <!-- Invocation Service scheme. -->
          <invocation-scheme>
               <scheme-name>examples-invocation</scheme-name>
               <service-name>InvocationService</service-name>
               <serializer>
                    <class-name>com.tangosol.io.pof.ConfigurablePofContext</class-name>
               </serializer>
               <autostart system-property="tangosol.coherence.invocation.autostart">true</autostart>
          </invocation-scheme>
     </caching-schemes>
</cache-config>
I want to also configure a backing map along with this configuration, but i am not sure how to size the backing map keeping in mind my server memory limitations. Can you please help me out in this? A sample backing map configuration will suffice.
Thanks
Surya

Answer 1

>
yzanagi wrote:
> ....
> The instruction in the FAQ note is actually straightforward if you are familiar with the xpath notation.
>
> If it's not working, can you provide how you set these parameters and how your SOAP envelope exactly looks?
>
+
# Can I extract some ID value from the SOAP envelope and use it as the message ID?+
You can use the com.sap.aii.axis.soap.MessageIDExtrator handler to extract some ID value from the SOAP envelope and use it as the message ID. This handler can extract an ID string value (i.e., the 36-character GUID string) from the SOAP envelope and set it to the request or response message ID property in the message context. The ID string must be contained within some XML element. See a configuration for extracting the ID from WS-Addressing's MessageID element. {quote)
Hi,
Thanks for your reply;
I'm familiar with xpath however the FAQ does not mention the use of xpath anywhere. Please see above an extract of the FAQ regarding the MessageIDExtractor;
The provided example of the module configuration looks like this:
Module Key | Parameter Name | Parameter Value
id | handler.type | java.com.sap.aii.axis.soap.MessageIDExtractor
xireq | handler.type | java.com.sap.aii.axis.xi.XI30InboundHandler
sap | module.pivot | true
xires | handler.type | java.com.sap.aii.axis.xi.XI30InboundHandler
When you observe this configuration you notice that there's only one entry for the MessageIDExtractor. How will the handler know which XML field to pick from the incoming SOAP envelope? I think the example is missing some additional parameters where you can provide the xpath query.
Can you clarify?
Many thanks,
Roberto
Edited by: Roberto Viana on Nov 5, 2010 9:00 AM
Edited by: Roberto Viana on Nov 5, 2010 9:06 AM