Adding Extended Attributes for Data Exporter

Question

Hi, I'm having trouble in getting an exported attribute to export within the new Data Exporter feature. In fact, once i alter the export schema to include the additional column (ext att), it won't write to that table at all.
I am doing the following per the documentation from Sun, hopefully someone can point out the error of my way.
First I alter the IDM Schema Configuration.xml file to include the additional User extended attribute.
Next, I alter the model-export.xml file under model name='User' within WS_HOME to include the additional attribute here, my entry is as follows:
<field name='employeeId'
type='java.lang.String'
introduced='8.0'
max-length='50'
forensic='User'
queryable='true'
exported='true'
friendlyName='Employee Id'>
<description>The Peoplesoft ID coming over</description>
</field>
Next, I go to the unzipped directory of IDM hence, \exporter and execute: "ant rebuild" and "ant deploy".
The following takes place, The rebuild process regenerates my create and drop schema configuration scripts for MySQL. I run both scripts and
my new column with the newly added extended attribute appears in the EXT_USER table. I also issue the proper permission commands on the tables
I then undeploy my web application from Tomcat and re-deploy the web app.
I start the server, log into IDM and go to the Data Exporter configuration page. Under the User data type, my extended attribute does not show up. Further, what once worked, the scheduler now does not write to the EXT_USER table and gives the following error when I believe IDM is starting up. I have no doubt that this is a clue as to why it is not working:
"StartupServlet: Defining properties from web.xml
Starting: Identity Server...
...Finished starting Startup Servlet
{Model=User, employeeId=[], assignedRoles=[], idmManager=, businessPhone=[], location=[], MemberObjectGroups=[(id=#ID#Top)], lhdis=true, lhlocked=false, controlledObjectGroupsRule=, ACCT_CD=[], lastModDate=Tue Oct 21 16:44:21 PDT 2008, failedPasswordLoginAttemptsCount=0, description=, lastModifier=Configurator, role=[], divisionCode=[], companyMobilePhoneNumber=[], fullname=Anuradha Rao, employeeType=[], CompanyMailingAddress=[], objectClass=[Top, Object, Principal, User], hasCapabilities=false, questionLocked=false, [email protected], subtype=, managerId=[], sponsorId=[], contractorLocation=[], jobCode=[], locked=false, failedQuestionLoginAttemptsCount=0, xmlSize=936, res=[], repoMod=Tue Oct 21 16:44:21 PDT 2008, accountId=, textPagerEmailAddress=[], lastname=Rao, lastAuditorScan=, user_resources=[], creator=Configurator, id=#ID#54D7-:3AE94AA9C11:110E5685:2FC0FC1B3DEDDBF6, title=[], idmManagerNameNotFound=, faxNumber=[], facility=[], dis=0, lastPasswordUpdate=Wed Oct 01 15:31:47 PDT 2008, name=definabl, authType=, effectiveDate=[], createDate=Thu Sep 25 10:56:13 PDT 2008, jobTitle=[], prov=2, accounts=[], ControlledObjectGroups=[], costCenter=[], firstname=Anuradha, correlationKey=, primaryObjectClass=User, departmentName=[], roleInfo=[], accountType=, middleInitial=[], departmentId=[], displayName=, cubeNumber=[], disabled=true, }
ex: java.lang.reflect.InvocationTargetException"
java.lang.reflect.InvocationTargetException is thrown which leads me to believe that something is wrong with the javabean that is regenerated under the ant rebuild and the underlying User.hbm.xml file that regenerated as well. I can see from the User.hbm file that the new extended attribute has been added but this is as far as I have gotten. I really don't know where to go from here.
Any and all help is extremely appreciated.
Thank you. Dan

Answer 1

Hi Nik,
From section 1.4.2 of the install guide.
https://docs.oracle.com/middleware/1213/edq/DQINS/planning.htm#DQINS5205
EDQ Configuration Directories
EDQ requires two configuration directories, which are separate from the EDQ Home (installation) directory that contains the program files. The configuration directories are:
The base configuration directory: This directory contains default configuration data. Once EDQ is installed, the files in the base configuration directory must not be altered, renamed, or moved.
The local configuration directory: This directory contains overrides to the default configuration. EDQ looks for overrides in this directory first, before looking in the base configuration directory. Files in the local configuration directory can be modified to customize or extend EDQ.
The names and locations of the configuration directories are as follows:
If you are using Oracle WebLogic Server, the Oracle installation wizard automatically creates and populates the configuration directories in the EDQ domain with the names of oedq.home (base configuration directory) and oedq.local.home (local configuration directory). An example installation path is: WLS_HOME/user_projects/domains/edq_domain/edq/oedq.home
WLS_HOME/user_projects/domains/edq_domain/edq/oedq.local.home
If you are using Apache Tomcat, you create the configuration directories manually in any location, with any names, and the configuration utility will populate them. You are prompted to create the directories during the installation instructions.
Just copy flags.xml from your oedq.home casemanagement folder to your oedq.local.home casemanagement folder and edit the file accordingly.
thanks,
Nick