faruk's learning journey

last week I have faced a problem on one of my asynchronous process which got an exception in the middle. and wanted to move forward it. the only one way to achieve it with calling the caller of this process. meaning returning with callback to the caller like this process is making it. at first the difficult part was finding the callback url which is being sent by soa infra as a ws-adressing tag in soap header. supposing you have a process which's url is in that process you have a partner link was defined in composite.xml with a wire definition like below : with this definition, your callback url becomes like but if you wanted to call your method via soapUI, you would get an exception about something but if you call via java or the page provided with mantioned url, you will be able to take forward your process. one other concern is the correlation. it is also a very easy problem. you have to send the information via soap header which is shown below. the fields which ha...

in addition to part 1 , we have some other duties to do. supposing that you have created some interfaces that clients connect to SOA Suite, these interface wsdls' do not have binding part in abstract form, but in runtime, SOA Suite generate it for clients. if you have an intent to port these abstract wsdls while unbeknownst to the caller parties about the porting from SOA Suite to OSB, perhaps you want to use these abstract wsdls as a proxy service, which clients want to connect with OSB. to make this, you must generate binding parts as SOA Suite does. below is a simple snipped part of abstact wsdl (wsdl that generated by jdev for composite to soap interface ) that shows the portType which has not got the binding part. when you deploy a composite which has an soap interface depending on this wsdl to SOA Suite, this portType has a binding part as shown below. as you can quickly realize that, is has an easy pattern for this part. you can see it blow abow example show...

it is sometimes needed to iterate the process number of times that defined in runtime. if you had used a programing language like java,C,C++ etc. , It would have been very easy to make it. but infect in ant it is some hard to do it without 3rd party libraries. below ant snipped part is a way to achive this. enjoy it.

In SOA Suite 11g, you can use MDS to manage and centralize your datamodel. if you have a big project ( if true, most probably you are using AIA or at least your own methodology ), perhaps mds would have a wide range of files that composed with wsdl and xsd files. To connect these files with each other, you can use either one of relative path or "oramds:/XXX/YYY" approach. it is recommended to use relative paths in whole of the datamodel. although this suggestion is very imported, you can not some times use this relative path approach, especially in requestorABCS or providerABCS (these are the connector services from/to the systems). in development time and time runtime, this ABCS wsdl files' are the points that entering to MDS. so you have to use "oramds" key word. it's not important where or how much you use the keyword (oramds) in your datamodel with while using SOA Suite, but if you want to use this datamodel out of the world , lik...

if you are wondering with the threads in request-response pipelines, this shorty brief explanation is enough for developers and operator for defining the rules. In Oracle Service Bus, several transports for proxy and business services provide a configuration option called "Dispatch Policy" that lets you associate a Work Manager with a service to prioritize service work. This section describes how proxy and business services use Work Managers. By configuring the Dispatch Policy of an Oracle Service Bus proxy service, the startup and execution of its request pipeline are governed by the rules of the Work Manager. For example, given a proxy service using a Dispatch Policy with a Max Constraint of 5, the proxy service will have no more than 5 request pipeline tasks executing simultaneously. While the request pipeline is governed by the proxy service's Dispatch Policy, the response pipeline is governed by the business service or Split-Join Dispatch Policy. The RouteTo ac...

We have a web service which has a basic auth. policy on it. I can call it with soap but while invoking java client which generated with weblogic ant tools, I can not achieve to call it with success. it gave me 401 http code all the time. then I made a call with soap and realized that it is sending Authorization http header while invoking. then made I small change with my code like BindingProvider bp = (BindingProvider) oloPortalTHKEndPoint; Map context = bp.getRequestContext(); Map > headers = new HashMap >(); headers.put("Authorization", Collections.singletonList("Basic " + new String(Base64.encode(newString("username"+":"+"password").getBytes())))); and Bob's your uncle here the detailed information about basic auth. http://en.wikipedia.org/wiki/Basic_access_authentication

this small line of code save my several times again. sudo tcpdump -v -w capture2.log -i eth0

in some cases, it can be difficult to explain the right order of the configuration of adaptor (db, AQ) on soa suite 11g. it is quite simple. first you have to have a datasource then, in jdev composite adaptor creation editor, you must define the outbound name after then you have to define it in deployments' outbound properties under the properties tab. the last think you have to do is, connect the two configuration properties names together. to do this : and, Bob's your uncle

It's sometimes - especially in uat, not in live - necessary to capture the soap header for debugging after appling the securty policy in soa suite 11g. if you apply regular logging policy after the security policy, you won't see any security tokens. but you must enforce it inside the policy definition. is it quite simple to do. you can follow the screen shots respectively. it must be for only checking some tokens, meaning debugging. before prod, you must rollback the changes.

This evening I spend my time to create a war that serving web service both soap and rest style together with spring. Although it is easy to create it, the java developers often faced some annoying class cast or class not found exceptions. in fact responsible from these errors are not the developers but the designers, but I don't know why they are stay developing packages with same name and also put them into rt.jar and also another package and so on. It is clear that the way preventing these errors is putting one class only one package and also a package is must be ONLY one place, not two or more. I want to prove it to you, if you have a big system that contains a lot of libraries, just grep the jars for packages and find it in your system. you will most probably see that packages are represent more than one jar. and the other thing is the jar names. why you don't give the jar name form the package name. I thing it must be a restrinction package names and jar names must iden...