The SQL-specific options probably apply equally to the Oracle and DB2 MAs, but I’ve never used ’em myself.<\/p>\n
We’ll start on the Connect to database<\/strong> page of the MA config, where you will no doubt have already filled in your server, database and table or view name. You may optionally enter a name of a Delta View<\/strong> (which could actually be a table) and Multivalue Table<\/strong> (which could equally be a view). Both options need explanation, and you will find it further down this page.<\/p>\n <\/p>\n On the Configure Columns<\/strong> page you will see the columns and their data types as found in SQL. There is an Edit<\/strong> button here but it all it does is allow you to set how empty fields are treated. If you want to change a data type, or add an extra field, you must do it in SQL and then, in ILM, choose the MA and Refresh Schema<\/strong>.<\/p>\n The Set Anchor<\/strong> option refers to the primary key of the table. It will be used to uniquely identify the record. Get it right as you can’t change it later!<\/p>\n For the Object Type<\/strong> you have two choices – fixed or column. This will also be unchangeable after MA creation.<\/p>\n The Delta View\/Table<\/strong> is where you list that subset of records which have changed since the last import, allowing you save time with a Delta Import and Delta Sync<\/strong>. The Delta table must have every<\/em> column of the primary table plus<\/em> an extra column indicating if the change is an ‘Add’, ‘Delete’ or ‘Modify’. As I’m just talking MA configuration here I shall refer you to my earlier post on how to make SQL delta tables<\/a>. It’s also covered in the MIIS Walkthroughs<\/a>.<\/p>\n Once you enter your Delta table name on the Connect to database<\/strong> page and click OK, you get this alarming looking message from ILM: “You must configure change type attribute (delta) in order to continue”. Which is kind of silly at this point, because you don’t configure it until the next <\/em>page. So OK the message, and you will arrive on the Configure Columns<\/strong> page.<\/p>\n Now you have the option to Configure delta<\/strong>. Click this button and you get a little form where you select that extra column in the delta table which holds the ‘Add’,’Delete’ or ‘Modify’ instruction. While you’re here you can also tell ILM you don’t want to use the words ‘Add’,’Delete’ and ‘Modify’, but something else instead – up to you.<\/p>\n You will also notice an option for Attribute modify<\/strong>. This is only enabled when you’re also doing multi-value imports. It’s rather an advanced topic so I shall refer you to this other post I wrote on attribute-level imports<\/a>.<\/p>\n The SQL MA will interpret each table line as a seperate object, and each column entry as a single value. This is fine for surname, userID and other such singled-valued attributes – but is no good for listing multiple telephone numbers, or direct reports, or group members.<\/p>\n To populate multi-valued attribtes from a SQL MA you must use a multivalue table.<\/p>\n Such a table can have multiple lines for each object, one for each attribute value. Using the classic example of group membership, you may have:<\/p>\n\n
Delta Table\/View<\/h3>\n
![\"\"](\"https:\/\/www.wapshere.com\/images\/ma-sql-configdelta.gif\")
<\/p>\nMultiValue Table\/View<\/h3>\n
![\"\"](\"https:\/\/www.wapshere.com\/images\/ma-multivaluesettings.GIF\")
<\/p>\n