Below is the plan that we can follow to monitor soa server performance and maintain 100 % uptime.1. Regular (eg. daily/bi- weekly) monitoring of all SOA environments as per the attached spreadsheet. I have covered the following aspects in the sheet.a. All SOA URLS should be up and running.b. All applications deployed like EOL, scheduler should be up and running.c. Proxy HTTPS URL i.e soahavrtest should be up and running.d. Monitor the disk utilization/soa server performance.e. Monitor SOA repository database utilization.f. Purge old instances from SOA environments based on direct table purge scripts and reclaim database storage space.g. There should be no more than 3 days old running/recoverable instances in SOA BPEL engine in any environment.h. Unwanted demo composites/old composite versions /domains created in soa server should be pruned.2. For PRODAll activities are managed by OOD.-------------------------------------------SOA Clonning - 1) Stop all managed server and admin servers.2) copy BEA_HOME directory to target location. ( You could install the WLS software-only, but a copy is quicker.) cp -r bea /tmp/test3) Copy the SOADOMAIN_HOME directory to your target destination. cp -r SOADOMAIN_HOME /tmp/test4) Export the SOA repository from the database. (make sure you have the rights to export the various SOA schema's such as, MDS, SOA_INFRA etc.)expdp owner=SOA5) Import the SOA repository in target database. impdp owner=SOA6) Manually make changes in the SOADOMAIN_HOME/config/config.xml file. (to set new hostnames and/or IP addresses for the Admin Server, Managed Servers and node manager (machine))7) Manually make changes in the WLS_HOME/wls_server1/common/nodemanger/* properties. (If this is a new server, the nodemanager.properties should be updated. If the cloning is done on the same server, you should change the port number only, or reuse an existing node-manager.)8) Manually make changes in the SOADOMAIN_HOME/config/jdbc/* datasource file(s) to target database. (The data-sources for target database updated.)9) Make changes in start-up scripts when using WKA in Coherence clustering. (If you are using a clusterm verify the coherence properties, such as multicast adresses. If you are using well-known-adresses (WKA) make sure the are updated.)10) Start servers ( Managed and admin servers ) 11) Check SOAP Server URL and Callback Server URL (If you are usingf a loadbalancer check SOAP Server URL and Callback Server URL via Enterprise manager. (EM -> SOA-INFRA -> SOA Administration -> Common Properties)