Big news! The community will be moving to a new platform April 21. Read more.
Big news! The community will be moving to a new platform April 21. Read more.
Commodore
Commodore
2580 views

Packaging the eDirectory Schema

Hi folks,

Over the years I've worked on lots of projects where a Development / User Acceptance Testing / Production environment model is utilised.

Packages make moving drivers / resources through that model really easy. One thing keeps coming back to bite me every now and then though is remembering to move the supporting schema updates into the higher environments.

My thought "Wouldn't it be awesome to include your vault schema in an Identity Vault package"

Just wanted to canvas thoughts really on whether you agree, and if not, I'd be interested to hear how you version control and manage your schema between environments?

Cheers!

Jim
Labels (1)
Tags (3)
0 Likes
18 Replies
Commodore
Commodore

Yeah - I do like Lothar's idea.

For our purposes I have consolidated the customer's schema into a single file that is sitting in a library that is off the root so that I can have it as an Identity Vault package - OCD I know :)! Had I a little more time, or been doing this from scratch I would take the approach of one per class.

I am doing a similar thing to Geoff for some JDBC drivers we have implemented - putting the SQL definitions into a resource so that you have everything you need right there in the driver package.

If I get a quite 5 minutes I might submit a request for improvement to have Designer handle packaging the schema itself.

Really appreciate your feedback as ever folks!

Have a great day / evening

Regards

Jim
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

> If I get a quite 5 minutes I might submit a request for improvement to
> have Designer handle packaging the schema itself.


The request is already in there. One possible problem is that packages
are meant to be uninstallable. How would you reliably uninstall Schema
updates?

What does uninstall mean in the context of a schema update?

I am ok with it being a one way action. But something to consider.

Also, what does an upgrade look like? Reapply? It seems
straightforward, but there is more to it..

Now, if Designer read in the schema, applied it to the local model,
generated the diffs for eDir maybe that could work better.

0 Likes
Commodore
Commodore

Hi Geoff, I didn't see an idea for packaging the schema, so I have created one. I guess it will get closed as a duplicate if there is already one there.

My thoughts where that you would have the package add / remove the extensions from your workspace schema - it's then your problem to get them into eDirectory - compare is generally the way to go.
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

On 7/6/2018 5:54 AM, jimgoodall wrote:
>
> Hi Geoff, I didn't see an idea for packaging the schema, so I have
> created 'one'
> (https://www1.v1ideas.com/MFI/identity-manager/Idea/Detail/14016). I
> guess it will get closed as a duplicate if there is already one there.


I know I have mentioned this to devs many times before, guess no one
ever wrote it up. Thanks for taking the time.

> My thoughts where that you would have the package add / remove the
> extensions from your workspace schema - it's then your problem to get
> them into eDirectory - compare is generally the way to go.


That works.


0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

jimgoodall;2483505 wrote:
Hi folks,

Over the years I've worked on lots of projects where a Development / User Acceptance Testing / Production environment model is utilised.

Packages make moving drivers / resources through that model really easy. One thing keeps coming back to bite me every now and then though is remembering to move the supporting schema updates into the higher environments.

My thought "Wouldn't it be awesome to include your vault schema in an Identity Vault package"

Just wanted to canvas thoughts really on whether you agree, and if not, I'd be interested to hear how you version control and manage your schema between environments?

Cheers!

Jim


I agree. In fact, it's such a great idea, that I put it in Bugzilla ... 8 years ago?

Bug 636889 - Enhancement: Option to add Schema to the packages.
https://bugzilla.netiq.com/show_bug.cgi?id=636889

So, yeah. I still think it's a good idea.
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

On 7/6/2018 11:16 AM, dgersic wrote:
>
> jimgoodall;2483505 Wrote:
>> Hi folks,
>>
>> Over the years I've worked on lots of projects where a Development /
>> User Acceptance Testing / Production environment model is utilised.
>>
>> Packages make moving drivers / resources through that model really easy.
>> One thing keeps coming back to bite me every now and then though is
>> remembering to move the supporting schema updates into the higher
>> environments.
>>
>> My thought "Wouldn't it be awesome to include your vault schema in an
>> Identity Vault package"
>>
>> Just wanted to canvas thoughts really on whether you agree, and if not,
>> I'd be interested to hear how you version control and manage your schema
>> between environments?
>>
>> Cheers!
>>
>> Jim

>
> I agree. In fact, it's such a great idea, that I put it in Bugzilla ...
> 8 years ago?
>
> Bug 636889 - Enhancement: Option to add Schema to the packages.
> https://bugzilla.netiq.com/show_bug.cgi?id=636889
>
> So, yeah. I still think it's a good idea.


Haha! I knew it was in there. I remember having this discussion MANY
times since IDM 4.0 was released with packages.

0 Likes
Commodore
Commodore

Given it my vote sir 😉
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.