Zero Bytes

Here is how IBM Sterling B2B Integrator map editor translator controller parse and executes the Rules. Pre-Session (Variable Declarations & Hard Coded Values) Root On Begin    Root Exedend Rules Record On Begin Standard Rule & Exedend Rule Record On End Root On Begin Post-Session (Executes before end of map)

soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:mesa="http://www.sterlingcommerce.com/mesa"    soapenv:Header/    soapenv:Body       mesa:DEMO_WEB_SERVICE xmlns:mesa="http://www.sterlingcommerce.com/mesa" Payload goes here....       /mesa:DEMO_WEB_SERVICE    /soapenv:Body /soapenv:Envelope Need to add namespace xmlns:mesa="http://www.sterlingcommerce.com/mesa under soapenv:Body.

Update bashrc file for to default required path variables, xclock setup etc. I find this is clean way then setting up or updating path variables under each user profile unless it is mandatory. This is clean way for sandbox setup at least not for production though. .bashrc file location: /etc/bash.bashrc ####Sirish Reddy: Settings ######## PATH=/u01/app/jdk1.6.0_25/bin:$PATH export LANG=en_US xhost local:oracle xhost local:sirishg xhost local:apache

Here is the interesting video I came across which teach the logic on how to learn anything in 20 Hours, Interesting... 

1. Download  VisualVM      https://java.net/projects/visualvm/downloads/download/release138/visualvm_138.zip 2. Find the value of the property called  ACTIVEMQ_JMX_PORT from sandbox.cfg. 3. Add Remote Host First and under Remote Host add Add JMX Connection.      < SI HOST Name >:< ACTIVEMQ_JMX_PORT >     No need of providing user credentials and Save the connection. 

Starting an External Purge Procedure If you have a cluster installation, make sure that you are not running the external purge on another node of the cluster. If you are running the external purge on more than one node, it will cause database locks. For more information, see  Monitoring an External Purge . Important:  It is the customer's responsibility to keep exactly one of these external purge processes running in the cluster. If you need to shut down the hardware that is running the external purge, you must run the external purge on a different node. Disable the default Purge service. Click  Deployment  >  Schedules , search for PurgeService, and then clear the  Enabled  checkbox for PurgeService. Note:  If you have customized the Schedule_PurgeService business process, you need to add your customized code to the new Schedule_PurgeService business process. The new Schedule_PurgeService business process includes a warning mess...