Finally resolved "unknown certificate"

Added both the certificates to ${USER_INSTALL_ROOT}/etc/DummyServerKeyFile.jks

Added both the certificates to ${USER_INSTALL_ROOT}/etc/DummyServerTrustFile.jks

Added both the certificates to ${USER_INSTALL_ROOT}/java/jre/lib/security/cacerts ??

Example command
/opt/WebSphere/AppServer/java/jre/bin/keytool -import -file -keystore -alias server.com01 –trustcacerts

If I add the certificate elsewhere need some more configuration in WAS.
http://www-128.ibm.com/developerworks/websphere/techjournal/0502_benantar/0502_benantar.html

Why it should be so hard?

Here are my series of thoughts on things that could have been simpler!

- Why it should be so hard to print request and response soap xml in WebSphere Application Server 5.x?

- Why it should be so hard to deploy one damn code change in WAS? It reminds me of COBOL days, flipping floopy-disks for compiling programs and waiting for 'minutes' to test a change.

- Don't send remainders to those who already did the job (timesheet submission or whatever).

- use urn: instead of http:// for name spaces.

Smartest SOA - Just do it.

Yes. The smartest implementations of SOA should - Just do it.

It's inevitable next-step in IT. Whether a company likes it or not, if their architecture is not SOA in this year, it will deemed to be outdated and still lurking in past. As a consultant I would not rate high an organization that hasn't started implementing SOA already.

Like it or not, the first steps in SOA implementation is all about web services. In most of the Fotune 500 and like-minded but not-so-fortune companies, should have started exposing webservices to one-another.

Sept 18th - ImmigrationVoice Rally in D.C

To highlight the long-delays in getting permanent residency - legal immigrants, members of IV (ImmigrationVoice) have planned to conduct a rally in D.C and address few major bottlenecks in the Employment-based immigration process.

The rally will take place with more than thousand immigrants walking down the streets with banners and the usual stuff you can imagine in a peaceful rally.

For more information - http://immigrationvoice.org/

Open secret : ESB helps outsourcing more work.

Currently offshore teams may not have access to various webservice endpoints (URLs) in various environments. Thus we may not be able to use them effectively during end-to-end testing.

If we can introduce ESB (Enterprise Service Bus) SOA pattern in its basic form i.e, mediation/redirection, there is a scope for saving lot of time and $$K.

Assume that a dumb ESB server some URLs like the ones given below for address validation and redirect those URLs to actual URLs provided by the service-provider application.

Offshore team can be setup to access the below URLs and forever they have the ability to call the services provided by the above systems. All that they need is to configure their desktop / local-UNIX server environment with the below standard URLs.

http://dev-d1.soa-comp1.com/esb/addressvalidation
http://dev-d2.soa-comp1.com/esb/addressvalidation

http://test-t1.soa-comp1.com/esb/addressvalidation
http://test-t2.soa-comp1.com/esb/addressvalidation

http://prod.soa-comp1.com/esb/addressvalidation

What do you think?

My new design pattern : skip step

SOA - Business Process Patterns:

Here is a pattern, that I never read about or came across. I would like to share with the programming world about "skip step" pattern. In this design pattern, one would write the application logic to use flags to skip certain steps in the use-case scenarios. Typically the need for "skip step" arises at each coarse-grained and down-stream dependent function-calls. In the skip-step pattern, one can store the flags as skip-flags outside the execution-environment. By changing these flags the application can be made to include/skip certain steps in the process flow. This design pattern has been extremely useful, in particular in EAI applications.

The advantages of "skip-step" pattern as occurs to me:

Assume a use-case that goes through a, b, and c steps. Here a, b and c steps interact with A, B and C external systems or database.

1) Skip a or b or c during the execution, if that step is not ready or not required anymore.
2) Step a is successful and step b failed. Next time you want to execute the same flow/order and want to skip a.

SunRocket is history. What to do?

I use VOIP phone here in US and at also at my parents and in-laws houses abroad. I use Vonics. I heard that SunRocket is gone out of business. Glad that I am not a customer of that Company which I considered at the time of choosing VOIP service.