Skip to main content

JQuery JavaScript Client for CoreService

In my previous post, I presented a JavaScript CoreService client that was using the out-of-the-box Visual Studio project and a WCF generated JS proxies using the Microsoft AJAX framework.

In this blog post, I write about a JQuery client for CoreService that is lighter and only depends on JQuery. I took my inspiration from Yoav's blog post Creating a Webservice Proxy with jQuery

The server part remains untouched. This means I can only focus on the JavaScript client.

CoreService is secured with Basic or Federated authentication. I am focusing on Basic auth in this post, mainly because it is so simple to use from JS.

The main entry point in the code is the ServiceProxy class. This is where we define the constructor and where we set the endpoint to use for CoreService and the username, password combination to use.

The ServiceProxy makes use of the JQuery's $.ajax function, where it performs a POST to the CoreService endpoint, sets the payload to send, Authorization header and the success, failed callback functions.

ServiceProxy = function (adminUser, adminPassword, endpoint) {
    this._basicAuth = "Basic " + btoa(adminUser + ":" + adminPassword);
    this._baseURL = endpoint;
};

ServiceProxy.prototype =
{
    _defaultErrorHandler: function (xhr, status, error) {
        alert(xhr.status + " " + xhr.statusText + "\r\n" + xhr.responseText);
    },

    _doAjax: function (method, data, fnSuccess, fnError, isAsync) {
        if (!data) data = {};
        if (isAsync == undefined) isAsync = true;
        if (!fnError) fnError = this._defaultErrorHandler;

        $.ajax({
            type: "POST",
            url: this._baseURL + method,
            data: data,
            contentType: "application/json; charset=utf-8",
            headers: { "Authorization": this._basicAuth },
            success: fnSuccess,
            error: fnError,
            async: isAsync
        });
    },

    getCurrentUser: function (success, error) {
        this._doAjax("GetCurrentUser", null, success, error);
    }
};

The code above also declares method getCurrentUser, which calls the CoreService GetCurrentUser method without posting any payload.

The HTML

The sample code below connects to the CoreService endpoint defined earlier and performs a sample call to retrieve the current user.

Notice that the JS code only requires the JQuery library and the ServiceProxy we defined earlier.

Since we are declaring contentType as application/json, JQuery will parse and decode the JSON response from the web-service into a JavaScript object.

<!DOCTYPE html>
<html>
<head>
    <script src="jquery-1.10.2.js"></script>
    <script src="ServiceProxy.js"></script>
</head>
<body>
    <script type="text/javascript">
        var proxy = new ServiceProxy("mihai@adfs", "p@assword",
            "https://web85.playground/webservices/CoreService201603.svc/rest/");

        function userSuccess(result) {
            if (!result) {
                alert("no result");
                return;
            }

            if (result.hasOwnProperty("d")) {
                result = result.d;
            }

            alert("Retrieved user: " + result.Id + " | " + result.Description);
        }

        $(document).ready(function () {
            proxy.getCurrentUser(userSuccess);
        });
    </script>
</body>
</html>




Comments

Popular posts from this blog

Running sp_updatestats on AWS RDS database

Part of the maintenance tasks that I perform on a MSSQL Content Manager database is to run stored procedure sp_updatestats . exec sp_updatestats However, that is not supported on an AWS RDS instance. The error message below indicates that only the sa  account can perform this: Msg 15247 , Level 16 , State 1 , Procedure sp_updatestats, Line 15 [Batch Start Line 0 ] User does not have permission to perform this action. Instead there are several posts that suggest using UPDATE STATISTICS instead: https://dba.stackexchange.com/questions/145982/sp-updatestats-vs-update-statistics I stumbled upon the following post from 2008 (!!!), https://social.msdn.microsoft.com/Forums/sqlserver/en-US/186e3db0-fe37-4c31-b017-8e7c24d19697/spupdatestats-fails-to-run-with-permission-error-under-dbopriveleged-user , which describes a way to wrap the call to sp_updatestats and execute it under a different user: create procedure dbo.sp_updstats with execute as 'dbo' as

Content Delivery Monitoring in AWS with CloudWatch

This post describes a way of monitoring a Tridion 9 combined Deployer by sending the health checks into a custom metric in CloudWatch in AWS. The same approach can also be used for other Content Delivery services. Once the metric is available in CloudWatch, we can create alarms in case the service errors out or becomes unresponsive. The overall architecture is as follows: Content Delivery service sends heartbeat (or exposes HTTP endpoint) for monitoring Monitoring Agent checks heartbeat (or HTTP health check) regularly and stores health state AWS lambda function: runs regularly reads the health state from Monitoring Agent pushes custom metrics into CloudWatch I am running the Deployer ( installation docs ) and Monitoring Agent ( installation docs ) on a t2.medium EC2 instance running CentOS on which I also installed the Systems Manager Agent (SSM Agent) ( installation docs ). In my case I have a combined Deployer that I want to monitor. This consists of an Endpoint and a

SDL Web 8 - Content Delivery Microservices

Among the new features in SDL Web 8 there are the Content Delivery Microservices, namely: Audience Manager Content Deployer Contextual Image Delivery Discovery Service Dynamic Content Dynamic Linking Profiling and Personalization Metadata Query Taxonomy User Generated Content These microservices make up the Content Interaction Services and they expose the existing Content Delivery in-process APIs as RESTful services. They provide the server-side component in a Services-Oriented Architecture and act as data layer between the the web client and the Content Delivery Storage Layer. According to the SDL marketing, these microservices: Simplify upgrades, thus offering shorter time to value Modernize architecture, offering better separation between the web application and Tridion APIs Offer more flexibility with less downtime and improved scalability Improve quality, being self-running, contained and having less dependencies In technical words, these microservices