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

Basic design decisions for a commerce search setup ( with an ATG Search view)

In this blog I would like to explain the basic set of configuration/design decisions needed to setup an ATG search project. Most of these design decisions are common for all Enterprise search applications. 1. Decide the searchable properties :   This means the properties that the business want the user to search in the ecommerce platform. In ATG search these are configured as the text properties in the product-catalog-output-config.xml ( the definitionFile of the \atg\commerce\search\ProductCatalogOutputConfig). Usually the displayName of product/sku, displayName of department/category/sub-category, skuId, brandName are the properties configured as searchable. 2. Decide the search refinement properties or the faceted properties :   After a user search for a keyword, search refinement is the next step done to filter his results. ATG supports the search refinement using the Faceted Search concept. Read more about facted search @...
6 comments
Read more

ATG Search - how to define the search configuration rules

ATG Search configuration rules are specified through the ATG BCC Merchandising UI. Over here you could specify the below set of rules Redirection rules --> If you want to redirect to another page other than the search result page for a search keyword Property Prioritization rules  --> Prioritize certain set of properties and give weightage Result exclusion rules  --> Exclude certain search results Result positioning rules  --> Position / Sort the search result data 1.  To create the search configuration tree, you need to log-in to the ATG BCC Merchandising UI and select the Search Configuration Tree in the Browse tab drop down. Now need to click the Create button and first you need to create the Search Configuration Folder. 2.  When you create the folder, give the name of the folder and select whether the contents vary by Language or Segment. If your ecommerce site need to support more than one language and y...
6 comments
Read more

ATG Search Indexing - behind the scene steps explained

Read more about the search indexing @  http://tips4ufromsony.blogspot.com/2011/11/atg-search-architectural-flow-search.html ATG search indexing involves index file creation, deploying and copying the index file to the search engine's box. The steps can be divided into Initial stage, Preparing Content, Indexing and Deploying. Please find below the detailed analysis of each step. 1. Initial stage:        a. Check whether the folder deployshare configured correctly @ LaunchingService.deployShare  ( \atg\search\routing\LaunchingService.deployShare ). Lets assume that it is configured to \Search2007.1\SearchEngine\i686-win32-vc71\buildedIndexFiles.        b. Lets assume that the index file folder ( \Search2007.1\SearchEngine\i686-win32-vc71\indexFiles)  has the following segments (folders) currently :                     66900...
7 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