Solved: How to deliver layout settings with par

Hi,

I've developed a Repository Manager and packaged it into a par.

In the RM I added some new UICommands and properties. That's, after deploying the par, the user needs map the new UICommands in KM-CM-User Interface, map new properties in KM-CM-Global Services, and add the commands to a layout, and finally set the layout to the repository.

Is there any way to deliver these settings along with the par, so that users can use the new commands immediately after deploying the par?

Thanks,

Ray

SAP Managed Tags:
PORTAL Knowledge Management and Collaboration

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (1)

Need help~~~ I have tried to export a layout set and then import it, but always fail... and still I have to map commands and properties manually.

I think there should be ways to ship the configuration information with the par.... Anybody knows how?

Thanks,

Ray

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Ray,

you can download the sample implementation from the SDN Guide <a href="https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/31fa0d2d-0401-0010-efa3-af7a8647c3bc">Implementing Resource List Filters for Flexible UI Navigation</a> to see how it's implemented there.

You would need a folder src.config with the same structure you will find the KM LayoutSet export (i.e.: \install\data\cm\services\properties_metadata).

Hope this helps,

Robert

Hi Robert,

Thanks for your help.

For the guide, I guess what I want is not a resource filter - I wanna know how to add & map properties, commands, layout set...

For the structure, now I know I should add properties metadata in src.config, and maybe so it is with commands metadata - but what should I do for them.... I have looked at the exported configarchive, but there're many many co.xml. Do I need all of them? Your kind advice can save me lots of time~

Thanks,

Ray

Hi Ray,

just copy only the xml configuration files for your own KM configuration objects and keep the folder hierarchy as it is in the exported configarchive.

Best regards,

Robert

Hi Robert,

Fine, I am testing it according to your help.

This is the question of configuring & mapping commands, so how can I add & map properties along with deploying the par? For example, my repository manager may add some new properties (and namespaces), can I do it in code, rather than going to Content Admin - KM - Global Services - Properties?

Thanks,

Ray

Hi Ray,

as mentioned above, instead of creating the properties manually you can integrated the KM configuration XML files in your par file.

For example, to create a new property my_displayname you can first create a XML files with the following content and save it in the folder of the PAR file I mentioned above:

<?xml version="1.0"  encoding="UTF-8" ?>
<Configurable configclass="PropertyMetadata">
<property name="bundlekey" value="cm_rnd_displayname"/>
<property name="folder_patterns" value="/documents/**"/>
<property name="renderer" value="my_displayname"/>
<property name="values"/>
<property name="metadata_extension" value="my_labels"/>
<property name="default_value"/>
<property name="namespace_alias" value="my"/>
<property name="comparator_class"/>
<property name="readonly" value="false"/>
<property name="property_id" value="my_displayname"/>
<property name="maintainable" value="true"/>
<property name="hidden" value="false"/>
<property name="indexable" value="true"/>
<property name="resource_types"/>
<property name="mandatory" value="true"/>
<property name="group" value="my"/>
<property name="dependencies" value="false"/>
<property name="composed_of"/>
<property name="multi_valued" value="false"/>
<property name="type" value="String"/>
<property name="document_patterns"/>
<property name="additional_meta_tags"/>
<property name="sortmode" value="Ascending"/>
<property name="virtual" value="false"/>
<property name="mime_types"/>
<property name="labelIcon"/>
<property name="unique_id" value="my_displayname"/>
<property name="description"/>
</Configurable>

The namesace configuration file must be under src.config\install\data\cm\services\properties_metadata\namespaces\ and could look similar to this:

<?xml version="1.0"  encoding="UTF-8" ?>
<Configurable configclass="PropertyNamespace">
<property name="namespace" value="http://net.brose.portal/xmlns/cm"/>
<property name="alias" value="brose"/>
</Configurable>

Hope this helps,

Robert

Hi Robert,

Thanks. Now let's move on:)

For the property, I tried to put the xx.co.cml under properties_metadata and properties_metadata/properties, but neither is OK - namespace.co.xml under properties_metadata/namespaces is OK. Commands and layouts are also OK.

Then, the user needs first enable service "presentation" before he can change the layout set of a document. So, can I also enable this service, and set the repository's layout in configarchive? I guess we can add a co.xml under cm/repository_services, but I don't know the format:(

Or, before deploying the repository manager, can I specify its layout in code?

Thanks,

Ray

Help needed... How to deliver properties along with par, and set the default layout for this repository, or enable services like subscription/discussion by writing an xml file under cm/repository_services...?

Thanks

Hi Ray,

sorry for not being able to reply earlier.

You can deliver properties with a PAR file like you have done with other KM configuration settings.

As mentioned above you need to create a new Portal Application in NWDS and create the folders src.config / install / data / cm / services / properties_metadata.

In this folder you can create the your_property.co.xml file that can look similar with the one I pasted above.

Additional you might need a configArchive.properties file directly under src.config with content similar to this:

ca.name=my.test
ca.version=6.0.1.0
ca.dependencies=
ca.creation.time=1041
ca.creation.date=20070125
ca.creation.user=undefined
ca.creation.machine=undefined

Concerning the Repository Manager it's the same procedure. You need to create the folder structure src.config / install / data / cm / repository_managers and there the configuration file with the content similar to the one posted by Thilo in the <a href="https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/a772ac90-0201-0010-9985-8a1f74d7b152">Implementing a Repository Manager Guide</a>.

The section where you mention the repository services might look like:

<property name="services" value="layout, properties"/>

Hope this helps,

Robert

Hi Robert,

Thanks for help:)

As to properties, I've tried to add a my_property.co.xml under install/data/cm/services/properties_metadata and ..../properties_metadata_properties, but neither is OK, saying that there's no corresponding configuration definition file under some folder I forgot:(

From the import-xx.prjconfig I can see many things, like icons and mimes can also be deployed in the config archive. (local/cm/utilities/mimes, local/cm/utilities/icons, local/cm/utilities/channels, etc). Is there any document explaining the structure of the configuration files?

Thanks:)

Part of the import-xx-prjconfig:

Folder "config://local/cm/repository_services/event_mappings" migrated

Migrating folder "config://local/cm/utilities"

No configuration objects to create

Folder "config://local/cm/utilities" migrated

Migrating folder "config://local/cm/utilities/mimes"