Service Metering by JBI

Currently I am building web services with AXIS2. Now I am facing to create a service which records all usage of web services to a database table. Like "userId; Service url...etc".
I tried some ESB tools like Mu, ServiceMix and WSO2 but still dont know how to do that? Actually I do think there must be a way do not need use these tools.

Dear all,
while making service PO reference to PR the account ***, tab not showing Network and activity.we maintain already network and activity in PR.....
Pl Help
Thanks In Advanced
regards
ranu

Similar Messages

Any tutorial for building adapters and routing services for JBI container ?

Hi
Thank you for reading my post
is there any tutorial for Sun JBI container ?
I want to know how i can build/deploy JBI components like adapters and routing service for Sun JBI container .
another question is that , is it based on OpenESB ?
thanks

You can find a white paper on writing a JBI service engine here:
http://java.sun.com/integration/reference/techart/DevelopingAServiceEngineComponent-1-2.pdf
Also, there is a lot of information on JBI and Open ESB here:
http://java.sun.com/integration/
You ask if the Sun JBI container is based on Open ESB - it's actually the other way around: Open ESB is based on the Sun JBI container. The JBI container is a JSR208-compliant implementation, and Open ESB builds upon that implementation to add full ESB capabilities.
hope this helps -
mark

Drawbacks to developing JBI Components

From a developers perspective my instinct tells me there appears to be two drawbacks to developing a JBI component.
First, I have to waste thousands of brain cells creating/updating a WSDL.
Second, each component is responsible for XML transformation (binding). For example, each component takes the incoming content (XML) and uses JAXB or XMLBeans to get some Java objects he can work with. Then right before he sends the response he uses the same objects to set the response content.
I was under the impression that we were getting away from all that complexity? Axis, XFire, JAX-WS, JSR181, etc�.. I thought all shared a common goal of providing developers a quick way to create web services by not requiring them to create WSDLs, supporting annotations, and handling the binding automatically.
To me there is a big time difference compared to writing a JAX-WS web service running in Glassfish and writing a JBI component.
Am I seeing JBI component development differently than how it was originally intended? Perhaps I am unfamiliar with potential existing solutions.
Thanks in advance.
James

JBI has to qualify as one of the most unusual standards to ever come out of the JCP, because it primarily addresses a very small audience (implementors of JBI environments and plug-in components), yet it is of great value to a much wider audience (the users of those plug-in components), who use JBI only indirectly.
When should you develop a new service engine? My short answer is "only when you have no other choice." SEs and BCs provide support for specific application and protocol technologies, respectively. If you need such a technology, and the appropriate SE (or BC) doesn't exist, you may have a case for creating a new SE (or BC).
You always have the option of implementing support for such technology separately, outside of the JBI environment, and using standard protocols such as SOAP over HTTP or JMS to connect to your JBI environment. In theory this lets you avoid implementing some JBI component features, but practice this ends up being more costly in terms of development effort. For example, a JBI SE doesn't have to worry about implementing SOAP, or any other protocol for that matter.
JAX-WS and JBI really have different goals. JAX-WS is an API for applications, to add WS support easily to Java code. It is meant for "regular" developers. JBI defines a "container of containers", defining an infrastructure for accomplishing integration of different application technologies and communications protocols.
JBI was designed as an integration technology. Any integration technology requires "adapters" for existing applications, protocols, resources, and services. That has always been a weak point for any integration technology -- do you have adapters for X, Y and Z? The big problem was that all those adapters were proprietary, which really locked you in to a particular vendor. JBI changed that, by introducing the standardized adapter: the JBI component. From that perspective, there are plenty of opportunities to create new JBI components out there. Packageware, CICS, custom apps, etc.
JBI also creates a "composite application" environment, which I suspect is your primary interest -- composing useful applications from a variety of application technologies, such as EJB, BPEL, even XSLT, and making those applications available over a variety of transports & protocols. From this perspective, there is still plenty of space for new components. I'd like to see a service engine that supports ebXML BPSS, for example. I'd also like to see a component that serves as a UDDI registry, exposing all of the internal services within the JBI environment to design tools. A business rules engine would be cool (I believe that is being developed already). I'd like to see an engine that integrates portal support, perhaps using WS-RP. I'd like to see some scripting engines, as well as a lighter-weight process engine (BPEL is very capable, but can be a problem if latency / throughput are of primary concern). I've love to see a work flow engine (XPDL would be very useful).
That's off the top of my head. I'd say that the current crop of components is enough to accomplish some very interesting, useful things. Their main accomplishment is to isolate you from all the plumbing underneath the covers -- you can concentrate on creating BPEL, or EJB, or XSLT, or configuring (not coding) SOAP, JMS, FTP, etc, access to/from BPEL, etc. Although JBI is a very interesting technology, I'd say it is doing its job when it 'disappears' into the plumbing, and application developers aren't even aware that it is there.

Integration with ESB and JBI

I'd like to know if somebody has used Oracle PM and some ESB (Enterprise Service Bus) or JBI (Java Business Integration, JSR 208) framework/product.
I am using ServiceMix and would like to know what is the best way to integrate Oracle PM and ServiceMix.
I do not know if Oracle is planning to release some ESB or JBI product. It would be nice to have a BC (Binding Component) or SE (Service Engine) to enable Oracle BPEL PM run in any JBI compliant framework.

Oracle talks of Integration InterConnect as their ESB... how does this fit into the puzzle? See the Middleware Business Integration FAQ, for instance. Also, is OracleAS Adapters replacing the Integration InterConnect adapters?
It is not easy to find concrete info, maybe that's because there are no real products yet...

Dynamic endpoint resolution in OpenESB

Hi,
I was wondering whether OpenESB also supports dynamic resolution of target endpoints. My impression so far is that I need to explicitly specify all connections from service consumers to service providers in a service assembly's jbi.xml deployment descriptor using the CASA editor in NetBeans. However, one of the strengths of the NMR in my opinion is that it can dynamically resolve endpoints to send message exchanges to. However, this would mean that the SA's jbi.xml must not contain any <connection>s, doesn't it? Does OpenESB's NMR support this at all? I would really like to be able to deploy a service consumer to a service engine without needing to explicitly specify the name of the endpoint providing the consumed service but instead specify the service interface name only letting the NMR resolve this to a matching endpoint at runtime.
Regards,
Kai

Hi Kai,
The BPEL SE supports dynamic endpoints allowing you to programatically (in the flow) change the port name, service name and address info. I've modified my flows to call an internal AddressResolution flow that calls a EJB in the Java EE SE that looks up address info from a DB. It works great but took a while to get rights as the Namespaces have to be perfect when assigning the XML to the Partner Link.
See: http://wiki.open-esb.java.net/Wiki.jsp?page=DynamicPartnerLinks
Cheers,
Paul

Where do I define how MessageExchange-XML-Payload looks alike on BC? SHORT!

Hi (again),
I think, I finally understood the concept of the abstract service definitions.
Nevertheless, one thing remains unexplained to me.
If my self-coded BC (need to use axis for a specific legacy application, therefore coded an own BC) receives a MessageExchange in its thread started at the ComponentLifeCycle, where is the content of the xml-payload defined? Or will I use some parsing engine, hoping I do find my parameters within the xml-msg?
As I/my BC don't/doesn't support deploying of service untits and JBI spec page 65 states that in jbi.xml for a binding component details about services MUST NOT be specified, how will I solve this?
As of my knowledge, deploying additional service untis is obligatory, right? Or can/must I somehow deploy those descriptions?
thnx again for reading (and answering),
applet5

I just found the method
public org.w3c.dom.Document getServiceDescription(ServiceEndpoint ref) {
in Component interface. Do I simply return a wsdl-document here? will I - in my case - simply hardcode this into my code or read it from file system??
thnx

ESOA Cockpit ?

Hi,
I ve just gave a try to a sample read of a new SAP Press Book "Developing Applications with eSOA".
The authors describe a new tool (which seems to sit on top of the Service Bus aka SAP PI) named as "SOA cockpit",
a web ui for quick configuration of connections between Service Providers and Consumers on Metadata published in
the Service Registry.
Sounds pretty good and useful, as it seems to give better overview of possible and realized connections then to pick it up
manually from the Integration Directory or whereever
Does anyone know when this tool will be released and available? (hello SAP people )
With best regards
Sebastian

Hi Sebastian,
I have exactly same question. Any named tool from sap or other vendor for service metering? Please let me know if you have succeeded in your quest
Many thanks.
Br
Suman

Technical Article on Service-oriented Integration Using JBI Posted

I've just posted an article on the open-esb site about using JBI for what we have come to call service-oriented integration: enterprise integration atop a SOA fabric. The article includes an example of a simple adapter pattern implementation that includes message transformation and protocol hopping.
See https://open-esb.dev.java.net/ for the PDF download.

At last!!
Finally an article about the real JBI and what JBI is all about. I don't know what's going on with people's understanding of JBI.
At JavaOne, I remember one of the expert group, from Oracle I think, proudly claiming that JBI will be one of the core architectures that companies will be delivering their integration business upon. Now I wonder where Oracle's, SAP's and IONA's contributions are so far. Oracle for example really contributed to JSR 208 by marketing and implementing SCA.
Although in early stages, I think open source implementations are missing the point as well. Using open source implementation X, I couldn't see a scenario that shows the power of the concept, while implementation Y just did not like service units, service connections and link types, then tried to invent its own configuration and routing descriptors, wasting very valuable time.
Anyway, may be one just have to wait and see!!
Thanks Ron for such contribution.

Java EE Service Engine: Bridging Java EE and JBI

An excellent blog from our resident expert on how to connect JBI components with services launched on Java EE side. Take a look and give us feedback.
http://weblogs.java.net/blog/binod/archive/2006/07/java_ee_service_1.html

Simply point it to your java program. J2SE = JDK.
--olaf

Full Service - Switch from Metered to Permit Indicia

Background:
We are participating in Full Service IMB for 1st Class mail with a typical mailing of 110,000 to 120,000 mail-pieces each day. On any given day, there may be 15 - 50 pieces that weigh over 1 ounce. This is due to enclosures and the number of pages in the envelope. We are metering our mail at the correct postage rate. These overweight pieces are removed from the current mailing and the proper postage is applied.
Task:
I am analyzing the potential of switching away from using meters to a preprinted permit indicia.
Question:
Is there a way for presort to identify the overweight pieces within the Mail.Dat files? If so How?
With the randomness of these overweights, what is the recommended method for handling these pieces?
Any known best practices?

I can't really think of an easy way to identify these pieces within the Mail.dat files.
What method are you using to set up the verisons within Presort? Version Description blocks or AUTO-DIMEN within the Version Defaults block?

Doubts about configurate services with JBI

Hi people,
I have been looking for a way to develop a wizard for configuration of services in different ESBs from my web application.
I took a look at some presentations (like http://80.69.93.183/sun-evenementen/pdf/jbi_openesb.pdf and http://mediacast.sun.com/users/~armin/media/SunTechDays2007_OpenESB.pdf), and I would like ask you about possibilities to configure services in a ESB using JBI.
What I really want to do is allow that my web application connects to some ESBs to configure services into them. It's like to have the web interface that some of them provide to make the configuration from my web application.
I have been talking about this with some guys and two possibilities that they gave me are:
1. To develop everything into the web application and send the information through JMX.
2. To develop a generator of XML content (in memory) and send it the ESB, where it would has another implementation made by me, like a module (one of the guys said me that this could be a JBI Service Engine), which would receive the XML content generated by the web application.
Using the first one possibility, I would have all solution into my application and developing the other one, I would have one implementation to each ESB that I want to connect to if it wouldn't be done with JBI (I think.. right? Because it seams that it would be the same if I do it with JBI).
One guy told me that the second one would be the best, because, until he knows (based on the PoCs (proof of concept) he made, with JBossESB, Mule and WebSphere ESB), some of the ESBs he tested require some manual configuration to publish the services to be accessed through the ESB. He didn't do anything with JBI and didn't know anything about this.
Another thing is that if I deploy only once a JBI Service Engine (SE), I can do the configuration of every service I want to publish in the ESB through this SE. In other words, I won't need to ask to the admin of ESB do the configuration to me (or do it through the web interface of ESB).
Please, does anybody know if all the ESBs that support JBI give an interface to another application connects to them to configures services?
I thank you in advance for any information!
Regards,
Luiz

Hi people,
I have been looking for a way to develop a wizard for configuration of services in different ESBs from my web application.
I took a look at some presentations (like http://80.69.93.183/sun-evenementen/pdf/jbi_openesb.pdf and http://mediacast.sun.com/users/~armin/media/SunTechDays2007_OpenESB.pdf), and I would like ask you about possibilities to configure services in a ESB using JBI.
What I really want to do is allow that my web application connects to some ESBs to configure services into them. It's like to have the web interface that some of them provide to make the configuration from my web application.
I have been talking about this with some guys and two possibilities that they gave me are:
1. To develop everything into the web application and send the information through JMX.
2. To develop a generator of XML content (in memory) and send it the ESB, where it would has another implementation made by me, like a module (one of the guys said me that this could be a JBI Service Engine), which would receive the XML content generated by the web application.
Using the first one possibility, I would have all solution into my application and developing the other one, I would have one implementation to each ESB that I want to connect to if it wouldn't be done with JBI (I think.. right? Because it seams that it would be the same if I do it with JBI).
One guy told me that the second one would be the best, because, until he knows (based on the PoCs (proof of concept) he made, with JBossESB, Mule and WebSphere ESB), some of the ESBs he tested require some manual configuration to publish the services to be accessed through the ESB. He didn't do anything with JBI and didn't know anything about this.
Another thing is that if I deploy only once a JBI Service Engine (SE), I can do the configuration of every service I want to publish in the ESB through this SE. In other words, I won't need to ask to the admin of ESB do the configuration to me (or do it through the web interface of ESB).
Please, does anybody know if all the ESBs that support JBI give an interface to another application connects to them to configures services?
I thank you in advance for any information!
Regards,
Luiz

JBI: problem with deploy-service-assembly

I've developed a service component following the instructions in :
http://java.sun.com/integration/reference/techart/DevelopingAServiceEngineComponent-1-2.pdf
The Componet has been installed and started succesfully:
With jbiadmin command "list-service-engines" the result is:
================================
List of Service Engines
================================
Name : MyServiceEngine
State: Started
Name : SunSequencingEngine
State: Started
Name : SunTransformationEngine
State: Started
When I try to deploy the Service Assembly deploy-service-assembly C:\mine\MyServiceAssembly.zip I got the following error:
deploy-service-assembly C:\mine\MyServiceAssembly.zipThe deploy-service-assembly Command Failed Component : MyServiceEngine
MESSAGE:()RuntimeException thrown by the invoke method of the Dynamic MBean
Root Cause:
MESSAGE:(UNKNOWN)<?xml version="1.0" encoding="UTF-8" standalone="yes"?><component-task-result><component-name>MyServiceEngine</componen
t-name><component-task-result-details><task-result-details><task-id>deploy</task-id><task-result>FAILED</task-result><message-type>ERROR</message-type
<task-status-msg><msg-loc-info><loc-token> </loc-token><loc-message>JBIFW0063: Internal error: Null argument received for serviceUnitRootPath.</loc-message></msg-loc-info></task-status-msg></task-result-details></component-task-result-details></component-task-result>
>
In the Application server log (server.log) there's the following message:
[#|2005-10-07T02:33:58.268+0200|SEVERE|sun-appserver-pe8.1_02|com.sun.jbi.framework|_ThreadID=40;|JBIFW0063: Internal error: Null argument received for serviceUnitRootPath.|#]
Any ideas'information on how to get past this situation?
Thx
Adrian

Adrian,
I'll pass this along to the RI team, to see if they have any ideas.
In the meantime, I'll take a guess: have you implemented the ServiceUnitManager interface, and have you implemented the Component.getServiceUnitManager() method such that it returns an instance (preferably a singleton) of your SUM class?
Also, if you look in the appserver's server.log file, are there any errors or warnings logged concerning the installation or startup of your custom component that occured before the JBIFW0063 error you reported?

JMX object names for JBI services

In a previous post it was stated that the JMX objectnames for the JBI installation service, deployment service, and admin service were implementation specific. Is it possible to lookup the installation service and deployment service from the admin service in a similar fashion to looking up the object name of a component by it's name?

The names are implementation dependent. The model is that administrative code is implementation-specific. You can use the AdminServiceMBean.getSystemService method to find things like the installation and deployment services:
The Open ESB names for the System services are:
DeploymentService
LoggingService
InstallationService
ConfigurationService
MessageService
AdministrationService
(These are best discovered using JConsole!)
Obviously there are more system services than Deployment and Installation; the Open ESB implementation supplies other MBeans to control other implementation modules that are not specified by JBI, but are needed to realize a controllable system.
-Ron

JBI and Local Service Bus

Can anyone share some thoughts on how IBM's use of Local Service Bus compare with what JBI is providing..

The concept of Local Service Bus from IBM, at first glance, appears to be somewhat similar to
JBI. However, the lack of details on Local Service Bus and the proprietary nature of its architecture
makes it hard to do a comparison.
Java Business Integration 1.0 is close to finalization and has been a community effort with the likes
of Apache, Iona, Jboss, Oracle, SAP, SeeBeyond, Sonic, Sun, Tibco and others (http://jcp.org/en/jsr/detail?id=208). It would be good to have IBM participate in the standardization effort too.
To see how JBI works, go to http://java.sun.com/integration and download the early access version.
There is a technical article at
http://java.sun.com/integration/reference/techart/jbi/ that describes how to develop a service engine component for JBI. More to follow.

Monitoring JBI services in JavaCAPS6

In 513 there was a java API for monitoring through emanager.
Is there something similar in JavaCAPS6 for monitoring JBI services and components?
Rupert

JavaCAPS6 comes with a bunch of monitoring APIs, more on this you can read here:
[http://developers.sun.com/docs/javacaps/reference/uclcm.uclcm_intro.html]
The graphical view of a business proces instance as it was available with emanager is not there for BPEL 2.0, it applies for Classic JavaCAPS only.
BRs
Kris

Service Metering by JBI

Similar Messages

Maybe you are looking for