How To Integrate wsdl and xsd Files By Using wsdl.exe

How To Integrate wsdl and xsd Files By Using wsdl.exe

Dec 14

When you work inside platform independent teams, web services and service oriented approaches are valuable. Especially in telecommunication sector, systems are mostly constructed on Unix – Linux based OS platforms and Java, C,  C++, Perl based software products and services. But the world is converging to each other day by day, companies share their services with outside or corporate with other companies. Value Added Service (for example the business corporation between a telecom company and a finance company) are the most chosen way of making a difference.

In a world that has more broaden borders than it has never before changes the architectures and design types of software. Contract First Design comes into prominence inside this kind of world. Teams or companies that uses different types of platform and works for the same project goal, starts to design their systems as black boxes tries to identify communication methods and services that they will share with each other.

In xml web services world this means to prepare your wsdl file to describe what kind of functionality you share with outsiders and xsd files that provides necessary metadata to describe data that will transform through communication channel. These are boundaries of these two black box systems which are basically the fundamentals of successful integration project.

What is next then? Read more…

SOA Manifesto

SOA Manifesto

Feb 15

As most of you know and use in the base of their internal enterprise level application architecture, service oriented architecture (SOA) has some tangible benefits. Reusability, governance, agility, interoperability, discoverability and so forth.

 

Today I would like to share SOA manifesto with you. Since October 2009 SOA has such a manifesto and up to now 700 different parties have signed this manifesto.  You can read it from here in detail, it is translated 9 different languages. But you can get useful information at a glance from below.

  • Business value over technical strategy.
  • Strategic goals over project-specific benefits.
  • Intrinsic interoperability over custom integration.
  • Shared services over specific-purpose implementations.
  • Flexibility over optimization.
  • Evolutionary refinement over pursuit of initial perfection.

 

At the first reading it had reminded me the Agile ManifestoSmile Maybe this is because of the protection approach to valuable characteristics. This manifesto was one of my motivators in front of my table on the pane at my ex company.

 

By the way, since we talked about agile, today IBM Vice President Julie King was our guest speaker at the company. She talked about how do they manage agile processes and lean development process inside IBM. After her 30 years development experience it was really easy to conduct on the same language with development crewWinking smile There was  a really nice slide deck which was showing the degradation over the problem calls after processes switched to agile methodologies. Maybe by a search engine miracle (or should I use failure Open-mouthed smile) she visits this page, so I would like to thank once more for her valuable visit .