TechDT

  The new home is techtrantor.com

Yesterday I was helping a customer in provisioning OIC, just after he activated his user account in a new OCI tenancy. I have done this many times and there is never an issue, but the customer ran into an error immediately: 401: Unable to create integration instance, the principal is NOT authorized. The message is quite clear and points out in to user permissions, so I asked the customer to check if his user was part of the group: OCI_Administrators ->  he was. The second thought was about entitlement roles, so we went and verified if the user was allowed to access/create that specific service -> he was. The next step took some time to figure out since we were doing this via the phone, but it turns out that he was trying to create an OIC instance in the default compartment -  ManagedCompartmentForPaaS.   It turns out this is a special compartment dedicated to all the PSM based platform services. Once the compartment was changed, the provisioning went smooth as always :) 

image from oracle blog Back in 2014 when I was still a Consultant, at one of my customers (a Telco company in Finland) it took me around 6 weeks to get test and production Weblogic environments to deploy the application (Tibco MDM). -    Meeting with Infra team to discuss hardware specs (1 hour) -    Procurement process (4 weeks) -    Meeting with dedicated Offshore team responsible for WLS installation (1 hour) -   Configuration of  WLS domain and other specs (1 week)   Nowadays, once we have agreed on hardware and WLS domain specs, we can provision a full Environment  in less than 15 minutes :) That is fantastic. The entire offering is available in the OCI Marketplace:  There are 3 WLS Editions available: Oracle WebLogic Server Standard Edition Oracle WebLogic Server Enterprise Edition - includes clustering Oracle WebLogic Suite - includes Oracle Coherence for increased performance and scalability, and Active Gridlink for RAC for advanced database connectivity With 2

The November release for the Oracle Integration Cloud (OIC) delivered the Trigger capability for the Kafka Adapter. Up until now we could only use Scheduled Integrations to consume messages. Now, we can make use of the App Driven Integration which will be triggered whenever new messages arrive to the subscribed Kafka topic. It's noteworthy to mention that this feature requires the connectivity agent in order to run. See the official release notes here : If you are new to the OIC Kafka Adap ter, start with this post , where I covered Kafka installation, OIC prerequisites and the  consumer/producer capabilities. Now I am going to cover the Kafka Adapter as a Trigger. In my Kafka server I will create a new Topic for this specific use case. Create a new Kafka topic Using the command line: ./kafka-topics.sh --create --bootstrap-server localhost:9092 -- replication-factor 1 --partitions 1 --topic TopicTrigger Create a new Connection The connection from the previous post was only for Invo

Up until recently we would need to generate a Salesforce (SF) Enterprise WSDL in order to create a connection in OIC. That is no longer the case, it's extremely easy to set this up :) Create a SF Connection I have a SF developer instance. Interesting to note that the OIC Connection wizard for SF only offers 2 instance types - Production and Sandbox. My developer instance credentials only work with the Production type. Apart from that you just need your SF credentials and the API version (which you can find inside your SF instance) And that's it! And now you may ask...but how does this work for a Trigger? Well, that requires some configuration in the SF side, and on top of that, we may get several WSDL's depending on how many business objects we configure. But the OIC team came up with a smart approach which does not require changes in the SF Connection. Let me show you the process. Configure SF for Business Events (Trigger) Create an Outbound message in the SF Setup. This i