we want to integrate sharepoint to our existing portal. The purpose of doing this is to use some of the features of sharepoint such as wiki,blogs etc.
is there any way we can aechvie this i.e. intigrating to our existing portal to use only specific services of share point.
Related
In one instance my custom mobile app that connects to Bizagi platform has to save data to SAP back-end. Looking for options to implement this.
To avoid having the mobile app interfacing with multiple back-end/platforms, looking for options to achieve this through the Bizagi interface.
It is learned that Bizagi has out of the box connectors for SAP et. to integrate one with other.
Also learned that Bizagi exposes out of the box webservices that extends its features to custom front-end apps.
Along with these out of the box Bizagi webservices, is there any provision in Bizagi to develop and expose custom webservices to pass data from mobile app to back-end systems such as SAP.
You can use several of the methods exposed in the Bizagi API to create cases, trigger events, perform activities, query entities, etc. etc.
The services with which you can affect the flow are exposed in: http://+ (YourServiceURL)+ /+ (NameProyect)+ /WebServices/WorkflowEngineSOA.asmx
The services with which you can affect or query the entities are exposed in: http://+ (YourServiceURL)+ /+ (NameProyect)+ /webservices/EntityManagerSOA.asmx
Also you can consult into the official documentation depending your versión and your needs and look at the request examples for the services
Additionally it has a connection with SAP services through connectors within the tool
I am looking at SharePoint web services and would like to know the best way to work with web parts. I have figured out most of the other stuff we will need but the functionality around web parts and the SharePoint Web Services seems complicated. So how do I
Retrieive a particular web part with HTML content? Is this possible?
Find out what web parts are on what pages?
I know that I can get the rendered html for an entire page through web services (although why that is exactly useful when you can retrieve the web page directly I'm not sure.) but would like to know if it is possible to embed web parts in external web sites through SharePoint Web Services.
"Web parts" are a means of "programming" Sharepoint. They are to Sharepoint much like "controls" are to Visual Basic, or "views" are to Android.
They're a creature of Sharepoint - I can't imagine you'd use them on an Apache server on a Linux host, for example.
Sharepoint web services, however, are intended to be a good way for Sharepoint to communicate with non-Microsoft technologies (like Java, for example).
If your "application" involves a heterogeneous mix of web servers and platforms, then Web Services is probably the way to go.
If your "application" resides exclusively on the Sharepoint server, and your "clients" just browse to it (preferably, browse to it with IE), then web parts might be a good choice.
Is it possible for a SharePoint 2010 Web Part to expose a web service (WCF?)?
I want a Web Part to send emails if a certain condition is met. The web part should be hit every 15 mins via a call initiated from a custom in-house scheduler.
Cheers
A web part is just a visual component. It can expose a web service. However, custom web services can be created and deployed to SharePoint where you can access data from a site (a list maybe) and add custom logic to send the email.
Here's a good guide on how to deploy web services to SharePoint.
I have a Standalone application, which needs to access a Sharepoint list. I bumped into a few articles, mentioning Web Service is the way to go about it.
But I am unable to find a step by step path to write a web service to fetch list from sharepoint. In addition to this, the application can take a WSDL file as an input.
Please let me know how to proceed about this scenario.
If you are using SharePoint 2007, then web services is the only way to do this. Here is a list of the different web services available.
If you are using SharePoint 2010 you can use the client object model.
You can simply use the SharePoint webservice Lists.asmx (both in SharePoint 2007 and 2010)
In your application, add a web reference 'http://(sharepoint-url)/_vti_bin/lists.asmx'
Once done, you can use the method GetList.
For more information, http://msdn.microsoft.com/en-us/library/lists.lists.getlist(v=office.12).aspx#Y82
So here is the scenario:
I have a MOSS 2007 box and I want my clients to be able to access a SharePoint site via the internet. I am told that I will be using an IPA and AD for authentication. However I have a DB outside of SharePoint that holds various business data and I want to use Web Services to access the data, manipulate it, and send it back to SharePoint via web parts.
The issue is that, from what I understand, I am going to have to authenticate the AD user every time a request to the Web Service happens. Obviously I dont want to do this every time because they have already authenticated to get onto the site, however I do want each call to have some form of security so its not open calls to my db. I do plan on having other applications access this service outside of SharePoint, so I dont want to have to reinstall the service for each application or even again.
Has anyone had to perform this task or something similar or do you have any suggestions on how to do this?
Thank you in advance and happy coding!
Why not just deploy the webservice to Sharepoint using a Sharepoint solution and a Feature.
That way it will be running under the sharepoint app pool and all authentication is done by sp.
Edit:
Seeing that SharePoint should not be in "control" (as stated in the comment), you should create the webservice, and run the application it's under in as using Windows Authentication. IMHO you should create a WCF Service. The, using the information found in this article you make the Service authenticate users against the AD usergroups they are in. see the "Security: Authentication" section of the article.
Then in Visual Studio you create a webpart and add a service reference to the project, pointing to your newly created Service. Have the webpart perform the needed logic (i.e. display data etc.)
Deploy the webpart to SharePoint using a SharePoint solution (.wsp files, created with WSPBuilder). Google for SharePoint + wspbuilder + tutorials. The solution should contain 1 feature to deploy the webpart. WSPBuilder integrates with VS and allows for the creation of WSPBuilde project. add a webpart feature item to the project (it will create the xml (deployment related) and code file for the webpart.