I'm trying to set up AIF web services on an instance of an AOS.
Once I'm done with the AIF Web Service component installation, I'm not seeing any .asmx/.svc or otherwise that would provide a WSDL to consume AIF web services.
Is there something I'm missing ?
C:\Program Files\Microsoft Dynamics AX\50\AifWebServices\Bin only holds Microsoft.Dynamics.IntegrationFramework.WebService.Process.dll and language named folders holding Microsoft.Dynamics.IntegrationFramework.WebService.Process.resources.dll
Also, in Basic->Setup->Application Integration Framework, I only have Endpoints. I saw some guides mentioning I should have Service and Websites in there.
I'm patched up to RU8.
Thanks.
Turns out you actually have to create the document service AND, well, the missing menu element is due to a missing AX license we need to purchase so the menu elements appear...
Related
I'm new to SFDC. I need to perform integration between SFDC and EBS. I have a SOAP webservice from EBS to create party,account, account site and site details.
Now i need to call this webservice in SFDC(using APEX). Can you please let me know how i can achieve this (Expecting Step by step explanation) or any document which will tell me how this can be achieved.
Salesforce provides an integrated tool called Wsdl2Apex. It can be used to create Apex classes from the WSDL to call the web service from Apex. See SOAP Services: Defining a Class from a WSDL Document, which includes step by step instructions on how to generate the Apex classes from a WSDL.
Remember that you will also need to setup a Remote Site to allow the callout to the web service URL.
There are a couple of alternatives depending on how complicated your WSDL is.
Firstly, there is also an open source version of Wsdl2Apex.
Secondly, I've created an independent tool that has increased support for various WSDL features. See Dreamforce 2014 Presentation - Improved Apex support for SOAP based web services.
I have a composite with a SOAP web service entry point running on SOA Suite. We will have a new client for that web service, but this client cannot speak SOAP, so we will have to publish that entry point on a REST endpoint. I know I can enable REST Support to the existing web service through EM console, but I would like to have this configuration enabled by default after deploy.
My research for ways to do that using a property or attribute on a configuration plan did not get useful informations.
Does anyone know how could I achieve that?
Thanks!
REST Support is formal part of SOA Suite 12c. Download and install that and then you can easily add a REST interface to a SOAP composite. Also, 12c now installs without RCU/DB, etc - just start the Integrated WLS domain in JDev and it builds itself and you are up and deploying in under 20 mins. And this may help.
I am new to Dynamic Navision .On just going through the Dynamic Navision Solution I could find certain in-built Web Services.
Can those Web Services be customizable .
If so how can I make it possible.
Can I create a new Service with new Object Id .
I have searched for resources,but couldn't find any .It would be really helpful if someone suggest me with a good resource.
I think, more specifically you're looking for:
http://msdn.microsoft.com/en-us/library/dd339004.aspx
Creating a codeunit from within Microsoft Dynamics NAV.
Exposing the Web service.
Verifying the Web services availability.
Consuming the Web service from a console application that is created
in Visual Studio
Just make sure you have
Microsoft Dynamics NAV 2009 with a developer license.
You might like to give: http://msdn.microsoft.com/en-us/library/dd355036.aspx a read.
I am new to developing web services using java. I have an academic project where I need to do dynamic service composition. For that I can't directly create a service-client for a particular service because if I do so then that client will call that particular service only. Client need to search various web services and then out of those services select any one at run time and also call that service at run time.
I was able to develop the web service(JAX-WS) using Eclipse(indigo), I also created the client for that web service and every thing is working fine. Now my problem is that while creating the client I am hard coding the client to call that particular web service only(since I am creating the client using the WSDL file of the service). However I actually need to call any one of the searched service, but for that I need to publish the service some where then discover it and then call it.
I tried publishing the service to juddiv3. But on juddiv3 I could only publish the sample service supplied with the juddiv3. When I try to publish service created by me then it is not getting displayed in the group of published services.
Is there any other UDDI server which I could install on my local machine and then publish and discover the service from that. Also I was not able to figure out how to create a client that will modify itself at run time to call any one service out of various searched services.
Kindly provide the necessary steps and code.
Thanks
You can use jUDDI (http://juddi.apache.org/ ).
juddi is based on UDDI v2.0, v 3.0 .
Here, you can publish as well as discover your web service.
For integration, you have to make some application which integrates with jUDDI.
But I think for your academic project, and for your purpose, jUDDI is best suitable! ( :) )
jUDDI has a boat load of examples in the source code trunk. You may want to check them out. It's difficult to guess what the problem is from the little information you've provided. Consider contacting the jUDDI team for further assistance. http://svn.apache.org/repos/asf/juddi/trunk/juddi-examples/. There's also additional document for working with UDDI in the jUDDI user's guide, which is at the jUDDI web site
You cannot directly publish on jUDDI. You need to create publisher entities in jUDDI server also. You'll find Rename4Sales and Rename4Marketing examples in 'Classes' folder in the standalone server's juddi application. Use these XMLs as your basis and create your own entity. You also need to configure the server's login credentials.
I suggest you follow the tutorials on jUDDI blog.
I'm learning about web services and most of the resources I've been reading talk about registering your web service once it's ready for use by others. Is registering a web service required to use the service?
For example, let's say I have a web application on a company intranet and I create another web service app that retrieves some sort of useful information to be displayed on this private intranet site. Would this new web service require being registered just so my web app can use it or can the web app simply interface directly to the new web service (following the WSDL file) without the need of some sort of UDDI registry?
You can certainly use the service without the UDDI registry.
I have created several Web Services and have immediately used them without registering them. Registration gives others confidence that your Web Service is legitimate and descriptions of how to interact with those services.
Imagine doing development where you have to register any Web Service before using it. Yikes!
No, not at all.
You are probably talking about API directories you may register your WS at. Like UDDI or what it’s named. Entirely optional.
Nobody uses UDDI anymore. It's an idea whose time has come and gone.
It was thought that there would be public registries of web services that everyone would use to find a web service to meet their needs. That never happened.
How could either the service or the app know whether or not the service was registered?
Furthermore, why would they care?
If you're trying to use service orientation the right way, your web services should be registered within a service registry. The registry should contain the published contract of the services and any meta-data that helps the discovery process.
A different questions is: does a service consumer program need to look up a registry and dynamically bind the service it needs to call? NO, NOT AT ALL.
But then, what discovery process am I talking about?
I'm referring to a human (developer, architect, etc.) who is designing/developing a program that needs to call a service. This person should have means to search what services are available in his/her organization. If not, the benefit of reusing services is compromised.
Discovery is also about humans finding out there's a service somewhere in the IT organization that offers the functionality they want.
In this case, the registry can be as simple as an html report that is created and updated manually or generated by parsing (xslt comes handy) the wsdl files.