Jboss Fuse Karaf Container - Could not start JMX connector server.

1. Goto <installDir>\etc
2. backup org.apache.karaf.management.cfg  
3. open org.apache.karaf.management.cfg 
4. change 0.0.0.0 to meaningfull IP like 127.0.0.1

Resolve Continious Start/Stop of application - Cleanup Fuse

Remove the files from the location below -

<fuse_install>\data\cache

Any features installed will have to re-installed.

Future Reading

Design Pattern -

• Builder Pattern

Common Commands

Common commands

• features:addUrl mvn:org.fusesource.sparks.fuse-webinars.cxf-webinars/customer-features/1.1.4/xml
• features:list | grep customer
• features:listrepositories

Install active MQ

• features:install activemq-camel

OSGI Commands

• osgi:install mvn:com.amtex/rdip/1.0.0-SNAPSHOT
• osgi:start 282
• osgi:stop 282
• osgi:uninstall 282
• osgi:update 282

• Deploying plain jar files
• osgi:install wrap:mvn:commons-dbcp/commons-dbcp/1.4
• osgi:install wrap:file:c:/ujjalb/data/backup/db2jcc4.jar

Log

• log:display

MVN

• mvn eclipse:eclipse
• generate an eclipse project
• mvn clean compile exec:java -Dexec.mainClass=camelinaction.GreetMeBean
• - compile and run the Java class
• mvn clean compile camel:run
• 
  
• mvn test -Dtest=OrderToCSVProcessorTest
• run a test
• 
  

Important personalities in Microservices / DSL

Martin Fowler

• http://martinfowler.com/dsl.html

Debasis Ghosh

• Book - DSL in Action - https://www.manning.com/books/dsls-in-action 
• Blog - - http://debasishg.blogspot.com/

Sam Newman

• Book - Building Microservices - http://shop.oreilly.com/product/0636920033158.do
• https://www.thoughtworks.com/profiles/sam-newman

Jonathan Anstey

• Book - Camel in Action

Claus Ibsen

• Book - Camel in Action

James Strachan

• Author of Camel, Active MQ, and many more

Criag Walls

• Spring in Action - https://www.manning.com/books/spring-in-action-fourth-edition
• Blog - https://spring.io/team/cwalls

Erich Gamma, Richard Helm, Ralph Johnson, John Vlissides (Gang of Four)

• Book - Design patterns - Elements of Reusable Object Oriented Software -http://www.amazon.com/gp/product/0201633612

What are the ESB implementation patterns and SOA in Datapower? (115/285 technotes for 2015)

An ESB Must Support the following mentioned below - 



Application Awareness in ESB

• Service Virtualization
• Improved Manageability - all the things below can be managed centrally
• style sheets
• security
• caching
• routing 
• Monitoring and Managing messages as they flow on the bus
• Routing messages 
• Converting Protocols
• Transformation
• Securing messages
• Providing connectivity to application services via open and propriety interfaces

Monitoring & Managing - log information about arrival path, contents of the msg based on filters

• ESB general monitoring
• track messages as they flow through the Enterprise - determine where time and resources are being spent
• remote monitoring of Datapower appliances - using SNMP, WSDM, WS-Management and proprietary SOAP API.
• for end to end monitoring for the ESB as well as the services is to - integrate Enterprise Monitoring software through std protocols like SNMP and ARM - like ITCAM for SOA

• ESB service level management (SLA) via monitoring - this is one of the most important 
• throttle (reject) and shape(delay) traffic based on patterns below
• Prioritization
• Count Monitors
• Duration Monitors
• protects the backend application resources when.
• application latency reaches a threshold
• processing latency reaches a threshold

Routing - is required the 2 reasons mentioned below

• Quality of Service - able to prioritize some message based on the the SLA
• Support of specific functionality or affinity - 
• some functionality provided in a particular version
• session may exist on a particular destination - requiring affinity based routing

• Different types of Routing
• Content based routing
• Context based routing
• Aggregation and Disaggregation

Protocol Conversion -

• need to move messages from one protocol to another
• web based scenario's are asynchronous, but back end systems are transaction oriented and want it to be synchronous. So state management responsibility is also there for the mediator.
• if Websphere ESB is used - to convert protocol and transform and route message - it in general degrades performance

Message Transformation -

• XML-to-XML Transformations 
• HTML/SOAP to XML Transformations
• Binary Transformations
• Content Enrichment and Filtering

Securing Messages -

• Though it has a large set of Security services - but a fairly small set of Services should be available for an ESB
• Support for standard WS-Security protocols as defined in the WS-I Basic Security Profile  
• Support for credential mapping across multiple protocols and transports  
• AAA

Connectivity -

• 
  

References:

Datapower Architectural Design Patterns - Integrating and Securing Services Across Domains - http://www.redbooks.ibm.com/redbooks/pdfs/sg247620.pdf

What are the three possible placement of Datapower in an ESB scenario? (114/285 technotes for 2015)

Architecturally Datapower can be placed in the three possible places in the Enterprise Infrastructure

• Standard ESB - basically used as an ESB
• ESB Federated Gateway
• DMZ Gateway - at the edge of the ESB

Standard ESB

ESB Federated Gateway

DMZ Gateway

What is a DMZ? (113/295 technotes for 2015)

In computer security, a DMZ or demilitarized zone (sometimes referred to as a perimeter network) is a 

• physical or logical subnetwork that 
• contains and exposes an organization's external-facing services to a larger and untrusted network, usually the Internet.

References:

Image Src - http://www.ibm.com/developerworks/websphere/techjournal/0907_banerjee/images/image002.gif

How can Datapower be used as an ESB? (112/285 technotes for 2015)

Datapower can be considered as an ESB since - 

• supports - abstraction using the proxy architecture
• highly message oriented - with support for SOAP, raw XML and ther formats
• has full Web Services support
• Is network aware - residing between application layer and network - with support for 
• routing, msg filter, transformation etc

• Also 
• has a surprisingly small footprint
• built from the ground up to be network aware.

What are the different Datapower security scenarios? (111/285 technotes for 2015)

Different Datapower security scenarios:

• Datapower typical security - solves the issues below
• Cross Enterprise Inter-operation - 
• Federated Interoperability - 
• Human and automated service invocations - 
• Dynamic service binding -
• Global architecture layers impact - 

• Datapower as a XML firewall

• While developing internet facing applications, the concept of DMZ is very important - this is the place where a hardened bastion host is placed between 2 firewalls.
• Below is the standard topology - without Datapower
• The WebServer - does almost nothing
• Most of the work is done by Webservices Gateway

• Using It is the most hardened device available in the market.
• the role of Datapower within the DMZ is that it needs to be able to stop any incoming request and provide authentication and authorization - depending on Business Requirements.
• Eliminates the Web Server and the Web Services Gateway
• More secure - easy to manage
• Below are a few of the protection which Datapower provides - 
• XDOS
• well formedness
• verify digital signature
• signing messages
• implementing service utilization to mask internal resources via XML transformation and routing
• encrypting data at the field level

• • Three basic types of Firewall
  • Static backend
  • Dynamic backend
  • Loopback

  
  

• Recommendation: All internet-facing systems that provide for inbound Web services, requests should use Datapower as their XML firewall, even when performance or security is considered unimportant.

• Recommendation: DataPower should be used as the policy enforcement point for Web services authorization. It should interact with a central policy decision point, such as Tivoli Access Manager.