Booting Oracle WebLogic

This post is related to our presentation at Oracle OpenWorld 2014. All code/configuration used during the presentation is available here.

The presentation as a PDF file – CON3633_Sysco_Booting_Weblogic

To start and stop AdminServer and the managed servers, we use a Jython (Python) script. It is on purpose made simple, but on production systems there should be more error handling, and also more efficient connection handling (i.e., check if there is a connection to NodeManager and/or AdminServer and reuse the connection if there is one active). Instead of calling the script below once for each server that we want to start, this script and the startall.sh script could be changed to give a list of servers to start, not just one and one as it is now.

wls.py

Full path for wlst.sh (under wlserver/common/bin) and wls.py must be given, unless they are in $PATH

startall.sh

stopall.sh

adminUrl must point to the AdminServer (often a VIP address) while nmHost points to the local NodeManager.

config.properties

Before running this command (deprecated in 12c, but still works in 12.1.3), you must source setDomainEnv.sh for the domain you are using.

Encrypt username and password (11g)

To run this command, you must start WLST in interactive mode. First you have to source setDomainEnv.sh, then start WLST

Encrypt username and password (12c)

This is not based on the script from the 12c documentation ( http://docs.oracle.com/middleware/1213/wls/NODEM/java_nodemgr.htm#BABJIDFD  ). One important difference is that this script starts NodeManager with user oracle, while the script in the documentation starts NodeManager as root, which is not recommended.

/etc/init.d/nodemanager

The weblogic scripts call the startall.sh when the server starts, and stopall.sh when the server stops.

weblogic

For both the nodemanager and the weblogic scripts, they must be made runable (chmod 0755) and activated (chkconfig –add) before they will be used next time the server starts or stops.

Oracle BPM success seminar september 10

Oracle, Sysco and Capgemini will host the following event in Oslo september 10th: Oracle BPM success seminar.

For registration, click here

BAM 12c new features

From my point of view BAM is the product in SOA/BPM Suite that has the largest number of improvements. As mentioned in What’s New - release 12c is a complete restructuring of Oracle BAM. In the documentation it is described the integration with SOA(BPEL) and BPM Suite. One other product that fits BAM perfectly is Oracle Event Processing.

Here are some of the improvements/changes:

  • Better browser support
  • Restructuring of artifacts / New naming for many of the Components
  • More flexible data – Four data object types are supported: simple, derived, logical, and external
  • Use of OEP for Event Stream Analytics and Alerts
  • Export of data possible
  • Security can be applied to an entire project or to individual queries, business views, and other parts of the project
  • Integration with SOA/BPM has been simplified
  • Geo Map views are supported as a preview feature
  • ICommand has become BamCommand
  • Consolidation / more Enterprise Grade Infrastructure- BAM use OEP, Email alerts use the Oracle User Messaging Service, use of ADF and Coherence
  • BAM can now be clustered – not like in 11g where it was not a symmetrically scalable system
  • Using loadgen with Oracle BAM is supported for testing of Dashboards
  • Importing data object metadata and data from Oracle BAM 11g is supported

Some features are also removed, but in a a “remake”-version like this one I feel it was a wise decision. This BAM looks a lot better than the old one (which did look a bit old)

  • Better browser support

    In the old version you had to use Internet Explorer – now the support is a lot better (as in all the 12.1.3 FMW-platform) . link click “System Requirements and Supported Platforms for Oracle Fusion Middleware 12c (12.1.3) xls”

    Restructuring of artifacts/more flexible data

    There are many changes:

    • Folders have become projects, in which all design entities are created
    • Key performance indicators (KPIs) are independent data-analysis entities
    • List and Crosstab views have become Table views
    • Reports have become Dashboards
    • Addition of derived data object – extends a simple data object or another derived data object. It inherits the columns and hierarchies of the parent data object and adds its own columns.
    • Addition of  logical data object – references data in other archived relation data objects. Unlike a derived data object, it is read-only and not a physical data object. However, it can do more than add columns. It can rename or hide columns, or add calculated columns. It can also join two or more simple or derived data objects
    • You can add indexes for attributes for better performance

    Here you can see how the different data Object Types can be combined:

  • The changes mentioned here will make it easier to structure data, queries and views in Projects. Things that were difficult and very limiting in 11g looks now more flexible,

    Use of OEP for Event Stream Analytics and Alerts

    BAM has embedded OEP, so it is now a separate part in the architecture – the “Advanced Continuous Query Service”.

    One of the difficult things of using OEP is to write CQL. Even if you know SQL well, it is not allways easy to formulate the correct statement. BAM has found a good way to solve this. It gives you a set of templates that you normally would need. For full flexibility you would need OEP. Here are the templates offered for Continuous Queries:

    • Trending Detection Template
    • Duplicate Detection Template
    • Monitor Count Template
    • Moving Aggregation Template
    • Missing Event Template
    • Top N Template
    • ‘KPI Alert Template

    Then you must configure – for example for the missing event, you must specify:

    Using OEP you would have to make this in JDeveloper, deploy etc. I think this embedding of OEP is excellent!

What’s new in Oracle Event Processing 12c?

Oracle Event Processing is not the most frequently used tool in the Oracle SOA Suite, but more and more people now know about it. With some of the new features in BAM 12c many people will probably use it, without knowing that it is actually OEP behind there. OEP has allways been open and easy to adapt to your needs, but with this version it will be easier to show value fast. My personal favorite in this version is the REST adapter.

For those of you interested in OEP – the following document describes What’s New in OEP 12c. This is the type of document that I think is really useful for us when a new release is available. The SOA whitepaper on 12c is also excellent. Read the full entry…

Booting WebLogic – presentation at Oracle OpenWorld 2014

Oracle WebLogic Server instances are the foundation for Java EE applications and Oracle Fusion Middleware, including SOA, BPM, and so on. But even as important as Oracle WebLogic Server instances are for organizations, there are no out-of-the-box scripts for booting Oracle WebLogic Server instances automatically when the server itself boots. Read the full entry…