Catalog Maintanance Service

Hi There,
After a deployment from BCC to Staging/Production, I have to execute CMS manually to reflect the changes. Also if I am invoking it manually, it is not updating both of the data sources (CATA and CATB).
How to configure CMS to support switching data sources?
Is there any way to resolve this issue?
Thanks,
R.

Hi Rajeev,
You should have debugging on for DeploymentAgent too in order to debug this. And make sure you are on a more recent ATG version, like 9.2 or above or 10.x. I know there were a few bugs that could affect the running of CMS in ATG 2007.1 and some may have still been present in 9.0 and early versions of 9.1.
Beyond that, if you have custom item-descriptor names in the ProductCatalog (e.g. subtypes of the out-of-box types), then you need to configure them in the "extraTriggeringAffectedItemDescriptors" property on CatalogMaintenanceHelper.
Thanks.
Nick Glover
Oracle Support for ATG Products

Similar Messages

  • Plant maintanance service order creation using Sales order

    Hi,
    We have created plant maintanance service orders  using requiremnt class in sales . so in sales order schedule line the service order is created. but in some sales orders it will show the service order number and when we double click on that shows an error service order does not exist. please let us know what would be the problem.
    Thanks & regards,
    Rohit

    Hi ROHIT,
    First check do you have authorization for (IW32 , IW33) and Check your number ranges in OION and check is there any status is blocking  that number.
    Regards
    Nishad

  • Operations Manager 2012 Management Pack Catalog Web Service - Missing Management Packs

    I am using SCOM 2012 R2 with UR5 and I see things like Exchange 2013 and Lync 2013 in the catalog when doing an MP import, but some other items like: SQL Server 2012/2014 and SharePoint 2013 are missing. I can download them from the MS download site,
    but is this catalog web service being maintained? 

    Hi Darren, I know what you mean. It would be nice to be able to pull the latest management packs as well as management packs available from the download site from the catalog via the Operations Console, however, the packs in the catalog are not comprehensive. 
    I highly recommend the SCOM management pack wiki which is kept up to date by the community. I use this myself :) An added benefit to using this wiki over the catalog is that this links to the download page for the management pack of interest from where you
    can obtain the management pack and its documentation which often contains useful detail on what the management pack entails. The wiki link is below:
    http://social.technet.microsoft.com/wiki/contents/articles/16174.microsoft-management-packs.aspx
    If you've found this post helpful,  please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
    MrChiyo | My blog: Technical | Twitter: MrChiyo

  • How to create a sub head(code) in a catalog- for service notification

    Hi everyone,
    How to create a sub head(code) in a catalog- for service notification?
    Please guide with your valuable comments.
    Please guide its very urgent.
    Thanks and Regards
    Edited by: MPVash Vash on Oct 24, 2008 8:14 AM
    Edited by: MPVash Vash on Oct 30, 2008 7:38 AM

    Hi,
    Go to T-code QS41, give the catalog and code group and enter.
    U can click on the code after selecting the code group and create new  codes.
    In SPRO u should see which type of catalog is assigned to the notification type. This u can see in the overview of the notification type by selecting the notification type in SPRO.
    Regards
    Haricharan

  • SRM 7.0 Catalog (Web Service) Portal Links Not Working

    Hi,
    Following an upgrade to the latest Service Packs for SRM, we are encountering an issue with dead links to Catalogs (both Internal MDM and External).
    Prior to the upgrade the normal catalog (webservice) links, as defined in the SPRO (Supplier Relationship Management>>SRM>>Master Data>>Content Management>>Define External Webservices)  would open a new window to either our Internal MDM Catalog or an external punch-out catalog.
    After the upgrade these links are now "dead", no window opens and neither of the Catalogs open.
    We are on the following release levels:
    Patch set SP 06 patch 01(Build 7.1.04.124 ). SMP is SP07 Patch01 (Build 7.1.04.134)
    Help would be appreciated.
    Thanks and Regards,
    Mike

    Hi Jason,
    I am also facing the same concern. I have done all the below configurations
    1.) As per the SAP note 1643978, I have configured the Launch catalog in LPD_CUST
    2.) And the group access has also been assigned to the user as per the above note
    3.) In reference to the folder permissions on portal content, the access has been given according to the note - 1260119
    After doing all the changes, the external punch out catalog links are still dead. Could you please advise if there is any other activity which needs to be performed. Thanks in advance for your help.
    Best Regards,
    Bharathi

  • Oracle BPM Studio 10g R3 cataloging Web Services strips special characters

    Hi folks,
    I have a Web Service that I'd like to invoke from an activity in my process.
    When I catalog the WSDL, BPM Studio creates the associated External Resource just fine except for one small problem, namely all Simple Types that have 'special characters' in their enumerated String values are stripped clean.
    Example 1:
    ADSL1
    ADSL2
    ADSL2+
    --> The plus is stripped from ADSL2+, causing BPM Studio to flag two problems caused by duplicate 'ADSL' values
    Example 2:
    adsl1#foo/123
    --> Everything to the left of 123 is stripped leaving only '123' as a value
    In fact in the BPM Studio's Editor, the only special character that is allowed is the underscore. Everything else e.g. \ # etc etc cannot be keyed in.
    Has anyone come across this before? Thanks for reading :-)
    cheers
    jm

  • How to create a Catalog (Product/Service) & TAX issues

    SRM Guru's
    Product Ver: SRM 5.0 : ECC 6.0  ( No CCM or Service Master )
    TAX S/w: Vertex ( O )
    As of now:    We are planning to implement a vanilla SRM-ECC (in ext. classic). We are into Indirect procurement w/limit orders.
    Catalog:
    I want to create a Catalog ( UNSPSC or 1 level company catalog),
           1. Can this be created in ECC  (with out Products ) and replicated to SRM (EBP)
           2. How to go about creating it ?
           3. Can it be done with out CCM, if so how
           4. How to replicate it ? ( no CCM or middleware )
           5. Can i create it in EBP ? if so, plse say how..
    TAX:
    Vertex mentioned that, Tax codes will be mapped to services, in our case, since we don’t have Services except a free form text describing what service is provided ( eg: "Payroll Service" ), what can be done ?
    In a normal scenario, i can imagine having Service Master with all "Services", but in our situation, how can we use catalog to map to TAX codes. ?
    PS: If you could, please describe/break down the relationship between
       Catalog -- Category Id -- Product -- Services/Materials
    regards.,
    -Rupesh

    Hi
    <u>To create internal catalog there are three possibilities</u>
    1. CCM Catalog developed by SAP.
    2. SRM-MDM Catalog taken over by SAP.
    3. Requisite Catalog other catalog provider.
    <u>Check these links -></u>
    http://help.sap.com/saphelp_ccm20/helpdata/en/index.htm
    https://websmp101.sap-ag.de/ibc-srm here check SRM-MDM Catalog.
    http://www.requisite.com/solutions/index.cfm?pageID=productpac_bugseye
    Re: Catalog Mgmt
    <b>Other related links -></b>
    <u>Create Internal Catalog</u>
    Re: Create Internal Catalog
    CCM Create catalog link
    Re: creating a catalog
    Catalog ID does not exist
    Re: SRM Contract Catalog - Creation
    CCM SRM product catalog
    Re: Product Catalog to CCM
    <u>Managing Catalog content in SRM</u>
    http://help.sap.com/saphelp_srm50/helpdata/en/0a/f9353e39011a38e10000000a114084/frameset.htm
    http://help.sap.com/saphelp_srm50/helpdata/en/ba/7a50415e216e24e10000000a155106/frameset.htm
    <b>P.S: All tables for CCM (Catalog tables and CCM) start with "/CCM/" ,so you can search on that using SE11 transaction.</b>
    <u>MDM-SRM Catalog</u>
    Re: MDM SRM - Catalog - External Catalog - Punchout
    <u>Punchout catalog</u>
    Punchout catalog
    <u>Loading Product Data into Catalog using CSV files</u>
    Loading Product Data into Catalog using CSV2.0 file
    <u>Contract catalog</u>
    Re: Contract catalog
    Hope this will definitely help. Do let me know.
    Regards
    - Atul

  • Punchout Catalog - "No Service Name Specified"

    I'm trying to create an OCI connection for a punch-out catalog and run into an error every time I try to bring the items back to my SRM server from the supplier's website.
    The error says...
    No Service Name Specified
    Your request did not contain a service name. Please provide a service name as part of the URL.
    Example URL:
    http://.../scripts/wgate/CreateSO/!
    or...
    Session Already Terminated
    There is currently no session running that might accept this request.
    This situation usually occurs if your session has been closed by the Internet Transaction Server and you tried to navigate to a previously requested page by selecting BACK in your browser. To proceed you must first restart the session as described above. 
    © 1996-2005, SAP AG 
    Does anyone know what service name it's referring to? Or what's the cause of this error?
    Thanks.
    SN

    http://www.groupe-rg-webshop.com/steelcase?sap-client=310&sap-user=steelconnect&sap-password=safety     URL
    shop / client     310     Fixed Value
    USERNAME     steelconnect     Fixed Value
    PASSWORD     safety     Fixed Value
    SRC     SAP     Fixed Value
    ACTION     Anmelden     Fixed Value
    LANGUAGE     FR     Fixed Value
    HOOK_URL                                                                                Return URL
    ~OkCode     ADDI     Fixed Value
    ~Target     _top     Fixed Value
    ~caller     CTLG     Fixed Value
    Sorry that I cannot format it to make it easier to read/follow, but each line (except the first line) has a paramter NAME, followed by parameter Value and Type.
    Thanks.
    SN

  • New item-descriptor and ATG needed changes

    Hello there,
    I was facing the same problem that related on this thread (Catalog Maintanance Service and I solved it adding my custom sku on CMS.
    My question is, Is there other components that I must edit adding my custom sku item-descriptor?
    Or, is there a doc that shows what components must be updated when creating a new item-descriptor?
    Thanks.

    I don't think you will found consolidated configuration required when adding a new item. It's scattered in different Oracle manuals, like Repository configurations can be found in Repository guide, CMS configurations can be found in Commerce programming guide, Search related configuration can be found in Search Admin guide, if you wan to customize how your new item will be displayed in BCC the information can be found in BCC admin guide.

  • What triggers CMS in ATGProduction and ATGStaging?

    I have been troubleshooting a problem that had our ATGProduction cluster misconfigured such that CatalogMaintenanceHelper was not active=true on any server in the cluster. Correcting the problem was easy enough, but now I am left trying to figure out how to test the fix. I was under the impression that, at the end of each BCC Project deployment from ATGPublishing, CMS would run on one of the machines in the target cluster. This doesn't seem to be the case (or I'm not looking in the right place). How do I confirm that my fix is working and CMS is running correctly in ATGStage and ATGProduction?
    As always, any help or insights are greatly appreciated.
    Edited by: robertkuhar on Apr 18, 2012 12:20 PM

    Check this thread:
    Catalog Maintanance Service
    Check this component in dyn/admin /atg/epub/DeploymentAgent/?propertyName=deploymentEventListeners
    There should be CatalogMaintenanceHelper listener configured which triggers the CMS.

  • Adding a Service to CAF Tile

    I've followed the steps in the docs and even looked at the StockData example provided but cannot seem to get it working. I get the following error:
    Before resolve: http://localhost:4502/content/mosaic/catalogs/Historian/tiles/SnapshotTile/SnapshotTile.sw f
    Before resolve: http://localhost:4502/content/mosaic/catalogs/Historian/services/HistorianService/theHisto rianService.gxml
    Created url: http://localhost:4502/content/mosaic/catalogs/Historian/interfaces/HistorianInterfaceLibra ry/HistorianInterfaceLibrary.swf
    Before resolve: http://localhost:4502/content/mosaic/catalogs/Historian/tiles/SnapshotTile/SnapshotTile.sw f
    Before resolve: http://localhost:4502/content/mosaic/catalogs/Historian/tiles/SnapshotTile/SnapshotTile.sw f
    [SWF] /content/mosaic/catalogs/Historian/interfaces/HistorianInterfaceLibrary/HistorianInterfac eLibrary.swf - 2,497 bytes after decompression
    Failure in Loader: Error: Error #2036: Load Never Completed. URL: http://localhost:4502/Historian/interfaces/HistorianInterfaceLibrary/HistorianInterfaceLib rary.swf
    Failure in Loader: Error: Error #2036: Load Never Completed. URL: http://localhost:4502/Historian/interfaces/HistorianInterfaceLibrary/HistorianInterfaceLib rary.swf
    Below is the code as well as the configuration files:
    IHistorianService.as
    package cafe.historian.services
              import mx.collections.IList;
              [Expose]
              public interface IHistorianService
                        function getSnapshots(userid:String):IList;
    HistorianService.as
    package cafe.historian.services.impl
              import cafe.historian.services.IHistorianService;
              import mx.collections.ArrayCollection;
              import mx.collections.IList;
              [Expose(catalog="Historian", library="HistorianInterfaceLibrary", scope="singleton")]
              public class HistorianService implements IHistorianService
                        public function HistorianService()
                        public function getSnapshots(userid:String):IList{
                                  var test:ArrayCollection = new ArrayCollection();
                                  test.addItem("one");
                                  test.addItem("two");
                                  return test;
    Historian.axml
    <?xml version="1.0" encoding="UTF-8" standalone="no"?>
    <!-- Copyright 2011 Adobe Systems Incorporated. All rights reserved. The original
    version of this material may be obtained from Adobe Systems Incorporated. -->
    <app:Application xmlns:app="http://ns.adobe.com/Mosaic/Application/1.0/" xmlns:catalog="http://ns.adobe.com/Mosaic/Catalog/1.0/" xmlns:ct="http://ns.adobe.com/Mosaic/CommonTypes/1.0/" xmlns:tile="http://ns.adobe.com/Mosaic/Tile/1.0/" xmlns:view="http://ns.adobe.com/Mosaic/View/1.0/" label="EMS Historian" name="Historian">
        <ct:Metadata>
            <ct:Description/>
        </ct:Metadata>
        <!-- Specifies a default panel or view to use when a user adds a new panel or
        view to the composite application (if permitted). Specify a default directly,
        or reference one from a composite application catalog. Referenced default
        panels and views override the composite application defaults. Note: You can
        specify only one panel and view in the app:Defaults section, but you can
        specify any number of catalog:CatalogReference children. -->
        <app:Defaults>
            <view:Panels>
                <view:Panel allowContentDelete="true" height="100%" label="Default Panel" tileChrome="full" width="100%">
                    <view:Layout name="HorizontalLayout" numColumns="2"/>
                </view:Panel>
            </view:Panels>
        </app:Defaults>
        <!-- Provide a global context containing values for use across entire
        application.
        <ct:Context>
            <ct:Data key="myApplicationContext" type="string" value="default value" />
        </ct:Context>
        -->
        <!-- A named context is useful for partition of a set of context values
        to a subsection of the application.
        <app:NamedContexts>
            <ct:Context name="basictypes">
                <ct:Data key="aSimpleString" type="string" value="sample string"/>
                <ct:Data key="aBoolean" type="boolean" value="true"/>
                <ct:Data key="anInteger" type="number" value="2011"/>
                <ct:Data key="aDate" type="date" value="2011-11-01T19:00:00-05:00"/>
                <ct:Data key="aNull" type="null" />
            </ct:Context>
        </app:NamedContexts>
        -->
        <!-- Specifies the runtime content for a composite application. The order of
        the elements affects the appearance in the application user interface. You
        can specify only one app:Shell or app:ShellReference element as a child of
        app:Application. -->
        <app:Shell label="Sample Shell" name="SampleShell"><!-- ShellStyle -->
            <!-- Specifies a reference to a composite application catalog. Catalogs
            contain composite application assets. The name attribute creates a
            shorthand reference to the catalog, which is stored on the Experience
            Server. -->
            <catalog:CatalogReference name="${catalog}" uri="${catalog}"/>
            <!-- Specifies a container to display views in the application user
            interface. The order of elements affects the appearance of the user
            interface. You can include only one view:ViewManager element as a child
            of the app:Shell element. The default skin for the view:ViewManager
            element provides a set of tab buttons to switch between views in the
            application, as well as an Add button, and an option menu. -->
            <view:ViewManager height="100%" width="100%">
                <view:View name="Research"
                                              height="100%" width="100%"
                                              label="Research"
                                              allowContentDelete="false">
                    <view:Panel allowContentDelete="false"
                                                  label="Analysis"
                                                  height="100%" width="100%"
                                                  styleName="PanelInShellStyle" ><!-- FullPanelTileStyle -->
                     <view:Layout name="HorizontalLayout"/> 
                        <tile:TileReference catalog="${catalog}"
                                      name="ResearchTile" optional="false" width="100%" height="100%" /><!-- TileStyle -->
                    </view:Panel>
                </view:View>
                <view:View label="Snapshots" height="100%" width="100%">
                          <view:Panel allowContentDelete="false"
                                                  label="Snapshots"
                                                  height="100%" width="100%"
                                                  styleName="PanelInShellStyle" >
                     <view:Layout name="HorizontalLayout"/> 
                     <tile:TileReference catalog="${catalog}"
                            name="SnapshotTile" optional="false" width="100%" height="100%">
                            <tile:Properties>
                                      <tile:Property name="historianService">
                                                <tile:ServiceReference catalog="${catalog}" library="HistorianService" name="theHistorianService"></tile:ServiceReference>
                                      </tile:Property>
                            </tile:Properties>
                     </tile:TileReference>
                          </view:Panel>
                </view:View>
                <view:View label="Views" height="100%" width="100%">
                          <view:Panel allowContentDelete="false"
                                                  label="Views"
                                                  height="100%" width="100%"
                                                  styleName="PanelInShellStyle" >
                     <view:Layout name="HorizontalLayout"/> 
                     <tile:TileReference catalog="${catalog}"
                            name="ViewsTile" optional="false" width="100%" height="100%"/>
                          </view:Panel>
                </view:View>
                <view:View label="Reports" height="100%" width="100%">
                          <view:Panel allowContentDelete="false"
                                                  label="Reports"
                                                  height="100%" width="100%"
                                                  styleName="PanelInShellStyle" >
                     <view:Layout name="HorizontalLayout"/> 
                     <tile:TileReference catalog="${catalog}"
                            name="ReportsTile" optional="false" width="100%" height="100%"/>
                          </view:Panel>
                </view:View>
                <view:View label="Admin" height="100%" width="100%">
                          <view:Panel allowContentDelete="false"
                                                  label="Admin"
                                                  height="100%" width="100%"
                                                  styleName="PanelInShellStyle" >
                     <view:Layout name="HorizontalLayout"/> 
                     <tile:TileReference catalog="${catalog}"
                            name="AdminTile" optional="false" width="100%" height="100%"/>
                          </view:Panel>
                </view:View>
            </view:ViewManager>
        </app:Shell>
    </app:Application>
    Historian.cxml
    <?xml version="1.0" encoding="UTF-8" standalone="no"?>
    <catalog:Catalog xmlns:catalog="http://ns.adobe.com/Mosaic/Catalog/1.0/" xmlns:ct="http://ns.adobe.com/Mosaic/CommonTypes/1.0/" xmlns:tile="http://ns.adobe.com/Mosaic/Tile/1.0/" xmlns:view="http://ns.adobe.com/Mosaic/View/1.0/" label="EMS Historian" name="Historian">
        <!-- Identifying description for this catalog. -->
        <ct:Metadata>
            <ct:Description>All content for the EMS Historian</ct:Description>
        </ct:Metadata>
        <!-- Specifies a list of tiles (tile:TileClass elements) contained within
        this catalog.  -->
        <tile:TileClassList>
                <!--  Remove the commenting from this tile:TileClass element to
                include a reference to a tile in this catalog. Within a tile:TileClass
                element, a tile:Content child element specifies tile content using the
                following attributes:
                    uri: A reference, either to absolute or relative, to the content's
                    location on a server.
                    contentType: The MIME type for the tile's content. For Flex tiles,
                    specify "application/x-shockwave-flash", and for HTML tiles
                    specify "text/html".
                    loadAs: For Flex tiles, if this value is "module", at run time the
                    tile loads as a Flex module. If the value is "default" or omitted,
                    at runtime the Flex tile loads as a SWF application. 
                    IMPORTANT: You must compile module tiles using one of the Flex SDKs
                    included in the Adobe Experience Services Tooling for Flash Builder
                    installation. Flex modules are similar to Flash Runtime Shared
                    Libraries (RSLs) in that they separate code from an application
                    into separately loaded SWFs. For more information on modular
                    applications, see "Modular applications overview" in the Flex
                    Developer's Guide.
            <tile:TileClass
                name="SampleTile"
                label="Sample Tile"
                width="600" height="400"
                fitContent="true">
                <ct:Metadata>
                    <ct:Description>sample description</ct:Description>
                </ct:Metadata>
                <tile:Content
                    uri="${catalogURL}/tiles/SampleTile/SampleTile.swf"
                    contentType="application/x-shockwave-flash"
                    loadAs="default" />
            </tile:TileClass>
            -->
                        <tile:TileClass fitContent="true" height="100%" label="ResearchTile" loadPolicy="auto" name="ResearchTile" width="100%">
                <ct:Metadata>
                    <ct:Description/>
                </ct:Metadata>
                                  <tile:Content contentType="application/x-shockwave-flash" loadAs="default" uri="${catalogURL}/tiles/ResearchTile/ResearchTile.swf"/>
                        </tile:TileClass>
                        <tile:TileClass fitContent="true" height="300" label="ViewsTile" loadPolicy="auto" name="ViewsTile" width="600">
                <ct:Metadata>
                    <ct:Description/>
                </ct:Metadata>
                                  <tile:Content contentType="application/x-shockwave-flash" loadAs="default" uri="${catalogURL}/tiles/ViewsTile/ViewsTile.swf"/>
                        </tile:TileClass>
                        <tile:TileClass fitContent="true" height="300" label="SnapshotTile" loadPolicy="auto" name="SnapshotTile" width="600">
                <ct:Metadata>
                    <ct:Description/>
                </ct:Metadata>
                <tile:Depends>
                          <tile:Interface interfaceName="cafe.historian.services.IHistorianService" library="HistorianInterfaceLibrary"/>
                </tile:Depends>
                <tile:Properties>
                          <tile:Property name="historianService" type="cafe.historian.services.IHistorianService"/>
                </tile:Properties>
                                  <tile:Content contentType="application/x-shockwave-flash" loadAs="default" uri="${catalogURL}/tiles/SnapshotTile/SnapshotTile.swf"/>
                        </tile:TileClass>
                        <tile:TileClass fitContent="true" height="300" label="ReportsTile" loadPolicy="auto" name="ReportsTile" width="600">
                <ct:Metadata>
                    <ct:Description/>
                </ct:Metadata>
                                  <tile:Content contentType="application/x-shockwave-flash" loadAs="default" uri="${catalogURL}/tiles/ReportsTile/ReportsTile.swf"/>
                        </tile:TileClass>
                        <tile:TileClass fitContent="true" height="300" label="cafe.historian.tiles.admin.AdminTile" loadPolicy="auto" name="AdminTile" width="600">
                <ct:Metadata>
                    <ct:Description/>
                </ct:Metadata>
                                  <tile:Content contentType="application/x-shockwave-flash" loadAs="default" uri="${catalogURL}/tiles/AdminTile/AdminTile.swf"/>
                        </tile:TileClass>
              </tile:TileClassList>   
        <!-- Specifies a list of interface libraries (tile:InterfaceLibrary elements)
        contained within this catalog -->
        <tile:InterfaceLibraryList>
            <!--  Remove the commenting from this tile:InterfaceLibrary element to
            include a reference to an interface library in this catalog. Within a
            tile:InterfaceLibrary element, a tile:InterfaceList child element
            specifies a list of interfaces (tile:Interface elements) to include
            in the catalog. For each tile:Interface element, specify the interface
            class using the following attribute:
                interfaceName: A fully-qualified package and class reference to class
                that defines a service interface.
            <tile:InterfaceLibrary name="SampleInterfaceLibrary">
                <ct:Metadata>
                    <ct:Description/>
                </ct:Metadata>
                 <tile:InterfaceList>                 
                    <tile:Interface interfaceName="com.adobe.adep.samples.services.sampleservice.ISampleService"/>                
                 </tile:InterfaceList>
             </tile:InterfaceLibrary>
             -->        
                   <tile:InterfaceLibrary name="HistorianInterfaceLibrary">
                <ct:Metadata>
                    <ct:Description/>
                </ct:Metadata>
                      <tile:InterfaceList>
                    <tile:Interface interfaceName="cafe.historian.services.IHistorianService"/>
                </tile:InterfaceList>
            </tile:InterfaceLibrary>
        </tile:InterfaceLibraryList>   
        <!-- Specifies a list of service libraries (tile:ServiceLibrary elements)
        contained within this catalog. -->
         <tile:ServiceLibraryList>
              <!--  Remove the commenting from this tile:ServiceLibrary element to
              include a reference to a service library in this catalog. Within a
              tile:ServiceLibrary element, a tile:ServiceClassList child element
              specifies a list of service classes (tile:SeviceClass elements) to
              include in the catalog. For each tile:ServiceClass element, specify a
              service using the following attributes of the tile:Content child
              element:
                  uri: A reference, either to absolute or relative, to the content's
                  location on a server.
                  contentType: The MIME type for the tile's content. For service
                  libraries specify "application/xml".
              <tile:ServiceLibrary name="SampleService">
                <ct:Metadata>
                    <ct:Description/>
                 </ct:Metadata>
                 <tile:ServiceClassList>                
                    <tile:ServiceClass name="SampleService">
                        <tile:Content
                        uri="${catalogURL}/services/SampleService/SampleService-com-adobe-adep-samples-services-s ampleservice-impl.gxml"
                        contentType="application/xml"/>
                    </tile:ServiceClass>               
                 </tile:ServiceClassList>            
             </tile:ServiceLibrary>        
             -->
                        <tile:ServiceLibrary name="HistorianService">
                <ct:Metadata>
                    <ct:Description/>
                </ct:Metadata>
                      <tile:ServiceClassList>
                    <tile:ServiceClass className="cafe.historian.services.impl.HistorianService" name="theHistorianService" scope="singleton">
                    <tile:Implements>
                              <tile:Interface interfaceName="cafe.historian.services.IHistorianService" library="HistorianInterfaceLibrary"/>
                    </tile:Implements>
                    <tile:Content contentType="application/xml" uri="${catalogURL}/services/HistorianService/theHistorianService.gxml"/>
                    </tile:ServiceClass>
                          <tile:ServiceClass name="HistorianService">
                        <tile:Content contentType="application/xml" uri="${catalogURL}/services/HistorianService/HistorianService-cafe-historian-services-imp l.gxml"/>
                    </tile:ServiceClass>
                </tile:ServiceClassList>
            </tile:ServiceLibrary>
        </tile:ServiceLibraryList>
        <!-- Specifies a list of style sheets (view:StylesheetClass elements) contained
        within this catalog -->
        <view:StylesheetClassList>
            <!--  Remove the commenting from this view:StylesheetClass element to
            include a style sheet reference in this catalog. Include a separate
            view:StylesheetClass element for each style sheet you include in the
            catalog. Within each view:StylesheetClass element, specify the style sheet
            content using the following attributes of the view:Content child element:
                uri: A reference, either to absolute or relative, to the content's
                location on a server.
                contentType: The MIME type for the style sheet content. For Flex
                tiles, specify "application/x-shockwave-flash", and for HTML tiles
                specify "text/css".
            <view:StylesheetClass name="CafeMosaicTheme">
                <ct:Metadata>
                    <ct:Description>An alternative way to navigate using a ComboBox.</ct:Description>
                </ct:Metadata>
                <view:Content contentType="application/x-shockwave-flash" uri="${catalogURL}/stylesheets/CafeMosaicTheme/CafeMosaicTheme.swf"/>
            </view:StylesheetClass>
           -->
        </view:StylesheetClassList>   
        <!-- Specifies a list of panels (view:PanelClass elements) contained within
        this catalog -->
        <view:PanelClassList>
            <!--  Remove the commenting from this view:PanelClass element to include
            a reference to a panel in this catalog. Include a separate view:PanelClass
            element for each panel you include in the catalog. Within a view:PanelClass
            element, a view:Content child element specifies information for a panel
            using a view:Panel child element. For each view:Panel child element,
            specify the panel information using the following attributes:
                name: A unique name for the panel used to reference it from within the
                catalog.
                label: Descriptive text that displays as the panel title in the user
                interface of the composite application.
                tileChrome: Sets the default user interface for the panel. Values may
                be "none", "title" or "full". If the value is "full", then there is
                chrome on the panel which displays the title (label) and allows the
                panel to be moved, potentially deleted (if permitted), and resized.
                If the value is "title", the chrome is the same as for "full" without
                the ability to resize. If the value is "none", then there is no
                chrome on the panel, which means no title (label), and no user
                interface for for manipulating the panel.
                allowContentDelete: Specifies whether users can delete this panel at
                run time when the "chrome" attribute is set to "full" or "title".
                Values may be "true" or "false".
            Each view:Panel element may contain one or more tile:TileReference child
            elements that specify tiles to display within the panel at run time. You
            can override default tile attribute values here to customize the tile's
            appearance when referenced within this panel:
                catalog: Reference to the catalog that contains the tile.
                name: The name of the tile specified in the catalog.
                label: (override) The label of the tile.
                chrome: (override) Sets the user interface for the tile. Values may
                be "none", "title" or "full". If the value is "full", then there is
                chrome on the tile, which displays the title (label) of panels
                contained within the tile, and the tile allows for the panel to be
                moved, potentially deleted (if permitted), and resized. If the value
                is "title", the chrome is the same as for "full" without the ability
                to resize. If the value is "none", then there is no chrome on the
                tile, which means no panel title (label), and no user interface for
                for manipulating the panel.
                fitContent: (override) Specifies whether tile content should be
                automatically resize to fit the container. Values may be "true" or
                "false".
            <view:PanelClass name="SamplePanel">
                <ct:Metadata>
                    <ct:Description />
                </ct:Metadata>
                <view:Content>           
                    <view:Panel name="SamplePanel" label="Sample Panel"
                        tileChrome="true" allowContentDelete="true" width="100%" height="100%">
                        <view:Layout name="HorizontalLayout" />
                        <tile:TileReference
                            catalog="${catalog}" name="SampleTile" label="Sample Tile" width="100%" height="50%"
                            chrome="full" fitContent="true"/>
                    </view:Panel>
                </view:Content>
            </view:PanelClass>
            -->
        </view:PanelClassList> 
        <!-- Specifies a list of views contained within this catalog -->
        <view:ViewClassList>
            <!--  Remove the commenting from this view:ViewClass element to include a
            reference to a view in this catalog.
            Include a separate view:ViewClass element for each view you include in the
            catalog. Within a view:ViewClass element, a view:Content child element
            specifies information for a panel using a view:View child element. For
            each view:View child element, specify the panel information using the
            following attributes:
                name: A unique name for the view used to reference it from within
                the catalog.
                label: Descriptive text that displays as the panel title in the
                user interface of the composite application.
            Each view:View element may contain one or more view:PanelReference child
            elements that specify panels to display within the view at run time. You
            can override default panel attribute values here to customize the panel's
            appearance when referenced within this view:
                catalog: Reference to the catalog that contains the panel.
                name: The name of the panel specified in the catalog.
            <view:ViewClass label="Sample View" name="SampleView">
                <ct:Metadata>
                    <ct:Description>Sample View</ct:Description>
                </ct:Metadata>
                <view:Content>
                    <view:View name="SampleView" width="100%" height="100%"
                        label="Sample View">
                        <catalog:CatalogReference name="Default"
                            uri="Default" />
                        <view:PanelReference catalog="Default" name="SamplePanel" />
                    </view:View>
                </view:Content>
            </view:ViewClass>
            -->
        </view:ViewClassList>
    </catalog:Catalog>
    SnapshotTile.mxml (snippet)
    private var watcher:ChangeWatcher;
    [Bindable]
    [Consume(catalog="Historian", library="HistorianInterfaceLibrary")]
    public var historianService:IHistorianService;
    protected function _preinitializeHandler(event:FlexEvent):void
              this.addEventListener( AnnotationParseEvent.COMPLETE, _annotationParseEventCompleteHandler );
              watcher = ChangeWatcher.watch(this, "historianService", onGotService, false, true);
              protected function onGotService(e:PropertyChangeEvent):void
              if(historianService)
                        var test:ArrayCollection = historianService.getSnapshots("jonphill") as ArrayCollection;
                        trace("Using service, item 1: " + test.getItemAt(0));
                        trace("Using service, item 2: " + test.getItemAt(1));
    I've also attached two screenshots showing the project structure in FB and CRX.
    Any help here would be great as I'm pulling my hair out at this point!
    Thanks

    There's not an actual space in the error, it just looks that way when I pasted the text into the post.
    For some additional information, I've tried going through the tutorial here (http://www.youtube.com/ADEPDevelopers#p/c/DF68F4464D4EF4E0/4/klNspQvfVMc) and here (http://help.adobe.com/en_US/enterpriseplatform/10.0/AEPDeveloperGuide/WS989a722fbb254cbe-6 f13dcd01304cbb1ac4-8000.html), however, neither one goes through the full steps of adding the Service to the axml and cxml files which is where I'm probably having trouble.
    I've also looked at the StockMosaicService sample included with ADEP and tried mimicking it but with no luck. I had expected the ADEP tooling in Flash Builder to handle all this for me but it doesn't appear to be working properly now.

  • Use of Open Catalog Interface (OCI) in ERP

    Dear colleagues,
    I am not sure if this is the right forum to post this question but can we use Open Catalog Interface (OCI) without having SRM directly in ECC 6.0? If yes what are the prerequisites, customizing, licensing etc.
    What we are planning is end users will select material(s) he/she wants to procure from a catalog from a portal (not an SAP portal) and once this is done purchase requisition will be created in ERP system.
    Regards
    Melih

    ECC6.0 MM does support OCI.  This works on both the Purchase Req and PO.  You can punchout from MM and shop from an OCI compliant source such as MDM, supplier hosted, other catalog tools and then this informaiton is pulled back into the Purchase Req or PO.  OCI is delivered with ECC6.0 MM so there should not be any license issues.
    Configuration is part of the catalog web service set up and this is where you maintain information such as URL, user id, password, etc.

  • Application Web Service Control Manager detected AWEBSVC is not responding to HTTP requests. The http status code and text is 400, Bad Request.

    Hi All,
    I am seeing the following error for SMS_AWEBSVC_CONTROL_MANAGER component with Message ID: 8100
    Application Web Service Control Manager detected AWEBSVC is not responding to HTTP requests.  The http status code and text is 400, Bad Request.
    awebsctl.log file has below errors:
    Call to HttpSendRequestSync failed for port 80 with status code 400, text: Bad Request
    SMS_AWEBSVC_CONTROL_MANAGER 12/22/2014 3:37:55 PM
    13920 (0x3660)
    AWEBSVCs http check returned hr=0, bFailed=1
    SMS_AWEBSVC_CONTROL_MANAGER 12/22/2014 3:37:55 PM
    13920 (0x3660)
    AWEBSVC's previous status was 1 (0 = Online, 1 = Failed, 4 = Undefined)
    SMS_AWEBSVC_CONTROL_MANAGER 12/22/2014 3:37:55 PM
    13920 (0x3660)
    Health check request failed, status code is 400, 'Bad Request'.
    SMS_AWEBSVC_CONTROL_MANAGER 12/22/2014 3:37:55 PM
    13920 (0x3660)
    Management point and Application Catalog Website Point are installed on the same Server where I am seeing the error for Application Catalog Web Service Point role. Management Point and Application Catalog Website Point are functioning properly. Application
    Catalog Website is working.
    Thanks & Regards, Kedar

    Hi Jason,
    Application Catalog Web Service Point and Application Catalog Website Point; both are installed as per below configuration on same Server:
    IIS Website: Default Web Site
    Port Number: 80
    with default value for Web Application Name configured.
    For SMS_AWEBSVC_CONTROL_MANAGER component, I am getting below error in Component Status:
    Application Web Service Control Manager detected AWEBSVC is not responding to HTTP requests.  The http status code and text is 400, Bad Request.
    Possible cause: Internet Information Services (IIS) isn't configured to listen on the ports over which AWEBSVC is configured to communicate. 
    Solution: Verify that the designated Web Site is configured to use the same ports which AWEBSVC is configured to use.
    Possible cause: The designated Web Site is disabled in IIS. 
    Solution: Verify that the designated Web Site is enabled, and functioning properly.
    For more information, refer to Microsoft Knowledge Base.
    And awebsctl.log has the below error lines:
    Call to HttpSendRequestSync failed for port 80 with status code 400, text: Bad Request
    SMS_AWEBSVC_CONTROL_MANAGER
    12/23/2014 11:04:36 AM 16388 (0x4004)
    AWEBSVCs http check returned hr=0, bFailed=1
    SMS_AWEBSVC_CONTROL_MANAGER
    12/23/2014 11:04:36 AM 16388 (0x4004)
    AWEBSVC's previous status was 1 (0 = Online, 1 = Failed, 4 = Undefined)
    SMS_AWEBSVC_CONTROL_MANAGER
    12/23/2014 11:04:36 AM 16388 (0x4004)
    Health check request failed, status code is 400, 'Bad Request'.
    SMS_AWEBSVC_CONTROL_MANAGER
    12/23/2014 11:04:36 AM 16388 (0x4004)
    STATMSG: ID=8100
    What should I check from IIS side?
    Application Catalog Website is functioning properly.
    Thanks & regards,
    Kedar
    Thanks & Regards, Kedar

  • Logic in case of Service PO

    Hello Team,
    We have a service PO with account assignment category as K, Item category D, Material  - blank and only short text, PO document type is normal.
    At item level we have two tabs service and limits. Under service tab we enter service number and under limits tab we enter expected value as 1000 ( this field is ESUH - SUMLIMIT.
    Now we want to have logic in one of our report to fetch the value for SUMLIMIT from table ESUH. I got the logic to fetch the value. In table ESUH we have PACKNO as key field. We have PACKNO field in table EKPO too which can be read for PO number and item number.
    I would like to know how the field PACKNO in table EKPO is getting updated and it's linkage with table ESUH> I tried to check from my side but not found the logic for the same yet.
    Regards,
    Deepak Gupta

    Hi
    check this table also
    ESLB Service Type Header of Standard Service Catalog
    ESLH Service Package Header Data
    ESLP Service Item
    ESLL Lines of Service Package
    i thing this only link between  purchase table like Po table  and service PO table
    so we can link service po logic for service Po
    Regards
    kailas ugale

  • FMCN - Open Item upload Commitment not updated in case of Service Entry

    Hi All,
    I am trying to use FMCN to update commitment and fund centers in open PO's and GR's, however where there is material PO's it updating perfectly but if there is Service PO then it is not updating in GR/IR account with non budgeted commitment Item.
    Here in this client what they have done whenever they create the service entry sheet same time GR (MIGO) entry will get generated and then user can do the MIRO for the same.
    Please help me to update the same with Non Budgeted commitment.
    Regards,
    Alok

    Hi
    check this table also
    ESLB Service Type Header of Standard Service Catalog
    ESLH Service Package Header Data
    ESLP Service Item
    ESLL Lines of Service Package
    i thing this only link between  purchase table like Po table  and service PO table
    so we can link service po logic for service Po
    Regards
    kailas ugale

Maybe you are looking for

  • Lightening cable doesn't work won't charge or connect to iTunes !

    The new itouch 5th gen lightening cable won't connect to my iTunes account because my MacOs  computer says the USB is drawing too much power, help please? I have tried it in my husbands computer and the same thing happens, it also won't charge proper

  • Worries about adding Essentials Roles to 2012 STD

    Hello!<o:p></o:p> This is my first real? Here so I would like to just say, with all that I have read, learned from this forum it has been a big help in the past, I’m sure it will continue to be in the future, with that said.<o:p></o:p> When I first s

  • Saving 3 sets of data in 3 seperate arraylist and passing them to next view

    Hai all, I am using tree.The user  has selected the required products in level 3 of tree.Iam getting all the parents of selected product.In order to save them in database i need to send them to next view.how to store all the 3 levels in seperate arra

  • Can you air drop to a desktop

    I have an HP desktop in my classroom. I do most of my work on my mac, I have files I would like to send to my desktop. Is this possible?

  • Disabling fields in table Maintenance generator

    Hi Experts, I would like to restrict some fields in table maintenance generator dynamically/ statically. Here is the situation. I have generated table maintenance for the table ZMARA and I have created three transactions for the above single table ma