Wearbles

For right posture: http://www.uprightpose.com/
For body temperature: http://www.cosinuss.com/en/vital-signs
For heart rate and performance: http://www.cosinuss.com/en/vital-signs

Oracle SOA 12 c installation issue

Parsing Failure in config.xml

http://www.programmingforliving.com/2010/10/jms-server-or-saf-agent-soajmsserver-is.html

Internet of things: IoT | Protocols

Protocol framework:

D2D (device to device):DDS: Data Distribution Service| A fast bus for integrating intelligent machines. Device and intelligent systems.

D2S (device to server): Control plane |
        MQTT:Message Queue Telemetry Transport | Protocol for collecting device data and communicating to server.
        XMPP: Extensible Messaging and Presence Protocol | Protocal connecting devices to people

S2S: AMQP: Advanced Message Queuing Protocol | A queuing system designed to connect servers to each other: Web services and business app

List of protocols:

• DDS
• MQTT: Paho
• Low battery consumption
• TCP based
• SSL/TLS
• Async
• Publish/subscribe
• Few verbs
• Payload agnostic
• QoS
• at most once
• at least once
• exactly once
• XMPP
• AMQP
• Queue based
• Messaging server based: fits into Enterprise application
• Load balancing on queues
• MQTT like publish/subscribe queue
• Filter based routing
• MQTT like QoS
• SSL/TLS
• smal packet size
• CoAP
• UDP based
• HTTP verbs, HTTP like status
• Response back after a while
• QoS with confirmable message
• DTLS
• Routing
• HTTP
• More battery
• More bandwidth
• no QoS
• SSL/TLS
• Request/resposne
• One to one 
• One to many
• no MOM
• STOMP

Communication patterns

• Telemetry: info from device to other systems
• Inquiry: information gathering
• Commands: initiate activity
• Notification: info from other systems

http://www.slideshare.net/paolopat/io-t-protocols-landscape?related=1
http://www.slideshare.net/paolopat/mqtt-iot-protocols-comparison?next_slideshow=1

Cloud and on-premise integration strategy

Until recently people in IT has been debating about various integration patterns. And EAI, AIA, WS, ESB, MOM based solutions largely solves the integration comes under:
1. Process modeling based
2. Data model based

To be on premise or cloud is new dimension. Architects, CIO etc are defining over all strategy for Cloud and on-premise, integration is missed out or only discussed at the level of feasibility(Cloud and on-premise integration). In addition there are various aspects(refer list below) which has to be considered, probably there has to be strategy for integration:).

1. Integration on-premise or cloud: Which integration should be in cloud and on-premise, how cloud and on-premise has to be integrated
2. Deployment: Where to host integration solution
3. Best practices
4. Integration cost: Every new integration adds to cost??
5. Code Portability: Same services in cloud and on-premise
6. Cloud integration skills
7. Design complexity
8. Scalability and high volume of data
9. Routing data from Cloud to On-premise or Cloud
10. Parallel processing, for Cloud to multiple targets (On-premise and/or Cloud)
11. Transformation and enrichment, when data model is not same for Cloud and target system and finaly
12. Fault tolerence

EDI standard for different industries

HL7	clinical and administrative
HIPAA	Healthcare, administration and insurer etc
X12N	Insurance
NCPDP	include most segments involved in the pharmacy services sector of healthcare
CCD	a US specification for the exchange of medical summaries, based on CDA.
DICOM	is a standard for handling, storing, printing, and transmitting information in medical imaging
Positional files	A type of file format used to represent business documents in which the records and fields have a fixed length, eliminating the need for delimiters.
Flat files	Plain text files usually contain one record per line,[2] There are different conventions for depicting data. In comma-separated values and delimiter-separated values files, fields can be separated by delimiters such as comma or tab characters.
W3C XML Schema	An XML schema is a description of a type of XML document, typically expressed in terms of constraints on the structure and content of documents of that type, above and beyond the basic syntactical constraints imposed by XML itself.
UB92	standard for billing paper institutional medical claims in the United States
OAGIS	OAGIS defines a common content model and common messages for communication between business applications. This includes application-to-application (A2A) and business-to-business (B2B) integration.
xCBL	As an XML document standard, xCBL is used primarily in B2B procurement tools for buyers, order and invoice management tools for suppliers and document routing tools for public and private marketplaces.
cXML	Business documents between procurement applications, e-commerce hubs and suppliers.
UBL	standard electronic XML business documents such as purchase orders and invoices
eHR-XML	An electronic health record (EHR), or electronic medical record (EMR), refers to the systematized collection of patient and population electronically-stored health information in a digital format.
ebXML	XML based standards sponsored by OASIS and UN/CEFACT whose mission is to provide an open, XML-based infrastructure that enables the global use of electronic business information in an interoperable, secure, and consistent manner by all trading partners.
papiNet	global communication XML standard for the paper and forest products industries.
STAR	An EDI standard
1Sync	Data format standard for facilitating global data synchronization.
EANCOM	is a subset of the EDIFACT standards, which takes place in the consumer goods industry use worldwide. From the EDIFACT message standards a subset of the segments used has been selected, constituting the EANCOM messages.
EDIFACT	Electronic Data Interchange For Administration, Commerce and Transport
EDIFICE	RosettaNet has several local user groups. The European User Group is called EDIFICE.
EDIEL	Is a standard describing technical arrangements for electronic data interchange (EDI) in the energy distribution sector.
X12	ASC X12 has sponsored more than 315 X12-based EDI standards and a growing collection of X12 XML schemas for health care, insurance, government, transportation, finance, and many other industries.
TDDC	Standard Electronic Data Interchange [EDI] standards primarily for transportation.
WINS	Warehouse Information Network Standards. A set of EDI standards for warehousing and distribution.
RosettaNet	RosettaNet standard is based on XML and defines message guidelines, interfaces for business processes, and implementation frameworks for interactions between companies. Mostly addressed is the supply chain area, but also manufacturing, product and material data and service processes are in scope.
CIDX	Standard for Chemical Industry Data Exchange
PIDX	Standard for Petroleum Industry Data Exchange
VDA	VDA-FS is a CAD data exchange format
IFX	Card and Payment
VICS	Voluntary Inter-Industry Commerce Standard which is used by the general merchandise retail industry

Oracle B2B Design patterns

• B2B Gate way(Async): Use B2B as a gateway for all trading partner integration. Gateway solution should persist data in EIS( using File,DB, JMS) and B2B processing system can take it further.
• Fault tolerant
• Increase Reuse
• Extendable
• Guaranteed delivery can be designed
• Scalable
• Time to market

• B2B processing hub(Async): Will take care of end-to-end processing of B2B messages
• Handles each message uniquely
• Would require complex error handling mechanism
• Single point of failure

• B2B Message forwarding(Async): Combination of B2B Gateway and Processing system; B2B gateway should work as explained above however B2B processing should be design to handle further processing of B2B message.
• Moduler
• Extendable
• Scalable 
• Reusable  
• Time to market

• Orchestration: Is similar to B2B processing hub but it should be sync
• Extend B2B processing beyond EDI
• Fault and error handling
• Reusable
• Moduler

• Gateway+orchestration

• B2B Translator: Use of B2B is limited to translating the EDI's.

• B2B Poller: Advance File adapter(poll file and parse it to XML).

Known issues with B2B: 

• De-batch the EDI and in some cases requirement can be to process whole batch, in such cases there aggregator component.
• Out of box XML translation(Sync), it is very handy however again it processes only one EDI txn at one time.
• B2B can not be used as webservice. 

Oracle SOA 12c and B2B 12 C installtion

Understanding the installation

For B2B you would require following:
1. Oracle B2B
2. Oracle SOA and BPM ( pre-requisite)
3. Oracle Weblogic and Coherence ( pre-requisite)
4. SOA infrastructure ( pre-requisite)
5. Database ( pre-requisite)
6. JDK ( pre-requisite)
7. Jdeveloper ( pre-requisite for design time)

Installation mode:
1. Development and learning: you can use quick start which have bundled all with java DB
2. Production: you need all the distribution listed

Distributions can be downloaded from Oracle software delivery cloud:  edelivery.oracle.com

Binaries:

fmw_12.1.3.0.0_b2b_Disk1_1of1.tar

fmw_12.1.3.0.0_b2b_Disk1_1of1.zip

fmw_12.1.3.0.0_b2bhealthcare_2.jar

fmw_12.1.3.0.0_infrastructure.jar

fmw_12.1.3.0.0_osb.jar

fmw_12.1.3.0.0_soa.jar

fmw_12.1.3.0.0_wls.jar

jdk-7u60-linux-x64.tar(used)

jdk-7u80-linux-x84.tar.gz

server-jre-8u31-linux-x64.tar


Steps for jdk
jdk-7u60-linux-x64.tar(used)
Extract:
tar -xvf jdk-7u60-linux-x64.tar
Move it to desired location:

mv /source directory/sourcefolder /target directory
mv /home/jdk1.xx /home/java

and you will get jdk in /home/java/jdk1.xx

Steps for Infrastructure:
export JAVA_HOME=<jdk location>; here it would be /home/java/jdk1.xx

<JAVA_HOME>/bin/java -d64 -jar fmw_12.1.3.0.0_infrastructure.jar

• Provide oraInventory location(for first time only, for other select the existing)
• Welcome page
• Installation location: choose your location(the installation user must have write access to the location, to create Oracle home)
• Installation type: Fusion Middleware Infrastructure
• Prerequisite checks
• Specify security updates, specify details in case you need it.
• Installation progress, next (you may save the response file for your verification)
• Installation complete(shows you two things)
• Installation Location
• Oracle Home location
• Log file location
• Feature set installed successfully
• Click Finish and you are done.

Further steps: I did not time to update rest, however you may use oracle's documentation, apologies! or you can drop me a message if I can be help.

madhavendra.mishra@yahoo.com

Oracle B2B 12 C design help

For Hands on:

https://drive.google.com/folderview?id=0B-JxCNrHSh7yeU50VjRSRk13NjA&usp=sharing
https://svgonugu.wordpress.com/2014/09/26/service-bus-12c-a-hands-on-tutorial/

B2B Design:

Pattern 1:
http://docs.oracle.com/cd/E23549_01/doc.1111/e17364/introaiab2b.htm
Pattern 2:
B2B as translator service
https://blogs.oracle.com/oracleb2bgurus/entry/osb_-_b2b_integration_-_edifac
Pattern 3:
Integration possibility with OSB:
https://community.oracle.com/thread/2318828?tstart=0
Pattern 4: 
Integration as a HUB
http://anuj-dwivedi.blogspot.in/2011/05/implementing-oracle-b2b-11g-as-hub.html
Pattern 5:
B2B for positional and delimited data
http://anuj-dwivedi.blogspot.in/

Other ref:
https://docs.oracle.com/cd/E28280_01/user.1111/e10229/bb_webservice.htm#XBBUG1751

Licensing with OVM

Some documents for reference:

http://www.oracle.com/us/corporate/pricing/partitioning-070609.pdf

https://technology.amis.nl/2015/02/02/changed-licensing-rules-exadata-x5-2-oraclevm/

https://www.gartner.com/doc/2968817/new-x-generation-bring-pricing

http://www.fishbowlsolutions.com/fishbowl/groups/public/documents/white_papers/029250.pdf

http://whywebsphere.com/2012/02/16/ibm-and-oracle-software-licensing-and-support-in-virtualized-private-cloud-environments/

http://mokumsolutions.com/chapter-4-oracle-vm-server-sizing-installation-and-updates

Understanding B2B

Important questions:
1. Who are your trading partners?
2. What B2B specification will be used for message exchange(EDI, EDIFACT, HL7, Custom, HIPPA etc)
3. What protocol(AS1,AS2, ebMS) will be used, transport medium(  FTP, HTTP)
4. Synchronous or Asynchronous
5. Connection pattern

1. Point-to-point: Invoice
2. One-to-many: quote for price
3. hud and spoke: HIPPA
4. Many-to-Many: emarkets

B2B standards:

• ISO: International Standards Organization 
• UN/CEFACT: United Nations Center of Trade Facilitation and Electronic Business
• OASIS: Organization for Advanced of Structured Information and Standards
• OAGi: Open Applications Group
• RosettaNet
• ebXML
• Biztalk
• SWIFT:Society for worldwide Interbank Financial Telecommunication

https://en.wikipedia.org/wiki/Electronic_data_interchange