Friday, June 10, 2011

Weblogic 10.3.5 Coherence

Coherence servers (also known as Coherence data nodes) are stand-alone cache servers, dedicated JVM instances responsible for maintaining and managing cached data.
To create a Coherence server in an existing domain:
  1. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit
  2. In the left pane of the Console, expand Environment and select Coherence Servers.
  3. In the Coherence Servers table, click New.
  4. On the Coherence Server Properties page:
    1. Enter the name of the server in the Name field. The server name is not used as part of the URL for applications that are deployed on the server. It is for your identification purposes only. The server name displays in the Administration Console, and if you use WebLogic Server command-line utilities or APIs, you use this name to identify the server.
    2. Select an existing Machine (WebLogic Server host computer name on which this server is meant to run) from the drop-down list. In order to use Node Manager to start this Coherence server, you must assign the server to a machine and you configure the machine for the Node Manager.
    3. Optional. In Cluster, enter the system-level Coherence cluster resource associated with this server.
    4. Optional. In Unicast Listen Address, enter the IP address for the cluster unicast listener. This attribute may be used to override the value of the referenced Coherence cluster.
    5. Optional. In Unicast Listen Port, enter the port for the cluster unicast listener.
    6. Optional. Use the Unicast Port Auto Adjust check box to specify whether the unicast port will be automatically incremented if the port cannot be bound because it is already in use. 


    1. Click Finish. The new server appears in the Summary of Coherence Servers table.
    2. To activate these changes, in the Change Center of the Administration Console, click Activate Changes



      Wednesday, June 1, 2011

      AIA Foundation Pack-Fulfill Prerequisites for Script Based Deployment


      To fulfill the prerequisites for script based deployment of Foundation Pack configure the following environment variables:
      1. Set MW_HOME (where you have installed FMW 11g).
      2. Set SOA_HOME to the directory where you have installed SOA 11g. For example c:\MW_HOME\AS11gR1SOA.
      3. Set AIA_HOME to the directory where you have copied AIA software. For example d:\AIA_HOME.
      4. Set JAVA_HOME to directory where you have installed Java.
      5. Set ANT_OPTS="-Xms512m -Xmx1024m -XX:MaxPermSize=512m".
      6. Set ORACLE_HOME=$SOA_HOME.
      7. Set WEBLOGIC_HOME=$MW_HOME/wlserver_10.3.
      8. Set HARVESTER_HOME=$AIA_HOME/Infrastructure/LifeCycle/AIAHarvester.
      9. Set ANT_HOME=${MW_HOME}/modules/org.apache.ant_<version number>. For example, 1.7.1.
      10. Set PATH=.:$JAVA_HOME/bin:$ANT_HOME/bin:$PATH.
      11. Set CLASSPATH=.:${WL_HOME}/server/lib/weblogic.jar: ${AIA_HOME}/lib/aia.jar: ${AIA_HOME}/lib/aia-utils.jar: ${MW_HOME}/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar: ${MW_HOME}/oracle_common/modules/oracle.mds_11.1.1/mdsrt.jar: ${MW_HOME}/oracle_common/modules/oracle.osdt_11.1.1/osdt_xmlsec.jar: ${MW_HOME}/oracle_common/modules/oracle.jps_11.1.1/jps-e.jar: ${MW_HOME}/oracle_common/modules/oracle.jps_11.1.1/jps-common.jar: ${MW_HOME}/oracle_common/modules/oracle.jps_11.1.1/jps-internal.jar: ${MW_HOME}/oracle_common/modules/oracle.jps_11.1.1/jps-unsupported-api.jar: ${MW_HOME}/oracle_common/modules/oracle.pki_11.1.1/oraclepki.jar: ${MW_HOME}/oracle_common/modules/oracle.idm_11.1.1/identitystore.jar: ${MW_HOME}/oracle_common/modules/oracle.xdk_11.1.0/xmlparserv2.jar: $CLASSPATH.

      Oracle SOA Stack 12.2.1.3

      SOA Suite 12c has a new  component: Oracle Enterprise Scheduler Service (ESS). ESS provides the ability to run different job types distribut...