faruk's learning journey

I have a customer who is struggling with db issues for several months, we have 550 million composite instances which are waiting to be purged. these instances takes nearly 12TB tablespace. so we are making investigations on this database. I realized that if i wrote a script which finds the ratio related the holding space behind the individual composites which are part of customer's order management process, it would worth the time I will spend. first I wrote a function which takes only composite instance id then one small select is enough to see which composite instance is taking the most size of db. this result is related with all spaces which can the different from instance to instance. the result would be like that default/ProcessSalesOrderEBF!13.10.25-0954*soa_1c1526b7-19c6-4633-bca4-bc06f1f157ad 43.8553333333 default/InterfaceOrderToProvisionEBF!13.10.24-1057*soa_91f81f2c-9d9c-4ef6-aa8e-1403138e3e34 12.6453333333 default/ProcessOrderToOLOProvABCS!13.12.03-1410*soa_...

occasionally, we need to transform from xmldate to custom date format. here is the clue script, enjoy it not a big deal :) translate(translate(string(substring-before(substring-before("2013-05-03T19:12:32.000+03:00","+"),".")),"-","/"),"T","-")

if you faced trouble whilst exporting configuration from eclipse workspace with ant and striving to find a fix to it. here it is. only put the on the ant script. the exception stack trace is Caused by: org.osgi.framework.BundleException: Exception in com.bea.alsb.core.AlsbCore.start() of bundle com.bea.alsb.core. at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:734) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683) at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381) at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:299) at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:440) at org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:268) at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107) ... 28 more Cau...

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