Wednesday, 23 November 2016

Digital Signature


A digital signature (not to be confused with a digital certificate) is a mathematical technique used to validate the authenticity and integrity of a message, software or digital document.

The digital equivalent of a handwritten signature or stamped seal, but offering far more inherent security, a digital signature is intended to solve the problem of tampering and impersonation in digital communications. Digital signatures can provide the added assurances of evidence to origin, identity and status of an electronic document, transaction or message, as well as acknowledging informed consent by the signer.

In many countries, including the United States, digital signatures have the same legal significance as the more traditional forms of signed documents. The United States Government Printing Office publishes electronic versions of the budget, public and private laws, and congressional bills with digital signatures.

How digital signatures work:


Digital signatures are based on public key cryptography, also known as asymmetric cryptography.

Using a public key algorithm such as RSA, one can generate two keys that are mathematically linked: one private and one public.

To create a digital signature, signing software (such as an email program) creates a one-way hash of the electronic data to be signed.

The private key is then used to encrypt the hash. The encrypted hash -- along with other information, such as the hashing algorithm -- is the digital signature.

The reason for encrypting the hash instead of the entire message or document is that a hash function can convert an arbitrary input into a fixed length value, which is usually much shorter.

This saves time since hashing is much faster than signing.

The value of the hash is unique to the hashed data.

Any change in the data, even changing or deleting a single character, results in a different value.

This attribute enables others to validate the integrity of the data by using the signer's public key to decrypt the hash.

If the decrypted hash matches a second computed hash of the same data, it proves that the data hasn't changed since it was signed.

If the two hashes don't match, the data has either been tampered with in some way (integrity) or the signature was created with a private key that doesn't correspond to the public key presented by the signer (authentication).

A digital signature can be used with any kind of message -- whether it is encrypted or not -- simply so the receiver can be sure of the sender's identity and that the message arrived intact. Digital signatures make it difficult for the signer to deny having signed something (non-repudiation) -- assuming their private key has not been compromised -- as the digital signature is unique to both the document and the signer, and it binds them together. A digital certificate, an electronic document that contains the digital signature of the certificate-issuing authority, binds together a public key with an identity and can be used to verify a public key belongs to a particular person or entity.






Wednesday, 28 September 2016

HOW TO CONSUME REST WEBSERVICE IN ORACLE SOA 12c
(REST ADAPTER IN SOA 12c)

1.Create a SOA Project named RESTInvoke



2.Create a Synchronous BPEL process




3.Drag and drop the REST Adapter into the external References




4.Give the name for Rest Reference and choose the appropriate option



5.Enter the Base URI and the resource path of your Rest WebService






6.Create Methods to invoke the WebService



7.Give name for the method,choose the resource path and then choose the operation that you are going to perform.Here I have used GET method.



8.Create URI parameters for the request.




9.Give name for the parameter and choose the style for the parameter.There are two Styles available.

#QUERY parameters are the most common type of parameter, which is appended to the path of the URL when submitting a request.

#  TEMPLATE parameters are a flexible way of parameterizing the actual path of the request.

I have selected query parameter.We can specify the default value also.I have given 77 as the default value.







10.Click finish to complete the rest configuration wizard.





11.Create a wire between BPEL and Rest Adapter



12.Create two json Variables for Invoke input and Invoke Output







13.Drag and drop the invoke activity.




14.Create a wire between invoke and RestReference




15.Choose the method that we are going to invoke and choose the input and output variables.






16.Map the input variables.





17.Map the Output Variables.







18.Now you can deploy and test the Service.











Tuesday, 27 September 2016

HOW TO CREATE A DECISION TABLE IN ORACLE SOA 12c

1.Create a SOA project DecisionTableDemo


2.Create a synchronous BPEL DecisionTableBpel



3.Drag and drop the Business Rule component



4.Create rule called EmpGradeRules



5.Assign Input and Output for the rules.














6.Create a wire between Bpel and Rules





7.Double Click on the Rules to define the ruleset



8.Click on the + sign in the Rules Designer window near the Decision table to create the decision table




9.Enter the description as EmpGradeTable



10.Create a valueset and attach it to the process fact





























11.Choose the RuleSet1 to open the rule Designer window




12.Specify the condition




13.Specify the action



14.Now enter the rules.If the salary is 1000 then the result should be Grade C.If the salary is 2000 then Grade-B.If the salary is 3000 the Grade C.












15.Drag and drop the business rule component in the Bpel




16.Double click on the Business Rule and Select the decision table that we have specified



17.Assign Input and Output facts








18.Now you can deploy and test the process