• timeouts on requests
• automatic actions on server, workmanager or application level: https://community.oracle.com/thread/1983700

SOA Suite can be up quickly!

 import os   
 import xml.etree.ElementTree as ET   
 import xml.dom.minidom as minidom   
 import sys,re   
 import argparse   

 deployed_composites="D:\\tmp\\soa-infra_metadata\\deployed-composites\\deployed-composites.xml"

 #read a file and return a ElementTree   
 def get_tree_from_xmlfile(filename):   
   if os.path.isfile(filename):   
    tree = ET.parse(filename)   
    return tree   
   else:   
    raise Exception('Error opening '+filename)   

 def get_deployedcomposites(deployed_composites):  
       deployed_composites_root = deployed_composites.getroot()  
       return deployed_composites_root  

 deployed_composites_el = get_tree_from_xmlfile(deployed_composites)  
 deployed_composites_root = deployed_composites_el.getroot()  

 list = []  
 for rev in deployed_composites_root.findall('composite-series/composite-revision'):  
      list.append(rev.attrib.get('dn').replace('!','_rev'))  
 for dir in os.listdir('D:\\tmp\\soa-infra_metadata\\deployed-composites\\default'):  
   if 'default/'+dir not in list:  
           print "deleteMetadata(application='soa-infra',server='soa_server',docs='/deployed-composites/default/"+dir+"/**')"

 public static void work()  
  {  
   try  
   {  
    MDSInstance mdsInstance = null;  
    if (true)  
    {  
     mdsInstance = MDSUtils.initializeDBStore("soa_mds_user",   
"soa_mds_pass",   
"jdbc:oracle:thin:@hostname:port/sid",   
"soa-infra",  
                          MDS_CONNECTION_NAME);  
    }  

    Boolean foundDocument = false;  
    // Find a resource  
    if (true)  
    {  
     List<ResourceName> list = MDSUtils.findResource(mdsInstance, "/deployed-composites/", false);  
     List<ResourceName> listinner = null;  
     List<String> path = new ArrayList<String>();  
     List<Boolean> type = new ArrayList<Boolean>();   
     System.out.println("List: (" + list.size() + " element(s))");  
     for (ResourceName rn : list) {  
       path.add(rn.getAbsoluteName());  
       type.add(rn.isPackageName());  
     }  

     ResourceName rn = null;  

     for (int i = 0; i < list.size() ; i++) {  
       rn = list.get(i);  
       foundDocument = false;  
       if (rn.isPackageName()) {  
         for (int j = 0 ; j<path.size();j++ ) {  
           if (path.get(j).startsWith(rn.getAbsoluteName())) {  
             if (!type.get(j)) {  
               foundDocument = true;  
               break;    
             }  
           }  
         }  
         if (!foundDocument) {  
           try {  
             MDSUtils.deleteResource(mdsInstance, rn);  
           } catch (Exception e) {  
             System.out.print("");  
           }  
           System.out.println("Deleted: "+rn.getAbsoluteName());  
         }  
       }  
     }  
    }  
    System.out.println("Done");  
   }  
   catch (Exception e)  
   {  
    e.printStackTrace();  
   }  
  }  

 this.bindFunc1 = function (zwayName) {  
   if (zwayName != "zway")  
    return; // you want to bind to default zway instance  

   var devices = global.ZWave[zwayName].zway.devices;  

   //sensor specific code  
 };  

 // process all active bindings  
 if (global.ZWave) {  
   global.ZWave().forEach(this.bindFunc1);  
 }  

 // and listen for future ones  
 global.controller.on("ZWave.register", this.bindFunc1);  

 this.bindFunc1 = function (zwayName) {  
   if (zwayName != "zway")  
    return; // you want to bind to default zway instance  

   var devices = global.ZWave[zwayName].zway.devices;  

  zway.devices[3].instances[0].commandClasses[48].data[1].level.bind(function() {  
   if (this.value == true)  
     debugPrint("Executing trigger");  
     system('/usr/bin/python /opt/z-way-server/automation/trigger.py');  
 });  

  zway.devices[3].instances[0].commandClasses[49].data[1].val.bind(function() {  
   debugPrint("Saving measure");  
   system('/usr/bin/python /opt/z-way-server/automation/savemeasure.py','Temperature',this.value);  
 });  

  zway.devices[3].instances[0].commandClasses[49].data[3].val.bind(function() {  
   debugPrint("Saving measure");  
   system('/usr/bin/python /opt/z-way-server/automation/savemeasure.py','Luminescence',this.value);  
 });  

  zway.devices[3].instances[0].Battery.data.last.bind(function() {  
   debugPrint("Saving measure");  
   system('/usr/bin/python /opt/z-way-server/automation/savemeasure.py','Battery',this.value);  
 });  

 };  
 // process all active bindings  
 if (global.ZWave) {  
   global.ZWave().forEach(this.bindFunc1);  
 }  

 // and listen for future ones  
 global.controller.on("ZWave.register", this.bindFunc1);  

 import time  
 import datetime  

 ts = time.time()  
 st = datetime.datetime.fromtimestamp(ts).strftime('%Y-%m-%d %H:%M:%S')  

 def send_email(user, pwd, recipient, subject, body):  
   import smtplib  

   gmail_user = user  
   gmail_pwd = pwd  
   FROM = user  
   TO = recipient if type(recipient) is list else [recipient]  
   SUBJECT = subject  
   TEXT = body  

   # Prepare actual message  
   message = """\From: %s\nTo: %s\nSubject: %s\n\n%s  
""" % (FROM, ", ".join(TO), SUBJECT, TEXT)  
   try:  
     server = smtplib.SMTP("smtp.gmail.com", 587)  
     server.ehlo()  
     server.starttls()  
     server.login(gmail_user, gmail_pwd)  
     server.sendmail(FROM, TO, message)  
     server.close()  
     print 'successfully sent the mail'
   except:  
     print "failed to send mail"

 send_email('xxx@gmail.com','pass','target@mail.nl','Intrusion detected','Intrusion detected at '+st)  

 f = open('/opt/z-way-server/automation/intrusions.log', 'a')  
 f.write(st+"\n")  
 f.close()  

 import time  
 import datetime  
 import sys  

 ts = time.time()  
 st = datetime.datetime.fromtimestamp(ts).strftime('%Y-%m-%d %H:%M:%S')  

 f = open('/opt/z-way-server/automation/measure.log', 'a')  
 f.write(st+"\t"+sys.argv[1]+"\t"+sys.argv[2]+"\n")  
 f.close()  

• Reduce superfluous data fetching. Think about efficient caching (and cache maintenance). Think about implementing a claim-check pattern.
• Reduce the number of service calls. Think about service layering, granularity and fetching of data sets instead of single pieces of data.
• When will the data be needed? Think about asynchronous processing (and how you know when it's done).
• Optimally use your resources. Think about parallel processing and efficient load-balancing.
• Keep the user experience in mind. Think about priority of message-processing (batches often have lower priority).

• Works out of the box. little implementation effort required.
• Works in the JDeveloper integrated WebLogic server.
• Is a generally accepted and widely acknowledged standard (see here). Also allows interoperability with several other web service providers.

• Possible integration patterns are limited. WS-Addressing is SOAP specific and always one caller and one called service. Multiple callbacks to the same process are not possible and integrating calls from other sources (e.g. a file which has been put on a share) is also not straightforward.
• It can be hard to propagate WS-Addressing headers through a chain of (e.g. composite) services.
• The callback when using SOAP over HTTP is always direct (the caller sends a callback port with the request in the WS-A headers). difficult to put a Service Bus in between unless using SOA-Direct (which has other drawbacks).
• Manual recovery in case a callback does not come, is possible, but requires determining the request headers. With SOA-Direct this becomes harder.
• The callback cannot arrive before the process which needs to do the callback has been called since the WS-Addressing headers have not been determined yet. if for example you want to respond to events which have arrived before your process has been started, WS-Addressing is not the way to go.
• Correlation is technical and cannot directly be based on functional data. It is not straightforward (or usual) to let the callback arrive at a different process.

• Implementation requires some thought. Where do you correlate and how do you correlate?
• Tight coupling between caller and called service requires effort to avoid. The called service should not explicitly call back to the caller with an hardcoded endpoint in order to allow re-use of the called service. A solution for this can be requiring the calling service to send a callback URL with the request or do integration not with HTTP calls but for example with JMS.
• The request and callback are required to contain data which allows correlation
• Correlation does not work on the JDeveloper embedded WebLogic server. You'll receive the below error
  [2015-12-17T07:04:40.500+01:00] [DefaultServer] [ERROR] [] [oracle.integration.platform.blocks.event.jms2.EdnBus12c] [tid: DaemonWorkThread: '1' of WorkManager: 'wm/SOAWorkManager'] [userId: <anonymous>] [ecid: c370fba3-1fcd-480f-8c27-7c4cd6a7a41e-0000010e,0:19] [APP: soa-infra] [partition-name: DOMAIN] [tenant-name: GLOBAL] Error occurred when saving event to JMS mapping to database: java.lang.ClassCastException: weblogic.jdbc.wrapper.PoolConnection_org_apache_derby_client_net_NetConnection cannot be cast to oracle.jdbc.OracleConnection
• Correlation sets can be used on the SOA infrastructure but is not a generally acknowledged standard method for doing correlation (vendor specific).

• Very flexible. multiple correlation sets can be used in a single process. external events using diverse technologies can be correlated to running processes. complex integration patterns are possible.
• Correlation does not depend on SOAP headers (technical data) but (most often) on functional data / message content
• Recovery can be relatively easy (no need to determine request headers, only expected callback message)
• The correlating events can arrive before the process is listening; they will be processed once the correlation set is initialized
• SB between request and response can be used (it does not matter from where the callback comes)

• First the Server URL configuration property value on the SOA Infrastructure Common Properties page is checked. 
• If not specified, the FrontendHost and FrontendHTTPPort (or FrontendHTTPSPort if SSL is enabled) configuration property values from the cluster MBeans are checked. 
• If not specified, the FrontendHost and FrontendHTTPPort (or FrontendHTTPSPort if SSL is enabled) configuration property values from the Oracle WebLogic Server MBeans are checked. 
• If not specified, the DNS-resolved Inet address of localhost is used

• It cannot refer to another virtual column by name.
• It can only refer to columns defined in the same table.
• If it refers to a deterministic user-defined function, it cannot be used as a partitioning key column.
• The output of the expression must be a scalar value. It cannot return an Oracle supplied datatype, a user-defined type, or LOB or LONG RAW.

• It is very flexible and relatively technology independent. It allows you to scan any XML file such as BPEL, BPMN, OSB, Mediator, Spring, composite.xml files
• It requires only configuration of SonarQube, the SonarQube XML Plugin and the CI solution (Jenkins in this example)
• It has few dependencies. It does not require an Oracle Home or custom JAR files on your SonarQube server. 
• The XML Plugin has support (by SonarSource) so high probability it will still work in future versions of SonarQube.
• Writing rules is simple; XPath expressions. it does not require you to write Java code to create checks.

• SonarQube Plugin
• Quality Gates Plugin

Server running at http://127.0.0.1:8000
0s, 0.054ms - Request start
0s, 147.451ms - Google response: dog
0s, 148.196ms - Response returned to caller
0s, 184.605ms - Systran response: dog

{
"result": "dog",
"source": "Google"
}

Server running at http://127.0.0.1:8000
0s, 0.003ms - Request start
0s, 107.941ms - Systran response: dog
0s, 108.059ms - Response returned to caller
1s, 78.788ms - Google response: dog

{
"result": "dog",
"source": "Systran"
}

• xml2js. This Node.js module allows transforming XML to JSON and back. The JSON which is created can be used to easily access content with JavaScript. This module is fast and lightweight, but does not provide specific SOAP functionality.
• soap. This Node.js module provides some abstractions and features which make working with SOAP easier. The module is specifically useful when calling SOAP services (when Node.js is the client). When hosting SOAP services, the means to control the specific response to a call are limited (or undocumented)

Using both modules, I encountered some challenges which I will describe and how (and if) I solved them. You can find my sample code here.

• Application Container Cloud provides an extensive user interface and API to allow you to do most required tasks easily. You do not need an expert to configure or operate Application Container Cloud (if you like, you can still hire me though ;).
• Node.js instances (inside Docker containers) can be added / deleted on the fly. The load-balancer (also hosted in the OPC) is configured for you. Thus you get cluster functionality (important for scaling and high availability) over Node.js instances with almost no effort.
• If one of the instances does not respond anymore, the load-balancer notices and sends requests to other instances. It does this by checking the root of your application. 
• When a Node.js instance crashes (by means of the Node.js process exiting), it is automagically restarted (you can confirm this by looking at the log files)

Creating an application is easy. You can use the provided API to easily create and manage an application or use the web interface. The format of the application to upload is also very straightforward. You upload a ZIP file with your complete application and a manifest.json file which can contain as little as for example:

{
  "runtime":{
    "majorVersion":"0.12"
  },
  "command": "node app.js",
  "release": {},
  "notes": ""
}

You can also add a deployment.json file which can contain variables you can use within your application. These variables can be updated with the web interface or the API and the application will be restarted to apply the new settings.

After multiple uploads and downloads, I noticed from the log files that my archive did not update. I changed the filename of the zip-file I uploaded and the problem did not occur anymore. Apparently, sometimes the uploaded file cannot be overwritten by a new upload (when doing certain actions at the same time probably). This can be dangerous. For a Continuous Delivery scenario I suggest using unique filenames to avoid this issue.

You can easily use a Maven build with the maven-assembly-plugin to create the archive to be deployed in case you want to embed this in a Continuous Delivery pipeline. You can of course also use the provided Developer Cloud Service. Read more about that here. There is a nice demo here.

Management

Application Container applications can be restarted, stopped, started, deleted. You can add and remove instances. You can not restart or start/stop a single instance. When a single instance does not respond anymore (on the application root URL), the load-balancer notices and does not send requests to that instance anymore. If you want to make it available again, you have to restart your entire application (or remove and add instances and hope the faulty one is removed and recreated). When adding instances, existing instances will keep running and for the new instances, when they are done creating, the load-balancer is updated. When removing instances, the load-balancer is also updated.

If the application ends the Node.js process, a new process will to be started immediately. This new process used the same IP and hostname during my tests. If I start/stop or restart the application, the hostname and IP get new values.

Log files

Log files can be downloaded from running applications.

If an application creation fails, you can also download the log files. See an example at 'Accessing the API' below. This can greatly help in debugging why the application cannot be created or started. Mostly the errors have been application errors. For example:

Aug 12 14:14:42: Listening on port: 8080
Aug 12 14:14:47: Request on url: /
Aug 12 14:14:47: /u01/app/app.js:49
Aug 12 14:14:47:   if (req.url.startsWith("/oraclecloud")) {
Aug 12 14:14:47:               ^
Aug 12 14:14:47: TypeError: undefined is not a function
Aug 12 14:14:47:     at Server.<anonymous> (/u01/app/app.js:49:15)
Aug 12 14:14:47:     at Server.emit (events.js:110:17)
Aug 12 14:14:47:     at HTTPParser.parserOnIncoming [as onIncoming] (_http_server.js:492:12)
Aug 12 14:14:47:     at HTTPParser.parserOnHeadersComplete (_http_common.js:111:23)
Aug 12 14:14:47:     at Socket.socketOnData (_http_server.js:343:22)
Aug 12 14:14:47:     at Socket.emit (events.js:107:17)
Aug 12 14:14:47:     at readableAddChunk (_stream_readable.js:163:16)
Aug 12 14:14:47:     at Socket.Readable.push (_stream_readable.js:126:10)
Aug 12 14:14:47:     at TCP.onread (net.js:540:20)

Do mind that the Node.js version running in the Application Container Cloud currently is 0.12.14. In this version for example you have to start Node.js with the --harmony switch if you want to use startsWith on the String object. My bad obviously.

Managing access

Even though there is an extensive user interface for management and monitoring of the Node.js application and also an extensive API (see more about about that below), the load-balancer configuration is not directly accessible. You can for example not configure a specific load-balancer probe or procedure to check whether the instance is up again. Also I did not find a way to easily secure my Node.js services to avoid them from being called by just anyone on the internet (I might have missed it though). It would be nice if for example the Node.js instance was behind an API platform or even just a configurable firewall.

 [oracle@localhost browsenexus2]$ python ./nexuscleanup.py localhost 8081 /nexus/service/local/repositories/releases/content /nl/amis/smeetsm/releases/ /nl/amis/smeetsm/applications/ admin admin123 true '2017-01-01 01:01:01' 1  
 2016-10-28 13:28:15.846401 INFO : Executing dummy run  
 2016-10-28 13:28:15.879159 INFO : Found 3 releases  
 2016-10-28 13:28:15.879267 INFO : Removing old releases (before: 2017-01-01 01:01:01) but keeping: 1  
 2016-10-28 13:28:15.879319 INFO : Not removing old release: {'url': 'http://127.0.0.1/nexus/service/local/repositories/releases/content/nl/amis/smeetsm/releases/simplewebapp-release/5.0/simplewebapp-release-5.0.pom', 'date': datetime.datetime(2016, 10, 28, 11, 2, 39)} because keeping 1 releases  
 2016-10-28 13:28:15.879369 INFO : Removing old release: {'url': 'http://127.0.0.1/nexus/service/local/repositories/releases/content/nl/amis/smeetsm/releases/simplewebapp-release/4.0/simplewebapp-release-4.0.pom', 'date': datetime.datetime(2016, 10, 28, 10, 59, 26)} because: 2016-10-28 10:59:26<2017-01-01 01:01:01  
 2016-10-28 13:28:15.879409 INFO : delete_artifact http://127.0.0.1/nexus/service/local/repositories/releases/content/nl/amis/smeetsm/releases/simplewebapp-release/4.0/simplewebapp-release-4.0.pom  
 2016-10-28 13:28:15.879448 INFO : delete_artifact path: http://127.0.0.1/nexus/service/local/repositories/releases/content/nl/amis/smeetsm/releases/simplewebapp-release/4.0  
 2016-10-28 13:28:15.879492 INFO : Removing old release: {'url': 'http://127.0.0.1/nexus/service/local/repositories/releases/content/nl/amis/smeetsm/releases/simplewebapp-release/3.0/simplewebapp-release-3.0.pom', 'date': datetime.datetime(2016, 10, 28, 10, 59, 2)} because: 2016-10-28 10:59:02<2017-01-01 01:01:01  
 2016-10-28 13:28:15.879565 INFO : delete_artifact http://127.0.0.1/nexus/service/local/repositories/releases/content/nl/amis/smeetsm/releases/simplewebapp-release/3.0/simplewebapp-release-3.0.pom  
 2016-10-28 13:28:15.879605 INFO : delete_artifact path: http://127.0.0.1/nexus/service/local/repositories/releases/content/nl/amis/smeetsm/releases/simplewebapp-release/3.0  
 2016-10-28 13:28:15.879643 INFO : Releases removed: 2  
 2016-10-28 13:28:15.879685 INFO : Releases not removed: 1  
 2016-10-28 13:28:15.879718 INFO : New number of releases: 1  
 2016-10-28 13:28:15.890064 INFO : Found 1 release dependencies  
 2016-10-28 13:28:15.954508 INFO : Found 4 artifacts  
 2016-10-28 13:28:15.954577 INFO : Artifact found as dependency in release. Do not touch!: Artifact: {'url': 'http://127.0.0.1/nexus/service/local/repositories/releases/content/nl/amis/smeetsm/applications/simplewebapp/4.0/simplewebapp-4.0.pom', 'date': datetime.datetime(2016, 10, 28, 11, 3, 53), 'version': '4.0', 'groupid': 'nl.amis.smeetsm.applications', 'artifactid': 'simplewebapp'} Release: {'date': datetime.datetime(2016, 10, 28, 11, 2, 39), 'version': '4.0', 'pom': 'http://127.0.0.1/nexus/service/local/repositories/releases/content/nl/amis/smeetsm/releases/simplewebapp-release/5.0/simplewebapp-release-5.0.pom', 'groupid': 'nl.amis.smeetsm.applications', 'artifactid': 'simplewebapp'}  
 2016-10-28 13:28:15.954630 INFO : Artifact not found as dependency and old so remove: {'url': 'http://127.0.0.1/nexus/service/local/repositories/releases/content/nl/amis/smeetsm/applications/simplewebapp/3.0/simplewebapp-3.0.pom', 'date': datetime.datetime(2016, 10, 28, 10, 58, 41), 'version': '3.0', 'groupid': 'nl.amis.smeetsm.applications', 'artifactid': 'simplewebapp'}  
 2016-10-28 13:28:15.954646 INFO : delete_artifact http://127.0.0.1/nexus/service/local/repositories/releases/content/nl/amis/smeetsm/applications/simplewebapp/3.0/simplewebapp-3.0.pom  
 2016-10-28 13:28:15.954671 INFO : delete_artifact path: http://127.0.0.1/nexus/service/local/repositories/releases/content/nl/amis/smeetsm/applications/simplewebapp/3.0  
 2016-10-28 13:28:15.954728 INFO : Artifact not found as dependency and old so remove: {'url': 'http://127.0.0.1/nexus/service/local/repositories/releases/content/nl/amis/smeetsm/applications/simplewebapp/2.0/simplewebapp-2.0.pom', 'date': datetime.datetime(2016, 10, 28, 10, 58, 31), 'version': '2.0', 'groupid': 'nl.amis.smeetsm.applications', 'artifactid': 'simplewebapp'}  
 2016-10-28 13:28:15.954755 INFO : delete_artifact http://127.0.0.1/nexus/service/local/repositories/releases/content/nl/amis/smeetsm/applications/simplewebapp/2.0/simplewebapp-2.0.pom  
 2016-10-28 13:28:15.954770 INFO : delete_artifact path: http://127.0.0.1/nexus/service/local/repositories/releases/content/nl/amis/smeetsm/applications/simplewebapp/2.0  
 2016-10-28 13:28:15.954804 INFO : Artifact not found as dependency and old so remove: {'url': 'http://127.0.0.1/nexus/service/local/repositories/releases/content/nl/amis/smeetsm/applications/simplewebapp/1.0/simplewebapp-1.0.pom', 'date': datetime.datetime(2016, 10, 28, 10, 58, 18), 'version': '1.0', 'groupid': 'nl.amis.smeetsm.applications', 'artifactid': 'simplewebapp'}  
 2016-10-28 13:28:15.954818 INFO : delete_artifact http://127.0.0.1/nexus/service/local/repositories/releases/content/nl/amis/smeetsm/applications/simplewebapp/1.0/simplewebapp-1.0.pom  
 2016-10-28 13:28:15.954838 INFO : delete_artifact path: http://127.0.0.1/nexus/service/local/repositories/releases/content/nl/amis/smeetsm/applications/simplewebapp/1.0  
 2016-10-28 13:28:15.954852 INFO : Artifacts removed: 3  
 2016-10-28 13:28:15.954872 INFO : Artifacts not removed: 1