Sujeeth Pakala

I would consider following "few" aspects to choose an ESB product

- Product extensiability
- How far product can integrate within current infrastrucutre (several end point connectors like SAP, SFDC, CICS.., supported dataformats XSD,CSV, IDOCS, Copybooks..)
- Non-functional aspects like supported secutiry mechanisms, transactions
- How quicly and easily solutions be implemented e.g. graphical coding is prefereable
- Performance and Runtime governance capabilities
- Operation and maintenance cost
- Knowledge available internally with in org. and external to org.
- Atleast try to do a reference check with other partners who are already using a proposed ESB solution..
- Vendor support..

No matter if ESB is open source or commercial. In my view total cost of owenrshi for both are same !

1. Do you have 2 explicit bindings for both SOAP1.1 and SOAP1.2 versions in WSDL ?
2. Which binding are you using to invoke an operation from your code?
3. Make sure to use correct SOAP version for the corresponding binding.
4. Based on your analysis, it have a feeling that the service provider supports only SOAP1.1
5. Try with: MessageFactory factory = MessageFactory.newInstance(SOAPConstants.DYNAMIC_SOAP_PROTOCOL);

1. Do you have 2 explicit bindings for both SOAP1.1 and SOAP1.2 versions in WSDL ?
2. Which binding are you using to invoke an operation from your code?
3. Make sure to use correct SOAP version for the corresponding binding.
4. Based on your analysis, it have a feeling that the service provider supports only SOAP1.1
5. Try with: MessageFactory factory = MessageFactory.newInstance(SOAPConstants.DYNAMIC_SOAP_PROTOCOL);

Firstly question is very high level.

Based on the business model you explained, consider B2B and B2C scenarios. There could be other

- You could expose a service which notifies car seller about expression of interest on a particular car from the website.
- You expose a service to enable clients (customes and organizations) to receive several alerts about information particular to their criteria (something like magical subscriptions to spam emails ;-) sorry for strong reasoning)
- You could expose a service to accept bids from clients

You can think of other scenrios based on the scenarios and business..

Also, think of SalesForce. It is delivered as a service cluster to the customers. It contains several services.

Hopw this helps to understand importance of services :-)

The task you have been asked is to do is called "Service Design". This task needs more of functional thinking. Forget the technical aspects for the moment.

You are exposing web service, that means you are providing service to consumer(s).

Ask your self:

1. Why service?
2. What service has to do? Try to clissify your service. As standard, service can be Utility, entity or task service.
3. What data is needed to perform <answer from question2>?
4. Is there a response is returned after performing <answer from question2>?
5. How service is exposed? : which data type : XSD, JSON .. ?, transport : HTTP, HTTPS, JMS ... ?
5. Non-functional requirements (Max message size, response time, number of requests per second, secirty..). This is advanced level. Normally this should be defined by the Solution Architect (or the person who is responsible for the overall architecture of system and identified the service)

Couple of suggestions:

1. Do not provide service particular for a customer. This is traditional application to application coupling. Strictly antipattern. So

" These interface operations and data type definitions align with the PIM model used by the Consumer integration stream. "

DO NOT DO IT.
2. Do not reveal the internal subsystem details to consumer. Do they really need to know those? In you case Informatica or pther provider system.
3. If you were able to classify your service from <question2>, use the appropriate data model from MDM. DO NOT extract the service interface and WSDLs as it is from MDM. It gives 360 degree view of particular entitiy (for example customer) which is normally very very big WSDL with several operation which are not required.
4. Visualise as much as possible in a modelling software and analyse well to fulfill the <answer from question2>
5. User service versioning

In my view, SOA is just a concept with some architectural views, design principles , patterns, standards, rules and governance.

ESB compliments in building SOA landscape in integration area.

Hello

A stupid question. What is RMC, seen in quite lot of posts.

Can any one point to the RMC url please?

Thanks.

Why do you need SOAP message ?

Are you trying to program a web service client to send SOAP message to a service provider?

Here you are doing this which is not good design.

Java Object (JAXB) -> String (XML) -> Java Object -> Java Object (SOAP) -> String (SOAP).

my query is how can we convert this plain xml into a SOAP req

To build SOAP message, you do not need to unmarshall object to string.

There are web service APIs like JAX-WS which has support for JAXB and SOAP API. Through this you can develop a WS client program which builds SOAP message for you.

Which web service client API are you using? JAX-WS or JAX-RPC ?

There are 2 types of web service clients can be developed

1. Static : The static use case for a JAX-WS client assumes that you already have a WSDL contract (stubs are generated in case of JAX-RPC and not generated in case of JAX-WS due to use of annotations)
2. Dynamic : Used when the WSDL is not known.

The "Proxy" class you see is dynamic web service client.

I can not answer without knowing which API are you using.

First pre-requisite to gain SOA knowledge is change in mindset and different thinking.

The book "SOA Principles of Service Design" by thomas erl is good start for beginner.

Follow the book series here: http://www.servicetechbooks.com/

You could also do some certifications on SOA delivered by Arcitura

http://www.soaschool.com/certifications

Good Luck.

Yes, I agree with you.

I am still thinking like beginner

How many parts are there in the wsdl messages ?

Web service is extension of web application. I will try to explain web service with comparison to web application.

In web application, the web application descriptor where your web application is described (think of contract between your web application classes and container, although strictly it is not)is used by container to initiate your web components and enable web application listening on URL at a given path (URL / end point URL). The only user(consumer) for your web application classes is container and it is wrapping your classes and exposing as web application.

A web service application is used by consumers out side container. So for them, the application is described in a file (something like deployment descriptor) called web service description language (WSDL). Like a web application, WSDL file contains the URL path where application is listening is called "End point URL".

Like the classes of web application are used by container, WSDL file is used by the web service client (programs or container). Hence WSDL is used by the software programs which communicate with the service and not human beings ;-).

Is both wsdl/webservice URL & end point URL is needed to obtain response for the request via java code?

So, to develop service client, definitely WSDL (deployment descriptor) is needed and this contains end point URL (servlet path).

For your question in second post :

It is nature of web services that it returns the WSDL file when you enter this URL in this format <web service end point>?wsdl in browser. So, this is how soapUI reads the WSDL file and create sample request...

I think the term web service URL is incorrect instead end point URL is right word.

Follow this for java web service tutorials.

Hope this helps.

OK. Now, this depends on the type of wrapping (doc/literal/wrapped or doc/literal/unwrapped) style you defined in the service client.

I suspect you are using settings in annotations for doc/literal/unwrapped and using Holder for response.

Hello Claude

Thanks for posting the problem and solution ;-)

Can't the EJBs are declared in EJB project, package as jar, kept in WEB-INF/lib folder as jar file and access them via HTTP as REST ? This way EJBS can also be accessible via other clients and more reusable. No ?