Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Custom Propertys and Bundle Files help!!!!!!

Hi All

I have created 2 properties, 'costcenter' and 'employeenumber' and I have them mapped to the corisponding AD properties and added them in the various places for them to appear on the User Details popup, which they do.

However they appear as the property name not the label name I have specified in my bundle file e.g 'costcenter' displays as 'costcenter' instead of 'Cost Centre'.

I have user the following link to set this up:

I have created 2 files and and they both contain the same text:



I have ziped the files and rename it to MyBundle.jar and put it in the j2ee/cluster/server<n>/apps/

The label is specified in System Administration - System Configuration - Content Management - Global Services - Property Metadata - Properties in the section Key For Label.

The Metadata is specified in the Metadata Extension section.

I have restarted the J2EE engine and the property lablel has not changed. What am I doing wrong?

Message was edited by: Phil Wade

Former Member
Former Member replied

Hi Phil,

You need to go carefully through the provided link <b>and</b> the there mentioned links.

You should be able to get it working with the PAR file provided by SAP. If not, check my mail address from my profile and send me a short mail, I will send you another example PAR.

Please make sure that you have checked those things first:

1. If the bundle file are named,, then the location in the metadata extension must have the name (not lable<b>s</b>).

2. If you have changed the PAR file name ("customer" to "arportal") make sure you rename also the path to the bundle file and also the entry in

3. When deploying with NWDS make sure you have set the option "Yes, I want the non java sources included into the portal component jars." You find this entry if you go to the menu "Window" -> "Preferences" -> "SAP Enterprise Portal" -> "Application Development Studio".

4. Deploying the bundle file might need a restart of KM, as hot deployment is not supported.

Hope this helps,


0 View this answer in context
Not what you were looking for? View more on this topic or Ask a question