Oracle SOA Blogs- Sandeep

In 12c, the OWSM security policy configuration is saved to a separate file called wsm-assembly.xml In order to update values in wsm-assembly.xml, the service needs to use the <policySet>. e.g. A configuration plan is required to change both a HTTP port number, and the csf-key used by the oracle/wss_username_token_client_policy OWSM policy. Replacement without configuration plan: Open wsm-assembly.xml file and add below code <?xml version='1.0' encoding='windows-1252'?> <orawsp:wsm-assembly xmlns:orawsp="http://schemas.oracle.com/ws/2006/01/policy" xmlns:mds="http://xmlns.oracle.com/mds">    <sca11:policySet xmlns:sca11="http://docs.oasis-open.org/ns/opencsa/sca/200912" name="policySet" appliesTo="SCA-REST-REFERENCE()" attachTo="REFERENCE('Get_Service_Now')" orawsp:highId="2" xml:id="SCA-REST-REFERENCE__REFERENCE__Get_Service_Now__"> ...

Hello, In Oracle SOA 12C, Oracle added few new adapters which can be used across with BPM/BPEL/OSB components. One of them is "Microsoft Message Queueing".  Microsoft Message Queuing is similar to weblogic JMS queues, difference is it's a Microsoft technologies. Microsoft Message Queuing provide most of the all functionalities and use case implementation which are provide by JMS queues. During the design of SOA applications it is inevitable that from time to time you will need to interface with Microsoft-based applications. While technologies like SOAP and REST do a great job when  request-reply  communication is needed, most people struggle when a  messaging-based  communication is required. This blog will present two approaches to get messaging working between Microsoft and  SOA Suite 12c . Before going to implementation part, let c what is it and why we should use it. What is MSMQ: Microsoft Message Queueing (MSMQ) is a message ...

Hello Everyone, Hope you are doing well, Today i am going to discuss how to manage domain credential stores and how we can create some WLST based ANT Scripts, But before that i will discuss what is it and why we use it. A credential store is a repository of security data (credentials). A credential can hold username and password combinations, tickets, or public key certificates. Credentials can be provisioned, retrieved, modified, or deleted, but only by a user in the appropriate administration role. The following sections explain how an administrator can manage credentials using FMC pages or WLST commands, and how code can access data in the CSF. Managing Credentials with Fusion Middleware Control: Fusion Middleware Control allows the management of credentials in a WebLogic domain, regardless of the type of credential store provider used in the domain. Managing Credentials: This section explains the steps you follow to manage credentials in a domain credential store wit...