Removing Namespaces from XML

Here is the following code you can use in your Transform XML activity. Map the input as string.

<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0"
 xmlns:xsl="http://www.w3.org/1999/XSL/Transform" >
 <xsl:output method="xml" encoding="UTF-8" indent="yes"/>
 <xsl:template match="/|comment()|processing-instruction()">
  <xsl:copy> <!-- go process children (applies to root node only) -->
   <xsl:apply-templates/>
  </xsl:copy>
 </xsl:template>
 <xsl:template match="*">
  <xsl:element name="{local-name()}">
  <!-- go process attributes and children -->
   <xsl:apply-templates select="@*|node()"/>
  </xsl:element>
 </xsl:template>
 <xsl:template match="@*">
  <xsl:attribute name="{local-name()}">
   <xsl:value-of select="."/>
  </xsl:attribute>
 </xsl:template>
</xsl:stylesheet>

Load balancing on single machine

If you want to deploy a BWENGINE in load balancing mode in a single machine, follow the steps

Process1
1) Generate the ear file
2) If you deploy through AppManage utility, edit bindings in the ServiceName.xml file
  <bindings>
        <binding name="Process Archive">
            <Machine>MachineName</Machine>
            ..............
            ..............
       </binding>
          <binding name="Process Archive-1">
             <Machine>MachineName</Machine>
               ..............
               ..............
           </binding>
     </bindings>
3) Start the services.

Process2
   1) Add multiple Process Archives in the Enterprise Archive
   2) Add the same processes to each Process Archive
   3) Build the archive
   4) Deploy and start the services
Finish.............
     

TIBCO

How to stop the Main process until all the spawned processes completes. Note: All spawned processes should have atleast one element in the starter activity.
Step 1 --> Drag a Notify Configuration shared activity in the Shared Configurations.
Step 2 --> Drag a Mapper activity and create a repeating element in the Input Editor tab.
Step 3 --> Map unique transaction id from the source to the element created in Step 2
Step 4 --> Create a Iterate Group on the Call process from where you are calling spawnned processes.
Step 5 --> Map the varialbe created in Step 2 in the Variable List using XPath.
Step 6 --> Map Index Name($i) value to an element of the sub process.(Sub-processes should have atelast one element in the starter activitiy)
Step 6 --> Drag a Wait activity on to the Main process and craete a Iterate group on that.
Step 7 --> In the Configurations, Map the Notify Configuration, created in Step 1.
Step 8 --> Map the varialbe created in Step 2 in the Variable List using XPath.
Step 9 --> Map Index Name($k) value to Key in the Wait activity input tab.
Step 10 --> In the spawned processes, drag a Notify activity before the End acitivity and map the Shared Configuration which is created in Step 1.
Step 11 --> Map the element created in Start activity to Key in the Input tab.
Finish...............
Please let me know if you face any difficulties................

How to Monitor TIBCO EMS Server using Hawk
Step 1 --> Copy the following jar files into <>/hawk/admin-plugins directory
a) tibjmsadmin.jar b) tibjms.jar c) tibcrypt.jar d) jms.jar(optional)
Step 2 --> Edit tibjmsadmin.hma file with appropriate userName, Password, HostName and Port values.
Step 3 --> Add following entries in classpath/path
tibjmsadmin.jar, tibjms.jar, jms.jar, tibcrypt.jar Step 4 --> Restart the Hawk service
Finish..............
Keep enjoying work when there is work............... :-)