Skip to main content

Streamlining the Core Service Java Client

In a previous post (, I was presenting the Java client for Core Service. In this post, I decided to post the distributable JAR on my Google Code project page. You can find the JAR distributable [direct link] for Core Service Java client for Tridion 2011 SP1 HR1 at the following URL:

The only new feature of this distribution is the CoreServiceFactory class in package mitza.coreservice.client, which allows you to easily obtain a Core Service client object. The following methods are exposed:
  • getBasicHttpClient() - Get the singleton CoreService client for the BasicHttp endpoint;
  • getService() - Get the singleton CoreService2011 service object. This method is used internally by the get*Client methods. The logic uses a WSDL local to the JAR rather than connecting and downloading the WSDL from the remote Core Service server;

The factory also allows to specify the Core Service base URL, user name and password:
  • setDefault(String coreServiceBaseUrl) - Set the default CoreService URL. The user name and password are omitted in this case -- the currently logged in user is used implicitely;
  • setDefault(String userName, String password) - Set the default CoreService user and password. The Core Service base URL is omitted in this case -- the URL http://localhost is used implicitely
  • setDefault(String coreServiceBaseUrl, String userName, String password) - Set the default CoreService URL, user name and password;

Example: how to get a Core Service client object:

CoreServiceFactory.setDefault("http://t2011sp1hr1.playground", "administrator", "password");
ICoreService client = CoreServiceFactory.getBasicHttpClient();

The distributable contains a test class Test in package mitza.coreservice.client. The program expects 0 to 3 arguments ranging from only specifying the URL to all 3 params (URL, user name, password).

public static void main(String[] args) throws Exception {
    if (args.length == 1) { // URL
    } else if (args.length == 2) { // username, password
        CoreServiceFactory.setDefault(args[0], args[1]);
    } else if (args.length == 3) { // URL, username, password
        CoreServiceFactory.setDefault(args[0], args[1], args[2]);
    } else {

    ICoreService client = CoreServiceFactory.getBasicHttpClient();

    System.out.println("Api version: " + client.getApiVersion());

    UserData currentUser = client.getCurrentUser();
    System.out.println("Current user: '" + currentUser.getTitle() + "' '" +
            currentUser.getDescription() + "' " + currentUser.getId());

    System.out.println("Publication objects:");
    PublicationsFilterData filter = new PublicationsFilterData();
    ArrayOfIdentifiableObjectData systemWideList = client.getSystemWideList(filter);
    for (IdentifiableObjectData iod : systemWideList.getIdentifiableObjectData()) {
        PublicationData publication = (PublicationData) iod;
        System.out.println("\t" + publication.getTitle());

    System.out.println("Publications XML:");
    GetSystemWideListXmlResult resultXml = client.getSystemWideListXml(filter);
    Element element = (Element) resultXml.getAny();
    Utils.printDocument(element.getOwnerDocument(), System.out);

To run the code, one could use runtest.bat available:

set classpath=;core-service-client-2011sp1hr1.jar
java -cp %classpath% mitza.coreservice.client.Test http://localhost author tridion


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: I stumbled upon the following post from 2008 (!!!), , 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

Debugging a Tridion 2011 Event System

OK, so you wrote your Tridion Event System. Now it's time to debug it. I know this is a hypothetical situtation -- your code never needs any kind of debugging ;) but indulge me... Recently, Alvin Reyes ( @nivlong ) blogged about being difficult to know how exactly to debug a Tridion Event System. More exactly, the question was " What process do I attach to for debugging even system code? ". Unfortunately, there is no simple or generic answer for it. Different events are fired by different Tridion CM modules. These modules run as different programs (or services) or run inside other programs (e.g. IIS). This means that you will need to monitor (or debug) different processes, based on which events your code handles. So the usual suspects are: dllhost.exe (or dllhost3g.exe ) - running as the MTSUser is the SDL Tridion Content Manager COM+ application and it fires events on generic TOM objects (e.g. events based on Tridion.ContentManager.Extensibility.Events.CrudEven