UnPublising the content

Hi ,

we have a requirement of unpublishing and then deleting the content from vcm of specific CTD type.we have wriiten a below java code for it which takes the vcm id of the ci as a parameter and unpublishes the content item.

private static void unpublishContent(String sSiteName, ContentInstance ci)throws Exception {
           String jobName = "";
           ObjectId jobId = null;
           String jobDescription = "UnPublish";
           DeploymentClient deploymentClient = null;
           ManagedObjectVCMRef movr = null;

           try {
               Site site = Site.findByName(sSiteName);
               System.out.println("DeleteWciti - site: "   + site);

               SiteRef oSiteRef = new SiteRef(site);
               System.out.println("DeleteWciti - site: " + oSiteRef);

               System.out.println("SiteName: " + sSiteName);
               jobName = "UnPublish wciti ci";
               System.out.println("jobName: " + jobName);

               deploymentClient = new DeploymentClient(oSiteRef);
               System.out.println("deploymentClient: " + deploymentClient);

               System.out.println("creating job.");
               movr = ci.getContentManagementId();
               DeploymentJobDefinition jobDef = new DeploymentJobDefinition(jobName, JobType.UNPUBLISH);
               ContentInstancePattern pattern = new ContentInstancePattern(movr);
               jobDef.setContentPattern(pattern, false);
               jobDef.setDescription(jobDescription);

               JobReport jobReport = deploymentClient.createJob2(jobDef);
               System.out.println("created job: " + jobId);

               deploymentClient.launchJob(jobReport.getJobData().getId());
               System.out.println("job launched.");

               // deploymentClient.releaseJob(jobId);
           } catch (Exception e) {
               System.out.println("ERROR while creating Unpublish job; VCM ID = "
                       + movr);
               System.out.println("Exception Message: " + e.getMessage());
               if ((null != deploymentClient) && (null != jobId)) {
                   deploymentClient.invalidateJob(jobId);
               }
               throw e;
           }
       }

Once the code is getting executed we also see that the jobs are getting successfully created and completed.But when we verify the delivery DB the content items are still exisiting.

We are using vcm 7.6.

Can any of me know what more needs to be done so that the content items are removed from delivery db also.

Thanks,

Soujanya

Find more posts tagged with

Comments

Mario_DAnna

You might have some of the assets that you are unpublishing which has been "implicitly" deployed to the delivery stage because they were linked by some other published content.

In this case, unpublishing the piece of content doesn't have the effect of removing it from the delivery stage since the asset itself is not in the "published" state for the VCM.

Deleting the content will also remove it from the delivery stage so it is useless to unpublish them first.

Your problem here is that you should not delete content which is referenced by other content, so you might wish to first remove all references.

-m

From: eLink Entry: Discussion Group - Web Experience Management [mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: Tuesday, November 22, 2011 9:47 AM
To: eLink Recipient
Subject: UnPublising the content

UnPublising the content

Posted by soujanyab@virtusa.com (Basana, Soujanya) On 11-22-2011 03:40

Hi ,

private static void unpublishContent(String sSiteName, ContentInstance ci)throws Exception {
           String jobName = "";
           ObjectId jobId = null;
           String jobDescription = "UnPublish";
           DeploymentClient deploymentClient = null;
           ManagedObjectVCMRef movr = null;

           try {
          ! ;     Site site = Site.findByName(sSiteName);
               System.out.println("DeleteWciti - site: "   + site);

               SiteRef oSiteRef = new SiteRef(site);
               System.out.println("DeleteWciti - site: " + oSiteRef);

               System.out.println("SiteName: " + sSiteName);
               jobName = "UnPublish wciti ci";
               System.out.println("jobName: " + jobName);

               deploymentClient = new DeploymentClient(oSiteRef);
               System.out.println("deploymentClient: " + deploymentClient);

               System.out.println("creating job.");
               movr = ci.getContentManagementId();
               DeploymentJobDefinition jobDef = new DeploymentJobDefinition(jobName, JobType.UNPUBLISH);
               ContentInstancePattern pattern = new ContentInstancePattern(movr);
               jobDef.setContentPattern(pattern, false);
               jobDef.setDescription(jobDescription);

               JobReport jobReport = deploymentClient.createJob2(jobDef);
               System.out.println("created job: " + jobId);

               deploymentClient.launchJob(jobReport.getJobData().getId());
               System.out.println("job launched.");

               // deploymentClient.releaseJob(jobId);
           } catch (Exception e) {
               System.out.println("ERROR while creating Unpublish job; VCM ID = "
                       + movr);
               System.out.println("Exception Message: " + e.getMessage());
               if ((null != deploymentClient) && (null != jobId)) {
                   deploymentClient.invalidateJob(jobId);
               }
               throw e;
           }
       }

Once the code is getting executed we also see that the jobs are getting successfully created and completed.But when we verify the delivery DB the content items are still exisiting.

We are using vcm 7.6.

Can any of me know what more needs to be done so that the content items are removed from delivery db also.

Thanks,

Soujanya

[To post a comment, use the normal reply function]
Forum:	Discussion Group - Web Experience Management
Content Server:	Knowledge Center

Soujanya_Basana

Hi Madan,

I have also tried first by unpublishing Referred Object and Reffering objects to the actual content and make sure those objects are not exisiting in delivery DB then upublishing the main CI.

But still the content is existing in delivery DB.

Thanks,

Soujanya

Mark_Scheevel

That code looks more or less correct. But, remember, publishing/unpublishing is asynchronous, and DeploymentClient.launchJob just sets things in motion; just because it returns without an error doesn't mean that unpublishing is finished. It only means that the job has been submitted to the site's deployment workflow, which will in turn submit it to your delivery stage(s), where it will eventually be executed. So check your job console to make sure that something isn't gummed up and causing your jobs just to queue up waiting for a problem to be resolved.Mark________________________________________From: eLink Entry: Discussion Group - Web Experience Management [v7webcontentmanagement@elinkkc.opentext.com]Sent: Tuesday, November 22, 2011 3:23 AMTo: eLink RecipientSubject: RE UnPublising the contentRE UnPublising the content Posted by soujanyab@virtusa.com (Basana, Soujanya) On 11-22-2011 04:18Hi Madan,I have also tried first by unpublishing Referred Object and Reffering objects to the actual content and make sure those objects are not exisiting in delivery DB then upublishing the main CI.But still the content is existing in delivery DB.Thanks,Soujanya________________________________[To post a comment, use the normal reply function]Topic: UnPublising the contentForum: Discussion Group - Web Experience ManagementContent Server: Knowledge Center

Oren_Mondshein

Hi,

Add at the end, (before the catch):

----

deploymentClient.waitForJob(jobId);

ci.commit(); // this one is critical for solving your problem

----

Good luck,

Shirley

David_Stiles

This is not correct. There is no need in the ci.commit() here.Nothing is being modified on the ci.

And the deploymentClient.waitForJob() call is only needed if youwant to do something else and only after the job has finished. With this logicdoing nothing after job completion there is no need to wait for the job here.

From: eLink Entry:Discussion Group - Web Experience Management[mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: Wednesday, November 23, 2011 8:16 AM
To: eLink Recipient
Subject: UnPublising the content

UnPublising the content

Posted by oren@realcommerce.co.il (Mondshein, Oren) On 11-23-2011 09:02

Hi,

Add at the end, (before the catch):

----

deploymentClient.waitForJob(jobId);

ci.commit(); // this one is critical for solving your problem

----

Good luck,

Shirley

[To post a comment, use the normal reply function]
Topic:	UnPublising the content
Forum:	Discussion Group - Web Experience Management
Content Server:	Knowledge Center

Oren_Mondshein

Hi,

The ci.commit() helped me when I had the same problem of the publish status not changing. but maybe it was just coincidence.

Shirley

David_Stiles

The only effect that commit will have on publish status is thatit will cause a item with a publish status of ‘published’ to have a publishstatus of ‘stale’.

From: eLink Entry:Discussion Group - Web Experience Management[mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: Wednesday, November 23, 2011 10:29 AM
To: eLink Recipient
Subject: RE UnPublising the content

RE UnPublising the content

Posted by oren@realcommerce.co.il (Mondshein, Oren) On 11-23-2011 11:19

Hi,

The ci.commit() helped me when I had the same problem of the publish status not changing. but maybe it was just coincidence.

Shirley

[To post a comment, use the normal reply function]
Topic:	UnPublising the content
Forum:	Discussion Group - Web Experience Management
Content Server:	Knowledge Center