Publishing to Facebook from LabVIEW

I have been tasked with adding social site functionality to a LabVIEW application. The goal is to let the user enter their Facebook and/or Twitter ID & password and then be able to sent updates periodically. The hangup with posting to Twitter has been discussed in this post.
On the Facebook front, my searching has turned up empty so far. Has anyone done any work to try to blaze a path from LabVIEW to Facebook or am I the first one trying to get there from here?
Thanks,
Travis

Facebook does have a REST API, but it looks like it's being deprecated (you have to have a Facebook account to view it, which I do not).
REST API's are by far going to be the easiest to work with in LabVIEW. Twitter's is actually fairly well documented, though I do agree that OAuth is a little difficult to navigate. It's certainly built more for web applications than desktop applications (as LabVIEW generally is).
Chris
Certified LabVIEW Architect
Certified TestStand Architect

Similar Messages

How to Publish to Revel from Lightroom using a Facebook Account

I signed in to my Revel Account using my Facebook Account. I'm trying to publish from Lightroom but it's not accepting my Facebook ID and Password. How do I publish from Lightrrom using a Facebook account or how do I switch my Revel Facebook login to my Adobe login? Any help is appreciated.
Thanks

Hello
To set up publishing to Revel 1.10 is easy in Lightroom 4. I would suggest that you update to Lightroom 4.4 first. You can goto the help menu in Lightroom and then select " Check for updates" then update to version 4.4. Also make sure you have updated to Revel 1.10
Here is the instructions to do this for Revel as its similar to set it up for Facebook too. It is pretty simple to set up. http://help.adobe.com/en_US/lightroom/using/WS2bacbdf8d487e582-46da1b6f13419e06a64-8000.ht ml
Here you will see the Lightroom Publishing Manager. Click on the Revel tab and then select Authorize Revel button. You will then be prompted to sign into your Revel account. If your Facebook account log in information is not working then I would suggest to log in with your Adobe ID. You are best to do that anyway.
In the image below you can see that I created separate albums for pictures. Then you can drag your photos to these folders and click publish. Then check your Adoberevel.com to see if the images show. Once you see that they uploaded in the upperleft of Lightroom, then you should see the images show in Revel.
You can publish to Facebook from Lightroom the same way. Just click on the facebook tab on the publishing manager and authorize the Facebook connection with your Facebook log information. You will then be prompted to log into your Facebook account thru a browser.
http://help.adobe.com/en_US/lightroom/using/WS2bacbdf8d487e582-46da1b6f13419e06a64-8000.ht ml
Let me know if this helped you out or if you have any questions
Thanks
Scott

How can i update an html web page from Labview?

I intend to publish the "status" of an experiment online through an web page. I mean, if my vi is running i would like to have a phrase or indicator set on at my web page. If my Vi is not running i would like this indicator set off. This page is hosted in a server and I would like to know if its possible to update the html file from labview through an ftp connection.
Thanks in advance...
MSc. Alexandre Michel Maul
Parana Federal Univeristy - Brasil

The system exec function is on the Communication palette. Its for executing system commands. On my Win2K system, the help for FTP is:
"Ftp
Transfers files to and from a computer running an FTP server service (sometimes called a daemon). Ftp can be used interactively. Click ftp commands in the Related Topics list for a description of available ftp subcommands. This command is available only if the TCP/IP protocol has been installed. Ftp is a service, that, once started, creates a sub-environment in which you can use ftp commands, and from which you can return to the Windows 2000 command prompt by typing the quit subcommand. When the ftp sub-environment is running, it is indicated by the ftp command prompt.
ftp [-v] [-n] [-i] [-d] [-g]
[-s:filename] [-a] [-w:windowsize] [computer]
Parameters
-v
Suppresses display of remote server responses.
-n
Suppresses autologin upon initial connection.
-i
Turns off interactive prompting during multiple file transfers.
-d
Enables debugging, displaying all ftp commands passed between the client and server.
-g
Disables file name globbing, which permits the use of wildcard characters (* and ?) in local file and path names. (See the glob command in the online Command Reference.)
-s:filename
Specifies a text file containing ftp commands; the commands automatically run after ftp starts. No spaces are allowed in this parameter. Use this switch instead of redirection (>).
-a
Use any local interface when binding data connection.
-w:windowsize
Overrides the default transfer buffer size of 4096.
computer
Specifies the computer name or IP address of the remote computer to connect to. The computer, if specified, must be the last paramete
r on the line."
I use tftp all of the time to transfer files in a similar manner. Test the transfer from the Windows command line and copy it into a VI. Pass the command line to system exec and wait until it's done.

Write to Citadel database from LabVIEW?

Hi. I'm a newbie when it comes to Lookout and the Citadel database... so here's my question for you all:
We have various labview applications that log data from instruments. We would like to be able to take this data and store it as "tags" in a Citadel database.
What do you think is the best way to do this?
There are ODBC drivers for the Citadel database, but they appear to only allow you to query the database to retrieve values... you can't write data to the database (so its read-only).
Are they any "Lookout VIs" or Citadel VIs that can write to the Citadel DB from LabVIEW? Or a DLL or something?
Any ideas?
regards,
John Paul

Very nice question John Paul. I take it you already have Lookout and LabVIEW. In this case, with the latest versions of either, simply use the LabVIEW datasocket to publish the items on your front panel. Lookout then can subscribe to these once you register the LabVIEW computer. Once you have subscribed to them in Lookout, you are then able to set up logging. You may need to create an expression object to route the data to citadel.
If you just want to use LabVIEW and the Citadel database, you might try VI Logger. This works in our configuration utility - MAX, and also comes with a set of VIs for LabVIEW. One caveot, the Citadel database in VI logger is newer (and faster) than the Citadel database in Lookout. I believe NI is working to synchronize
the version in the future, and its hard to say when. So till then, you would not be able to merge data in the dislike citadel databases. However, you can always use and ODBC call set to extract from both and store in a more permanent SQL database such as access, oracle, ms back office, etc.
Good Luck,
Preston Johnson
Business Development Manager
Industrial Applications
National Instruments
Preston Johnson
Principal Sales Engineer
Condition Monitoring Systems
Vibration Analyst III - www.vibinst.org, www.mobiusinstitute.com
National Instruments
[email protected]
www.ni.com/mcm
www.ni.com/soundandvibration
www.ni.com/biganalogdata
512-683-5444

How to Pass Container in a queue from LabVIEW to TestStand?

I was succussful to pass simple type(string, number) using queue from LabVIEW to TestStand base on the example: Use TestStand Queue.seq.
I want to pass a container variable from LabVIEW to TestStand. But there are some errors happen.
Anyone who can help on this issue?
Thanks in advance.
Attachments:
Sequnce and VI.zip ‏28 KB
VI Error.jpg ‏61 KB
Run_time Error -17001.jpg ‏41 KB

You ought to have a listener somewhere that calls a function
to then set up the loaded swf. In that function you can do this
kind of thing:
var ldrmc:MovieClip;
function swfloaded (e:Event) {
ldrmc = null;
if (e.target.content is MovieClip) {
ldrmc = e.target.content as MovieClip;
If the swf was published for AS3, then ldrmc will end up
being a pointer to the root of the swf, and you can call functions
or set variables however you like. If it was an AS2 swf, ldrmc
would be null.
Inside the loaded swf you could try trace statements, to make
sure you're looking up the hierarchy far enough. Like this:
trace(MovieClip(parent.parent));
If that doesn't trace MainTimeLine, then maybe you're not
looking up far enough. Don't forget that the swf itself is in a
loader, and so may be one level down from where you thought it was.

Help! The "publish" option is grayed out when trying to publish to Facebook blish to Fa

The problem is stated above - the grayed out option when trying to publish to Facebook...

Try the fix posted from Franchi Panchi in this topic: My publish button on iphoto is grey and...: Apple Support Communities.
OT

How do I post a slide show (from iPhoto 11) with music to Facebook from my mac

How do I post a slide show to facebook, from my imac. I am using it was made on iphoto 11 but I cannot figure out how to post or publish to post link. I also have slide show saved in itunes Thank you for your help

Export the slideshow from iPhoto
Then upload it to Facebook via their own uploader.

Can't post photos on Facebook from iPad since upgrading to ios8

Since upgrading to ios8 I can no longer post photos on Facebook from existing photos on my iPad 2. Is this a problem connected to the upgrade or something else? Also, since the upgrade my keyboard sometimes freezes up and I have to refresh the page and start over and lose whatever I had been working on. Also an ios8 issue?

Roddy
I hate to sound obnoxious, and I really do appreciate your efforts to help me. The link actually is not what Facebook normally does. Yes, the thumbnail goes to your FB profile. But if you had pasted almost any other link in the link publisher, you'd get a second thumbnail and a L/R arrow that allows you to scroll through the graphics posted on the linked site and pick one to serve as a thumbnail from your website. Then, had you linked to a page with a long and cumbersome address, you'd have seen the link "cleaned up" aesthetically so that you would not see 4 lines of URL, but a tidy site title and abbreviated link. That's what I'm missing, and scrolling down that iWeb interest page on Facebook shows a lot of others with the same issue.
But as I said, earlier, I really have about stopped caring and am planning to take Ethmoid's advice and can iWeb altogether and look to some other arrangement for managing my site, though I find it ironic that I was urged to dump iWeb by people on the Apple discussion board!

Cannot publish to Facebook and Keychain Error

I want to publish photos from iPhoto 09 to Facebook but I've got some sort of endless loop error. See the screens at the link or read my description.
http://www.flickr.com/photos/stanomatic/4113756464/in/set-72157622701757225/
I press the Facebook icon in the lower right and I get the drop down dialog which asks "Do you want to set up iPhoto to publish to Facebook?" I click the Setup button. Then I get the iPhoto Uploader button and I put in my Email and Password. Then I get this "iPhoto wants to use the "loginrenamed2" keychain." Please enter password. So I enter the same password. I didn't make this keychain. I never use keychain and don't understand how it works or anything else about it. Then it takes me back to the original screen, "Do you want to set up iPhoto to publish to Facebook?" So the loop starts all over again.
Any ideas on how to fix this?

Keychain is what stores your passwords. Try use Keychain Access to repair them. It's in your Applications / Utilities folder.
Regards
TD

Photoshop Elements 12: Unable to publish to Facebook

I just installed PE12 and tried publishing to Facebook. This worked flawlessly in PE9. PE asks me to authorize Facebook and I log in and receive a message saying that I am logged in. I then return to PE and "complete authorization". I was able to create an Album in Facebook from PE12, but the 9 pictures that appeared to successfully upload do not appear in Facebook.
Any suggestions?
Using Windows 7 Ultimate and recently upgraded from PE9 to PE12.

Did they copy over your programs and settings to the new disk? You can't do that with PSE (unless you do a total system clone).
If that's the situation, you need to download and run this:
Use the CC Cleaner Tool to solve installation problems | CC, CS3-CS6
And then go around and manually remove all the bits you can find from applications, hard drive>library>application support>adobe, and your username>library preferences and then reinstall from scratch. Note that spotlight won't help you with this, you have to do it yourself since spotlight is programmed to skip the files you want to find.

Iphotos won't publish on facebook?

I have previously been able to post/publish photos from iphoto straight to facebook. Now when I go to Share - Facebbook it comes up with Do you want to set up iphoto to publish to Facebook? Cancel or Set Up. When I choose set up it open a small Facebook window, a blue bar moves (looks like it is loading the photos) and then finishes but only give me an option to Close. When I do, nothing happens, I assume the set up has happened and try to re: share them but asks me the same thing. Pls help?? There are no updates needed on my computer so unsure why this has stopped working for me?
Tks

Once I downloaded Yosemite the iphoto does not work anymore. So I went ahead and trash the app and attempted to reinstall.
Did you check, if iPhoto is really gone from the Applications folder? You should not be seeing an "Update", if you do not have iPhoto installed any longer. Make sure, it has been deleted from "Applications".
Then go to the main page of the App Store ("Featured") and search for iPhoto. If iPhoto is now showing as "Free", buy it for free to install it again.

Won`t publish to Facebook Timeline

Hi, I am trying to publish an album to Facebook from Lightroom 5, however its not happening for me. Initially I was able to ghet the images on FB, but they did not appear on my timeline, nor did they appear as an album, just in my photos and no-one was able to view them. I deleted the images on FB, and also deleted the collection in LIghtroom. Now if I try to re-publish, i just get an empty album on Facebook.
I suspect there is something wrong with the lightroom publishing manager, which is now set as `IOS photos` and will not allow me to change it as its greyed out.
If anyone has any suggestions, i would be grateful, thank you

I found the solution!
On facebook, go to your privacy settings. On the lower left, click on the edit option for "Apps and Websites". The first option is "Apps you use", click on edit settings. And then I'll bet you have the iPhoto Exporter on that list. Click the little "x" to remove it, click ok, and then you're done! Now you can go back to Aperture and successfully add a facebook account.
Hope this helps.
(also, in my limited testing the http vs https thing doesn't make a difference).

LR3 unable to publish to facebook - help

Think I put this in the wrong discussion thread first time round, Hope it works now.
I can't publish to facebook. Tried various collections and it won't work. Everything was fine last week.
Error message #1 "Failed to retrieve item info" apprears when I try to upload to facebook.
Error message #2 (could be a summary), "Warning, can't update this collection. Failed to retrieve item info.", appears as soon as I close the tab for Error #1,
Anyone has a solution?
Thanks,
Joe

Hi Julie,
I've been using LTR since Beta 1. I love this program and spend about 10 hours a day living in it.
I've been using in LTR 2 for years now and just downloaded LTR 3.3 4 days ago.
I wanted to test drive the Publishing tool for FaceBook. LTR will not let me select an ALBUM for FaceBook and I keep getting this error message
"Could not get album info from Facebook." and then this one also after I click to close that error "Can’t update this collection."
If you have a fix I'd like to know to give it a test drive. I don't know what to do to so if you can please help me out I'd be smiling again.
I'd like to volunteer or test drive the new fix
LTR 3.3
Mac 10.6.6
Firefox Browser 3.6.15
Thanks
Bryan

LR 3.2 Publish to Facebook - "PAGES"

Like most photographer's I've got a facebook page and then a "photography studio page". The way facebook makes you basicly have a "sub account" for promoting your photo business.
I can configure LR 3.2 to publish to albums in my normal account, but I'd like to publish directly to my "professional page" which is linked to the account. It does not have a seperate login... but when I load it up it does show that Lightroom is authorized to publish to it. However, the albums for the "page" are not available in the lightroom publish to facebook area.
Any ideas?

My apologies if you have already found this answer, but I didn't see it in the replies for this thread.
Here is an answer to your "pages" issues with the default Facebook plugin. Check out Jeff Friedl's plugin...
http://www.adobe.com/cfusion/exchange/index.cfm?event=extensionDetail&loc=en_us&extid=1686 557
Here is his personal blog, from which he supplies a wealth of information and a variety of plugins for Lightroom (see "Lightroom Goodies")...
http://regex.info/blog/
I''m setting up my plugins from Jeff as "I speak."
I hope this helps,
Adam

Error while publishing enterprise service from ES builder.

Hi Friends
I am not able to publish my service from ES builder. I am getting this error after publishing.
Please let me know if anyone has faced similar problem and has solution for it.
Thanks
-Mitesh
This is the error log generated.
javax.ejb.EJBException: Exception raised from invocation of public com.sap.aii.ibrep.core.esregistry.ServicesRegistryPublication com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishServiceInterface(com.sap.aii.ib.bom.gen.XiReference) throws com.sap.aii.utilxi.misc.api.ResourceException,java.rmi.RemoteException,com.sap.aii.ib.core.uddi.RegistryClientException method on bean instance com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean@c8c9bc for bean sap.com/com.sap.xi.repositoryxml|com.sap.xpi.ibrep.server.jarxml|ServicesRegistryBean; nested exception is: javax.ejb.EJBTransactionRolledbackException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected] for bean sap.com/tcesiuddisrproxyear*annotation|tcesiuddisrproxyejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details.; nested exception is: javax.ejb.EJBException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected] for bean sap.com/tcesiuddisrproxy~earannotation|tcesiuddisrproxyejbm.jar*annotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. javax.ejb.EJBTransactionRolledbackException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected] for bean sap.com/tcesiuddisrproxyearannotation|tcesiuddisrproxy~ejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details.; nested exception is: javax.ejb.EJBException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected] for bean sap.com/tcesiuddisrproxyear*annotation|tcesiuddisrproxyejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. javax.ejb.EJBException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected] for bean sap.com/tcesiuddisrproxy~earannotation|tcesiuddisrproxyejbm.jar*annotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:159) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEISyncMethod(WSInvocationHandler.java:118) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEIMethod(WSInvocationHandler.java:84) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invoke(WSInvocationHandler.java:65) at $Proxy1507_10002.publishPhysicalSystems(Unknown Source) at com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(ServicesRegistryProxyFacade.java:339) at sun.reflect.GeneratedMethodAccessor1785_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy61_10002.publishPhysicalSystems(Unknown Source) at com.sap.aii.ib.server.uddi.RegistryClientDelegateProvider$EjbRegistryClient.publishPhysicalSystems(RegistryClientDelegateProvider.java:389) at com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishPhysicalSystem(ServicesRegistryBean.java:303) at com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishServiceInterface(ServicesRegistryBean.java:172) at sun.reflect.GeneratedMethodAccessor1787_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy2658_10002.publishServiceInterface(Unknown Source) at sun.reflect.GeneratedMethodAccessor1786_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:234) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351) at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62) at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37) at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:872) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53) at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108) at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304) Caused by: com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1035) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:699) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:672) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:153) ... 65 more Caused by: java.lang.NullPointerException at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.ContentTypeImpl.init(ContentTypeImpl.java:40) at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.ContentTypeImpl.<init>(ContentTypeImpl.java:36) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.handleSOAPResponseMessage(SOAPTransportBinding.java:459) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:953) ... 68 more javax.ejb.EJBException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected] for bean sap.com/tcesiuddisrproxyearannotation|tcesiuddisrproxy~ejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:72) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy61_10002.publishPhysicalSystems(Unknown Source) at com.sap.aii.ib.server.uddi.RegistryClientDelegateProvider$EjbRegistryClient.publishPhysicalSystems(RegistryClientDelegateProvider.java:389) at com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishPhysicalSystem(ServicesRegistryBean.java:303) at com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishServiceInterface(ServicesRegistryBean.java:172) at sun.reflect.GeneratedMethodAccessor1787_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy2658_10002.publishServiceInterface(Unknown Source) at sun.reflect.GeneratedMethodAccessor1786_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:234) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351) at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62) at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37) at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:872) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53) at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108) at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304) Caused by: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:159) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEISyncMethod(WSInvocationHandler.java:118) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEIMethod(WSInvocationHandler.java:84) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invoke(WSInvocationHandler.java:65) at $Proxy1507_10002.publishPhysicalSystems(Unknown Source) at com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(ServicesRegistryProxyFacade.java:339) at sun.reflect.GeneratedMethodAccessor1785_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) ... 56 more Caused by: com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1035) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:699) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:672) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:153) ... 65 more Caused by: java.lang.NullPointerException at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.ContentTypeImpl.init(ContentTypeImpl.java:40) at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.ContentTypeImpl.<init>(ContentTypeImpl.java:36) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.handleSOAPResponseMessage(SOAPTransportBinding.java:459) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:953) ... 68 more javax.ejb.EJBTransactionRolledbackException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected] for bean sap.com/tcesiuddisrproxyear*annotation|tcesiuddisrproxyejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details.; nested exception is: javax.ejb.EJBException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected] for bean sap.com/tcesiuddisrproxy~earannotation|tcesiuddisrproxyejbm.jar*annotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.ejb3.runtime.impl.TransactionAttributeHandler$Required.error(TransactionAttributeHandler.java:307) at com.sap.engine.services.ejb3.runtime.impl.TransactionAttributeHandler$TransactionAttributeErrorsHandler.error(TransactionAttributeHandler.java:130) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:40) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy61_10002.publishPhysicalSystems(Unknown Source) at com.sap.aii.ib.server.uddi.RegistryClientDelegateProvider$EjbRegistryClient.publishPhysicalSystems(RegistryClientDelegateProvider.java:389) at com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishPhysicalSystem(ServicesRegistryBean.java:303) at com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishServiceInterface(ServicesRegistryBean.java:172) at sun.reflect.GeneratedMethodAccessor1787_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy2658_10002.publishServiceInterface(Unknown Source) at sun.reflect.GeneratedMethodAccessor1786_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:234) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351) at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62) at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37) at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:872) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53) at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108) at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304) Caused by: javax.ejb.EJBException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected] for bean sap.com/tcesiuddisrproxyearannotation|tcesiuddisrproxy~ejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:72) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) ... 50 more Caused by: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:159) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEISyncMethod(WSInvocationHandler.java:118) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEIMethod(WSInvocationHandler.java:84) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invoke(WSInvocationHandler.java:65) at $Proxy1507_10002.publishPhysicalSystems(Unknown Source) at com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(ServicesRegistryProxyFacade.java:339) at sun.reflect.GeneratedMethodAccessor1785_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) ... 56 more Caused by: com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1035) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:699) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:672) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:153) ... 65 more Caused by: java.lang.NullPointerException at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.ContentTypeImpl.init(ContentTypeImpl.java:40) at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.ContentTypeImpl.<init>(ContentTypeImpl.java:36) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.handleSOAPResponseMessage(SOAPTransportBinding.java:459) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:953) ... 68 more javax.ejb.EJBException: Exception raised from invocation of public com.sap.aii.ibrep.core.esregistry.ServicesRegistryPublication com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishServiceInterface(com.sap.aii.ib.bom.gen.XiReference) throws com.sap.aii.utilxi.misc.api.ResourceException,java.rmi.RemoteException,com.sap.aii.ib.core.uddi.RegistryClientException method on bean instance com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean@c8c9bc for bean sap.com/com.sap.xi.repositoryxml|com.sap.xpi.ibrep.server.jarxml|ServicesRegistryBean; nested exception is: javax.ejb.EJBTransactionRolledbackException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected] for bean sap.com/tcesiuddisrproxyear*annotation|tcesiuddisrproxyejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details.; nested exception is: javax.ejb.EJBException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected] for bean sap.com/tcesiuddisrproxy~earannotation|tcesiuddisrproxyejbm.jar*annotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:72) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy2658_10002.publishServiceInterface(Unknown Source) at sun.reflect.GeneratedMethodAccessor1786_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:234) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351) at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62) at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37) at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:872) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53) at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108) at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304) Caused by: javax.ejb.EJBTransactionRolledbackException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected] for bean sap.com/tcesiuddisrproxyearannotation|tcesiuddisrproxy~ejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details.; nested exception is: javax.ejb.EJBException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected] for bean sap.com/tcesiuddisrproxyear*annotation|tcesiuddisrproxyejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.ejb3.runtime.impl.TransactionAttributeHandler$Required.error(TransactionAttributeHandler.java:307) at com.sap.engine.services.ejb3.runtime.impl.TransactionAttributeHandler$TransactionAttributeErrorsHandler.error(TransactionAttributeHandler.java:130) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:40) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy61_10002.publishPhysicalSystems(Unknown Source) at com.sap.aii.ib.server.uddi.RegistryClientDelegateProvider$EjbRegistryClient.publishPhysicalSystems(RegistryClientDelegateProvider.java:389) at com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishPhysicalSystem(ServicesRegistryBean.java:303) at com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishServiceInterface(ServicesRegistryBean.java:172) at sun.reflect.GeneratedMethodAccessor1787_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) ... 31 more Caused by: javax.ejb.EJBException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected] for bean sap.com/tcesiuddisrproxy~earannotation|tcesiuddisrproxy~ejbm.jar*annotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:72) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) ... 50 more Caused by: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:159) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEISyncMethod(WSInvocationHandler.java:118) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEIMethod(WSInvocationHandler.java:84) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invoke(WSInvocationHandler.java:65) at $Proxy1507_10002.publishPhysicalSystems(Unknown Source) at com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(ServicesRegistryProxyFacade.java:339) at sun.reflect.GeneratedMethodAccessor1785_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) ... 56 more Caused by: com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1035) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:699) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:672) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:153) ... 65 more Caused by: java.lang.NullPointerException at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.ContentTypeImpl.init(ContentTypeImpl.java:40) at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.ContentTypeImpl.<init>(ContentTypeImpl.java:36) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.handleSOAPResponseMessage(SOAPTransportBinding.java:459) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:953) ... 68 more

Hi ,
try to change the ServiceRegistry Logical Port
In NetWeaver Administrator under SOA Management _Business Administration _Web Services Administration
Client Proxy Name: ServicesRegistrySi
Authentication: User name/password
Role: SERVICES_REGISTRY_READ_WRITE
Should help u out

Publishing to Facebook from LabVIEW

Similar Messages

Maybe you are looking for