A XML document that defines a producer's fragments endpoints. This information will be added to the routing.xml file to autoregister the fragments. There are two types of producers: CPS producer and custom producer The portalPackage that these fragments will be added to during auto-registration. The default value is Connection. Portlets added to Connection will be visible to the user. Portlets added to Administration would not be visible to the user. The portalPackage must already exist in CM. Available since BlueSea. This root handle identifies the producer. This is an end point to a custom producer. The default end point for the CPS producer is /fragmentproducer A class that implementents the interface 'com.cognos.portal.fragment.autoregistration.IAutoRegistrationPlugin". This class will be called when the producer is regisrtered. There is also an option to call it when the producer is being updated. For a custom producer fragment, the name given to the resource. For CPS producer, it can be picked up from the fragment's implementation.xml. For a custom producer fragment, a textual description of the content of the resource. For CPS producer, the description is automatically picked up from the implementation.xml. For a custom producer fragment, supported modes (e.g. view, edit, cps:config). For CPS producer, it is picked up from the fragment's implementation.xml. For a custom producer fragment, supported window states (e.g. normal, maximized, minimized). For CPS producer, it is picked up from the fragment's implementation.xml. For a custom producer fragment, capabilities required to execute this fragment. For CPS producer, it is picked up from the fragment's implementation.xml. This handle is a unique identifier for the fragment within this producer. This is used by a CPS Producer. It is the path of the implementation.xml file starting from the /WEB-INF/fragments/producers directory. extraInfo is appended to the implementation url and is added to the routing url - example of an extraInfo: ?mode=admin&page=two. Note if you have several fragments using the same implementation file but with different extraInfo strings be sure to add a unique title to these fragments in this file in order to have unique portlet names. Available since BlueSea. The segment that will be appended to the producer's endpoint to create the physical endpoint. The custom values that will be used to initialize the fragment. The name assigned to this localized string for dereferencing into a ResourceList for values from other locales. When the resourceName is not supplied, there are no values for additional locales available in the ResourceList.