External Rest API call from SharePoint 2013 On Premises

Hi All,
May my questions is silly but I am totally tired by trying different things.
I need to call a third party rest api from my SharePoint Designer page using &Ajax call.First time when i tried it gave me access denied then added this line
jQuery.support.cors =true;
Again error changed to "No Transport" last time i had the same situation i saw some sites where people mentioned some power shell script to enable something at web app level but didn't remember if possible can some help me please i already wasted
my half long weekend :(
Note :- This is SharePoint On Premises
Thanks in Advance :)

Similar Messages

401 Unauthorized Error When calling a SharePoint REST web service from SharePoint 2013 Workflow

We have our Workflow Manger installed on the same server as our SharePoint 2013 WFE development environment. When creating a SharePoint 2013 Workflow all Calls to a SharePoint 2013 REST web service results in a 401 Unauthorized error.
As an example I created a simple workflow that should return a JSON result. The REST Url returns the results in the browser without error.
Set Variable:webServiceUrl to https://<hostnamedsitecollection>/_vti_bin/client.svc/web/lists/getbytitle('ISR%20Approvers')/Items?$select=Title&$filter=Title%20eq%20%27General%27
then Build{...} Dictionary (Output to Variable:requestHeaders)
then Call [%Variable:webServiceUrl%] HTTP web service with request (ResponseContent to Variable:responseContent |ResponseHeaders to responseHeaders | ResponseStatusCode to Variable:responseCode)
The RequestHeader is set to the requestHeaders variable though the web service call properties
then Log Variable:responseCode to the workflow history list
After manually running the workflow in SharePoint on a list item in the ISR Approvers list it Logs "Unauthorized" in the Workflow History Log. It does this with every SharePoint REST web service call that I have tried through the workflow.
It doesn't have anything to do with the Workflow Manger being installed on the same machine as the SharePoint WFE does it?
Thank You for any insight

Hi,
According to your post, my understanding is that you had 401 Unauthorized Error when calling a SharePoint REST web service from SharePoint 2013 Workflow.
Please make sure you use the ‘Call HTTP Web Service’ correctly.
You can enter the URL into the brower to check whether it is correctly.
You need to
create the Request header requestHeaders
using a Dictionary:
Accept : application/json;odata=verbose
Content-Type : application/json;odata=verbose
To associate the
requestHeaders variable, select the Call action
property, set the RequestHeaders property to
requestHeaders.
Please refer to the following articles:
Working with Web Services in SharePoint 2013 Workflows using SharePoint Designer 2013
Calling the SharePoint 2013 Rest API from a SharePoint Designer
Workflow
In addtion, you need to make sure you install the workflow manager correctly.
More information:
Install and configure workflow for SharePoint Server 2013
Known Issues in Workflow Manager 1.0
Troubleshooting Workflow Manager 1.0 Management and Execution
Best Regards,
Linda Li
Linda Li
TechNet Community Support

HTTP REST API call to CPSC 10.x from an external system

Hi,
I would like to know the below items.
Is it possible to connect with the CPSC 10.x from an external system via HTTP REST API call to process a request and complete a task?
Is it possible to create a new ticket / request in CPSC for a specific service via the HTTP REST API call?
One of the use case is to know how many requests are pending in a queue via a HTTP REST API call? How to pass a queue name in the HTTP REST API call to get the result? These kind of custom piece is not available in the integration guide.
Is there any specific REST API guide available which Cisco provides for the REST capability in CPSC?
Any help is highly appreciated!
Thanks.

When a task is invoked from a service catalog request to an external system, the request remains open and the task is pending until the external system issues a call to complete the task. The API for completing the task is SOAP-based. Check out the Cisco Prime Service Catalog Integration Guide. Within the doc, go to the section about "Web Service Listener Adapter" for the WSDL.
You can order a service within Prime Service Catalog with a SOAP call, which is also documented in this same document. Starting with Prime Service Catalog 10.1, you will have a way to order a service via a REST API.
Existing REST APIs are also documented in the integration guide.

Sharepoint 2013 REST API calls with JASONP support

We are working on sharepoint online integration with PHP Based application. We need to provide REST API call which supports JSONP.
So is it possible to create new REST API Endpoints in Sharepoint online APP? Please sugggest right direction.

Hi,
In Office 365 (aka SharePoint Online), you can simply consume the SharePoint data through REST API or WS call,but cannot create your own endpoint.
By default you can get the JSON response from the Office 365 REST API,its upto you to use the JSONP on your client compatibility not on SharePoint online REST API.
Sometime before I tried, It didn't work for me.
If you develop the AppModel, SPRequestor.js does the same job(overcome the Cross domain restriction) the what JSONP does.
Murugesa Pandian| MCPD | MCTS |SharePoint 2010

HTTP Rest api call maximum results

Hi all,
I´m trying to get data from the portal using the follwoing rest api call:
http://<ServerURL>/RequestCenter/nsapi/serviceitems/serviceitemsubscription
but it only gives me 20 results, which I believe it is the default, is there any way to get all the elements or a way to page all the results?
Thanks
Alex.

Hi all,
found some info on the Integration guide (Cisco Prime Service Catalog 10.0 Integration Guide) page 222, there is a section regarding Paging, but the max results are 50.
I was looking a simple way to export / import info from the portal, but it seems Java is going to be neded instead http nsapi.
Regards,
Alex.

ADFS SSO and SharePoint 2013 on-premise Hybrid outbound search results from SharePoint Online - does it work?

Hi,
I want to setup an outpund hybrid search for SharePoint 2013 on-premise to SharePoint Online.
But I'm not shure if this works with ADFS SSO.
Has somebody experience with this setup?
Here's my guide which I'm going to use for this installation:
Introduction
In this post I'll show you how to get search results from your SharePoint Online in your SharePoint 2013 on-premise search center.
Requirements
User synchronisation ActiveDirectory to Office 365 with DirSync
DirSync password sync or ADFS SSO
SharePoint Online
SharePoint 2013 on-premise
Enterprise Search service
SharePoint Online Management Shell
Instructions
All configuration will be done either in the Search Administration of the Central Administration or in the PowerShell console of your on-premise SharePoint 2013 server.
Set up Sever to Server Trust
Export certificates
To create a server to server trust we need two certificates.
[certificate name].pfx: In order to replace the STS certificate, the certificate is needed in Personal Information Exchange (PFX) format including the private key.
[certificate name].cer: In order to set up a trust with Office 365 and Windows Azure ACS, the certificate is needed in CER Base64 format.
First launch the Internet Information Services (IIS) Manager
Select your SharePoint web server and double-click Server Certificates
In the Actions pane, click Create Self-Signed Certificate
Enter a name for the certificate and save it with OK
To export the new certificate in the Pfx format select it and click Export in the Actions pane
Fill the fields and click OK Export to: C:\[certificate
name].pfx Password: [password]
Also we need to export the certificate in the CER Base64 format. For that purpose make a right-click on the certificate select it and click on View...
Click the Details tab and then click Copy to File
On the Welcome to the Certificate Export Wizard page, click Next
On the Export Private Key page, click Next
On the Export File Format page, click Base-64 encoded X.509 (.CER), and then click Next.
As file name enter C:\[certificate
name].cer and then click Next
Finish the export
Import the new STS (SharePoint Token Service) certificate
Let's update the certificate on the STS. Configure and run the PowerShell script below on your SharePoint server.
if(-not (Get-PSSnapin "Microsoft.SharePoint.PowerShell" -ErrorAction SilentlyContinue)){Add-PSSnapin "Microsoft.SharePoint.PowerShell"}
# set the cerficates paths and password
$PfxCertPath = "c:\[certificate name].pfx"
$PfxCertPassword = "[password]"
$X64CertPath = "c:\[certificate name].cer"
# get the encrypted pfx certificate object
$PfxCert = New-Object System.Security.Cryptography.X509Certificates.X509Certificate2 $PfxCertPath, $PfxCertPassword, 20
# import it
Set-SPSecurityTokenServiceConfig -ImportSigningCertificate $PfxCert
Type Yes when prompted with the following message.
You are about to change the signing certificate for the Security Token Service. Changing the certificate to an invalid, inaccessible or non-existent certificate will cause your SharePoint installation to stop functioning. Refer
to the following article for instructions on how to change this certificate: http://go.microsoft.com/fwlink/?LinkID=178475. Are you
sure, you want to continue?
Restart IIS so STS picks up the new certificate.
& iisreset
& net stop SPTimerV4
& net start SPTimerV4
Now validate the certificate replacement by running several PowerShell commands and compare their outputs.
# set the cerficates paths and password
$PfxCertPath = "c:\[certificate name].pfx"
$PfxCertPassword = "[password]"
# get the encrypted pfx certificate object
New-Object System.Security.Cryptography.X509Certificates.X509Certificate2 $PfxCertPath, $PfxCertPassword, 20
# compare the output above with this output
(Get-SPSecurityTokenServiceConfig).LocalLoginProvider.SigningCertificate
[/code]
## Establish the server to server trust
[code lang="ps"]
if(-not (Get-PSSnapin "Microsoft.SharePoint.PowerShell" -ErrorAction SilentlyContinue)){Add-PSSnapin "Microsoft.SharePoint.PowerShell"}
Import-Module MSOnline
Import-Module MSOnlineExtended
# set the cerficates paths and password
$PfxCertPath = "c:\[certificate name].pfx"
$PfxCertPassword = "[password]"
$X64CertPath = "c:\[certificate name].cer"
# set the onpremise domain that you added to Office 365
$SPCN = "sharepoint.domain.com"
# your onpremise SharePoint site url
$SPSite="http://sharepoint"
# don't change this value
$SPOAppID="00000003-0000-0ff1-ce00-000000000000"
# get the encrypted pfx certificate object
$PfxCert = New-Object System.Security.Cryptography.X509Certificates.X509Certificate2 $PfxCertPath, $PfxCertPassword, 20
# get the raw data
$PfxCertBin = $PfxCert.GetRawCertData()
# create a new certificate object
$X64Cert = New-Object System.Security.Cryptography.X509Certificates.X509Certificate2
# import the base 64 encoded certificate
$X64Cert.Import($X64CertPath)
# get the raw data
$X64CertBin = $X64Cert.GetRawCertData()
# save base 64 string in variable
$CredValue = [System.Convert]::ToBase64String($X64CertBin)
# connect to office 3656
Connect-MsolService
# register the on-premise STS as service principal in Office 365
# add a new service principal
New-MsolServicePrincipalCredential -AppPrincipalId $SPOAppID -Type asymmetric -Usage Verify -Value $CredValue
$MsolServicePrincipal = Get-MsolServicePrincipal -AppPrincipalId $SPOAppID
$SPServicePrincipalNames = $MsolServicePrincipal.ServicePrincipalNames
$SPServicePrincipalNames.Add("$SPOAppID/$SPCN")
Set-MsolServicePrincipal -AppPrincipalId $SPOAppID -ServicePrincipalNames $SPServicePrincipalNames
# get the online name identifier
$MsolCompanyInformationID = (Get-MsolCompanyInformation).ObjectID
$MsolServicePrincipalID = (Get-MsolServicePrincipal -ServicePrincipalName $SPOAppID).ObjectID
$MsolNameIdentifier = "$MsolServicePrincipalID@$MsolCompanyInformationID"
# establish the trust from on-premise with ACS (Azure Control Service)
# add a new authenticatio realm
$SPSite = Get-SPSite $SPSite
$SPAppPrincipal = Register-SPAppPrincipal -site $SPSite.rootweb -nameIdentifier $MsolNameIdentifier -displayName "SharePoint Online"
Set-SPAuthenticationRealm -realm $MsolServicePrincipalID
# register the ACS application proxy and token issuer
New-SPAzureAccessControlServiceApplicationProxy -Name "ACS" -MetadataServiceEndpointUri "https://accounts.accesscontrol.windows.net/metadata/json/1/" -DefaultProxyGroup
New-SPTrustedSecurityTokenIssuer -MetadataEndpoint "https://accounts.accesscontrol.windows.net/metadata/json/1/" -IsTrustBroker -Name "ACS"
Add a new result source
To get search results from SharePoint Online we have to add a new result source. Run the following script in a PowerShell ISE session on your SharePoint 2013 on-premise server. Don't forget to update the settings region
if(-not (Get-PSSnapin "Microsoft.SharePoint.PowerShell" -ErrorAction SilentlyContinue)){Add-PSSnapin "Microsoft.SharePoint.PowerShell"}
# region settings
$RemoteSharePointUrl = "http://[example].sharepoint.com"
$ResultSourceName = "SharePoint Online"
$QueryTransform = "{searchTerms}"
$Provier = "SharePoint-Remoteanbieter"
# region settings end
$SPEnterpriseSearchServiceApplication = Get-SPEnterpriseSearchServiceApplication
$FederationManager = New-Object Microsoft.Office.Server.Search.Administration.Query.FederationManager($SPEnterpriseSearchServiceApplication)
$SPEnterpriseSearchOwner = Get-SPEnterpriseSearchOwner -Level Ssa
$ResultSource = $FederationManager.GetSourceByName($ResultSourceName, $SPEnterpriseSearchOwner)
if(!$ResultSource){
Write-Host "Result source does not exist. Creating..."
$ResultSource = $FederationManager.CreateSource($SPEnterpriseSearchOwner)
$ResultSource.Name = $ResultSourceName
$ResultSource.ProviderId = $FederationManager.ListProviders()[$Provier].Id
$ResultSource.ConnectionUrlTemplate = $RemoteSharePointUrl
$ResultSource.CreateQueryTransform($QueryTransform)
$ResultSource.Commit()
Add a new query rule
In the Search Administration click on Query Rules
Select Local SharePoint as Result Source
Click New Query Rule
Enter a Rule name f.g. Search results from SharePoint Online
Expand the Context section
Under Query is performed on these sources click on Add Source
Select your SharePoint Online result source
In the Query Conditions section click on Remove Condition
In the Actions section click on Add Result Block
As title enter Results for "{subjectTerms}" from SharePoint Online
In the Search this Source dropdown select your SharePoint Online result source
Select 3 in the Items dropdown
Expand the Settings section and select "More" link goes to the following URL
In the box below enter this Url https://[example].sharepoint.com/search/pages/results.aspx?k={subjectTerms}
Select This block is always shown above core results and click the OK button
Save the new query rule

Hi Janik,
According to your description, my understanding is that you want to display hybrid search results in SharePoint Server 2013.
For achieving your demand, please have a look at the article:
http://technet.microsoft.com/en-us/library/dn197173(v=office.15).aspx
If you are using single sign-on (SSO) authentication, it is important to test hybrid Search functionality by using federated user accounts. Native Office 365 user accounts and Active Directory Domain Services
(AD DS) accounts that are not federated are not recognized by both directory services. Therefore, they cannot authenticate using SSO, and cannot be granted permissions to resources in both deployments. For more information, see Accounts
needed for hybrid configuration and testing.
Best Regards,
Eric
Eric Tao
TechNet Community Support

Word Viewer will not open documents from Sharepoint 2013 in IE11

I've run into an issue while trying to open documents from SharePoint 2013 after upgrading to IE11. My organization uses Word Viewer with the compatibility pack and all other Word documents (local files, intranet hosted) will open with no problems. When
trying to open a Word document from SharePoint the Word Viewer will open, but the file does not. We have verified that all Windows Updates are installed. We have tried opening SharePoint in Compatibility View and Enterprise Mode. We have re-downloaded the
latest version of Word Viewer and reinstalled it along with the compatibility pack. If we open the SharePoint site in Explorer view and then open a Word document it will open in Word Viewer with no problem. Excel and PowerPoint documents open from SharePoint
with no problem. This is only affecting Word documents with Word Viewer. When using the full version of Word the documents open fine. Within SharePoint we have tried activating the site collection feature "Open Document In Client Applications by Default"
but it made no difference. We're completely at a loss how to make this work as there doesn't seem to be much information specifically pertaining to issues with Word Viewer.

Hi Victoria.
1. The PCs do not have Microsoft Office installed, nor are we using the Office Web Apps. "Word Viewer" means the Microsoft Word Viewer application available here (http://www.microsoft.com/en-us/download/details.aspx?id=4) that is available
free for read-only viewing of Word documents.
2. There are no errors when I open Word docs in Word Viewer. The Word Viewer application launches after clicking a Word document link in Sharepoint, but there is no file open in it. When that happens the IE11 Sharepoint window on the taskbar is flashing
yellow, but when I click back to it there are no messages or alerts to click on.
3. This issue does occur with all Word documents (.doc, .docx) in SharePoint. However, it does not occur when opening Word documents in the Word Viewer when they are local files or through IE11 from a non-SharePoint website like our local intranet.
Those files will open with no problem in Word Viewer.
4. I will try to get a screenshot, but we are working on creating images for deployment and I don't currently have a machine configured the same way. I'll work on reconfiguring one and post a screenshot.
Thank you for your help!

Problem opening documents from SharePoint (2013) libraries with Office 2010 and 2013 components installed

Hi
I've been encountering the problem of Office files failing to open from SharePoint 2013 libraries with the prefix of 'ms-excel:ofv|u|' etc. in the url. Following the
helpful questions and answers in the forum, I've identified the likely cause as the fact that my main Office installation is 2010, but I also have installed OneDrive for Business 2013 (which I need in order to sync document libraries with my local drive).
The solution I've seen suggested elsewhere of deactivating the SharePoint integration of Office 2013 components fails for two reasons: there is no way (or at least, I can't find one) of deactivating SharePoint integration probably because, deactivating
SharePoint integration would likely stop the syncing of libraries/folders.
One thing that I have noticed in my case that I've not seen mentioned elsewhere is that if I right-click a document and select 'open in new tab/window' the required
document opens directly in the relevant office package. I don't know if this is a useful observation, but it seems to be new information.
My question is, is there a way I can continue to sync libraries and open Office documents directly in Office 2010? My thoughts are possible changes to registry settings
(which I can do, but don't know enough to find the correct ones myself) or (re)installation of software in some appropriate order to leave the correct settings.
I have 'repaired' my Office 2010 installation without any observed affect on behavior.
Thanks
Ray
(I've just seen a suggestion that Office 2010 SP2 may fix this issue. I've requested to test this, but whilst this may fix my problem, rolling it out to
other users may be more problematic. In the meantime, other suggestions of solutions are welcome)

Hi,
According to your description, it is a good way to do a test about office 2010 SP2, here is an article about this issue- limitations of using the OneDrive for Business sync app with Office 2010 applications , it may help you.
http://office.microsoft.com/en-us/sharepoint-help/solve-problems-youre-having-with-the-onedrive-for-business-sync-app-HA104047973.aspx
Paul Shui
Microsoft Online Community Support
Please remember to click “Mark as Answer?on the post that helps you, and to click “Unmark as Answer?if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

Sorry, we couldn't open...Error opening office documents from SharePoint 2013 in the desktop applications

Sorry, we couldn't open...Error opening office documents from SharePoint 2013 in the desktop applications
One of our Managers encounters the error 'A problem occurred while accessing the Office document cache. Do you want to repair this problem?'
Then When he says yes it give a warning that the cache will be backed up and replaced
Then it says 'A new office document Cache has been created...'
Then it loads this cache with an error
Then After all that the next time he tries to open the document it says is encountered "Sorry, we couldn't open 'URL."
We have Reinstalled office 2013 on the users PC repaired the cache numerous times
Followed -  http://office.microsoft.com/en-gb/word-help/manually-rename-the-office-document-cache-HA101848838.aspx
Updated Lync to 2013 leaving Access as the only office 2010 application (required for legacy systems access)
Repair installed office 2010 and office 2013 again
The SharePoint site has been added to the trusted sites list and the set up assistant run from office 365
And the issue remains the Same all other users including some who also have Access 2010 for legacy systems access have no Issues OS is windows 7 32 Bit browser is IE 9
Office 365 said
Reply by Rachel Zhang MSFT Support
Hi Alex,
From your description, I notice that the issue is related to Office client. We would like to help you, but I’m sorry that our forum does not focus on this scenario and has limited resources regarding it. However, we have a dedicated support forum where
the support engineers will help you with the issues about Office client:
Microsoft Office Community:
http://answers.microsoft.com/en-us/office/forum/office_2013_release?tm=1365567547805
Feel free to sign in to the Office community and click Participate->Ask a Question to post the question with the relevant information.
Microsoft Office Community:
Feel free to sign in to the Office community and click to post the question with the relevant information.
Office team said
Hello Alex,
Thank you for posting your query in Microsoft Office Community.

Check if other excel works fine
Do you have any script\macro in excel file
Check if all application pool on all servers are running
both office and IE should be same build (64 or 32 bit)
what is the error message in ULS log and Event viewer
If this helped you resolve your issue, please mark it Answered

Can't open Excel files from Sharepoint 2013

I am having an issue with opening Excel files from SharePoint 2013. If I click on an excel file it comes up with the error below.
If I click Try again I get the message below also:
If I try to open Word or PDF files they open correctly in the appropriate client and I have the option of checking them out and editing them. Any ideas why this would only be happening to Excel files?
Thanks,
Shaun

Hi Shaun,
I understand that the Excel files cannot be opened from SharePoint in Microsoft Excel.
Can these files be viewed in the browser?
I recommend to download a copy of the files with issue and then open them in Excel to see if the issue still occurs.
If above cannot work, I recommend to repair Office.
Best regards.
Thanks
Victoria Xia
TechNet Community Support

Error occurs when I open the tasks list in MS Project Professional 2013 from SharePoint 2013

Hi,
I have created a SharePoint 2010 workflow for a tasks list that updates a list item column if the Date Complete <= Today's date & Percentage Complete = 100%
I used 'Set Field in Current Item' in the workflow & the values are updated in the list for the current item.
However, when I open the tasks list in MS Project Professional 2013 from SharePoint 2013, then I get a error "We can't write task - taskname to the SharePoint site. This is either because tasks list is in read only mode or because this task has a column
that requires unique value."
If I remove the 'Set Field in Current Item' in the workflow, then the error does not occur. However, the 'Set Field in Current Item' in the workflow is required.
Please provide solution to this issue ASAP. Your reply will be greatly appreciated.
Thanks in advance

Hi Jack,
A shot in the dark here. I'm not convinced the error is from the workflow. What is the definition of the list item column in SharePoint? Have you set the column to requiring a unique vale? Look at the column definition.

Disable Edit Report Option from SharePoint 2013 PowerView Dasboard

Hi All,
I have PowerView Dashboard in Sharepoint 2013, In a Preview Bar there are three options i.e. File, Edit Report, Full Screen.
The requirement is disable only Edit Report Option from preview bar not all.
Please help me if there is any possibility for the same.

Hi,
Based on your description, you want to disable the edit report option from SharePoint 2013 PowerView Dasboard.
There is a workaround:
You can change the permission of the report. You should upload the report to a SharePoint library and set a user have read-only permission of the report. When the user open the report and save the changes, it will have error. The user cannot edit the report.
The article below is about change the report permission in order to disable the edit option.
http://parasdoshi.com/2013/10/30/a-note-about-edit-report-button-seen-on-power-view-in-sharepoint/
Best regards
Sara Fan
TechNet Community Support

Word 2013 slow to open documents from SharePoint 2013

Hi all,
Word 2013 running on a Windows 8.1 client is take 2 or more minutes to open a document from SharePoint 2013. Excel takes less then 10 seconds from the same site in SharePoint.
I have remove all proxy configuration from IE, clear the Auto Detect Settings. Added the URL's to the intranet zone and disabled all IE addons. I have also performed a reset on IE, reinstall of Office and tried a number of workstations. All have the same
issue. The document just take forever to open.
Checking with Fiddler, I can see 3 requests hit the SharePoint server then nothing... after a few minutes the document opens.
Any ideas?
Cheers
Craig

Hi Craig,
For troubleshooting your issue, please take steps as below:
1.Open IE, go to "Tools > Internet Options > Connections > Lan Settings" and uncheck "Auto Detect Proxy".
2.From the File tab in Word application, select Options and then click on Advanced and then in the Display section of the dialog, check the box for
Disable hardware graphics acceleration.
3.Edit the registry at HKEY_CLASSES_ROOT\Word.Document.12\shell\Open and deleting the ddeexec key.
Also please have a look at the article:
https://msdn.microsoft.com/en-us/library/office/jj230106.aspx?f=255&MSPPError=-2147217396
Reference:
http://sharepoint.stackexchange.com/questions/19390/what-is-slowing-the-opening-of-office-documents/9203
http://answers.microsoft.com/en-us/office/forum/office_2013_release-word/office-2013-products-slow-to-open/baf311b0-6a47-498b-9836-39e0c8b94c46?page=1
Best Regards,
Eric
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

REST API call in SCOM 2012R2

Hi,
We are planning monitoring our cluster using SCOM 2102R2 server. REST API developed for our cluster. How to call these REST API calls in SCOM 2012R2 server? I searched, I am not able to find. Please help me with any steps or documents or with links. I am
struct here. I am new to SCOM 2012 server.
Thanks,
Boopalan

You can refer below links
http://mountainss.wordpress.com/2014/05/02/windows-azure-pack-service-management-api-samples-april-2014-wapack-scvmm-ws2012r2/
http://www.vmunify.com/tag/windows-server-2012-r2/
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

Best logging option for SharePoint 2013 on-premise application

What is the best logging option for SharePoint 2013 on-premise application?

Hi,
According to your post, my understanding is that you want to know the logging option in SharePoint 2013.
SharePoint has its own logging system called “Unified Logging System (ULS)“, we can use the ULS log to see if anything unexpected occurred, we can use the
ULSViewer for more convenient log viewing experience.
Or we can log information programmatically.
There are some logging classes can be used, such as
SPMonitoredScope , SPDiagnosticsService, or create your own “Diagnostics Service” – which is technically just a new class inherited
from SPDiagnosticsServiceBase.
We can also utilize diagnostics.asmx web service for the client side applications.
For more reference:
http://www.codeproject.com/Articles/620996/Five-suggestions-to-implement-a-better-logging-in
Thanks & Regards,
Jason
Jason Guo
TechNet Community Support

External Rest API call from SharePoint 2013 On Premises

Similar Messages

Maybe you are looking for