Skip to main content

ATG CA - different activity sources used @ BCC

Read about how a new link can be added in BCC home page @ http://tips4ufromsony.blogspot.com/2012/03/atg-ca-bcc-home-screen-how-to-add-new.html

Normally an ActivitySource.properties file define the set of actions that it supports under a genericActivityDefinitionFile. But some ActivitySource.properties  define the actions  using the workflowActivityDefinitionFiles.

For example consider the default "Content Administration" ,  "SearchAdministration",  " Merchanding "  and "Personalization" options in BCC homepage. Below I listed the ActivitySource.properties and other properties for these links. To get all these activitysource names, just take the /atg/bizui/activity/ActivityManager component @ dyn/admin.



Content Administration
ActivitySource  --> /atg/bizui/activity/PublishingActivitySource
genericActivityDefinitionFile


Search Administration
ActivitySource  --> /atg/bizui/activity/SearchingActivitySource
genericActivityDefinitionFile

Personalization
ActivitySource  -->  /atg/web/personalization/activity/PersonalizationActivitySource
workflowActivityDefinitionFiles  and genericActivityDefinitionFile

Merchanding
ActivitySource  -->  /atg/commerce/web/CommerceActivitySource
workflowActivityDefinitionFile

Consider the tasks under Merchandising,  Administer Commerce Search  and Manage Commerse Assets and a Browse option. These are defined in the workflowActivityDefinitionFile @ /atg/commerce/web/CommerceActivitySource. You could find the details in the below screen shot.



Also consider the tasks under Search Administration , these are defined  in the genericActivityDefinitionFile @ /atg/bizui/activity/SearchingActivitySource. You could find the details in the below screen shot.


The PublishingActivities.xml file is checked at intervals for modifications, so you can make changes to it without needing to restart the server. The interval is set to 5 minutes by default and is defined by the genericActivityFileModificationInterval property in the /atg/bizui/activity/PublishingActivitySource.properties component.

When you create a workflow in the ATG Control Center, it automatically displays in the ATG Business Control Center under Merchandising in the Operations list as long as you save the workflow in the /atg/registry/data/epubworkflows/Commerce directory. If you’d prefer to keep the workflow in a different directory, you need to update the /atg/commerce/web/CommerceActivitySource component workflowDirectories property to with the new directory name and path.

Labels:

Comments

  1. Anonymous25 September 2012 at 17:18

    Under Personalization there are 4 sub tasks Targeting and Segmentation, Preview Users, Internal Users, External Users. When i look into the xml /atg/web/personalization/activity/workflowActivities.xml i cannot see 4 activites.


    <workflow-activities>
    <activity>
    <id>personalization.editSegmentsAndTargeters</id>
    <workflow-name>/Common/commonWorkflow.wdl</workflow-name>
    <acl>Profile$role$epubAdmin:read;Profile$role$epubSuperAdmin:read;Profile$role$epubManager:read;Profile$role$epubUser:read;</acl>

    <resource-bundle>atg.web.personalization.WebAppResources</resource-bundle>
    <display-name-resource>personalization.editSegmentsAndTargeters.displayName</display-name-resource>
    <description-resource>personalization.editSegmentsAndTargeters.description</description-resource>

    <display-name-resource-2>personalization.editSegmentsAndTargeters.browse.displayName</display-name-resource-2>
    <description-resource-2>personalization.editSegmentsAndTargeters.browse.description</description-resource-2>
    <destination-page-2>
    <url>/AssetManager/assetManager.jsp</url>
    <activity-id>personalization.browseSegmentsAndTargeters</activity-id>
    <clear-context>true</clear-context>
    </destination-page-2>

    </activity>
    </workflow-activities>


    I need to add subtasks to my custom link created as per your previous post.

    Thanks

    ReplyDelete

Post a Comment

Popular posts from this blog

ATG - quick reference to commonly used DSP Tags

In this blog, I would like to give a quick reference to the most commonly used DSP Tags.Note that in this DSP tag details : bean refers to a Nucleus path, component name, and property name param refers to a Page parameter value refers to a Static-value var refers to a EL variable id refers to a scripting variable ============================================================== 1.dsp:importbean     example: <dsp:importbean bean="/atg/dynamo/droplet/Switch"/> ============================================================== 2.dsp:page     usage: It encloses a JSP. The dsp:page invokes the JSP handler, which calls the servlet pipeline and generates HTTPServletRequest.    example:    <dsp:page> ..... </dsp:page> ============================================================== 3.dsp:include     usage: Embeds a page fragment in a JSP.     example:   <dsp:include src="/myPage/Result...
9 comments
Read more

ATG - more about Forms and Form Handlers

An ATG form is defined by the dsp:form tag, which typically encloses DSP tags that specify form elements, such as dsp:input that provide direct access to Nucleus component properties. Find below a sample dsp:form tag.    <dsp:form action="/testPages/showPersonProperties.jsp" method="post" target="_top">      <p>Name: <dsp:input bean="/samples/Person.name" type="text"/>      <p>Age: <dsp:input bean="/samples/Person.age" type="text" value="30"/>      <p><dsp:input type="submit" bean="/samples/Person.submit"/> value="Click to submit"/>    </dsp:form>   When the user submits the form, the /samples/Person.name property is set to the value entered in the input field.Unlike standard HTML, which requires the name attribute for most input tags; the name attribute is optional for DSP form element tags. If an input tag omits the n...
11 comments
Read more

Search Facets - how to create a new search facets in ATG Search

A Facet is a search refinement element that corresponds to a property of a commerce item type. ATG supports the search result refinement using the Faceted Search concept. Read more about facted search @  http://en.wikipedia.org/wiki/Faceted_search . Facet can either be ranges or specific values. Each facet is stored in the RefinementRepository as a separate refineElement repository item. Facets are divided into Global and Local facets. Global facets apply to all the categories and local facets only to the category in which they are created. For example Price/Brand can be considered as the facets that are common for all skus and New Release/Coming Soon can be considered as the facets that are specific to Physical Media products like Vidoe/DVD/Blue-ray/Books. We can use the ATG BCC - Merchandising UI to create facets. The Faceting Property depends on the meta-properties defined in the \atg\commerce\search\product-catalog-output-config.xml ( the def...
4 comments
Read more

Eclipse plug-in to create Class and Sequence diagrams

ModelGoon is an Eclipse plug-in avaiable for UML diagram generation from Java code. It can be used to generate Package Dependencies Diagram, Class Diagram, Interaction Diagram and Sequence Diagram. You coud get it from http://marketplace.eclipse.org/content/modelgoon-uml4java Read more about it and see some vedios about how to create the class and sequence diagram @ http://www.modelgoon.org/?tag=eclipse-plugin Find some snapshots below which gives an idea about the diagram generation.
8 comments
Read more

ATG Search architectural flow : Search and Index

I would like to explain the high level ATG Search implementation architecture ( for an online store) through the above diagram. In this diagram 1.x denotes the search functionality and 2.x denotes the indexing functionality. I have given JBoss as the application server. Physical Boxes and Application Servers in the diagram ( as recommended by ATG )  : Estore ( Commerce ) Box --> The box with the estore/site ear (with the site JSPs and Java codes). Search Engine Box --> The box with the search engine application running. Indexing Engine Box --> The box with the indexing engine application running. CA (Content Administration) Box --> The box with the ATG CA ear ( where we could take CA -BCC - Search Administration and configure the search projects) . Search Indexer Box --> The box with the ATG Search Index ear ( to fetch the index data from repository). Note that the engine performing indexing will need access ...
7 comments
Read more