Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
Anonymous_User Absent Member.
Absent Member.

Re: Worked until consultant suggested running osp configupdate

On 09/01/2015 05:23 AM, Steven Williams wrote:
> On 08/31/2015 07:14 PM, ScorpionSting wrote:
>>
>> Some of the below variables were removed by the osp configupdate:
>>
>>
>> Code:
>> --------------------
>> DirectoryService/realms/jndi/params/AUTHORITY = ****
>> DirectoryService/realms/jndi/params/CONTAINER_OBJECT = ****
>> DirectoryService/realms/jndi/params/DRIVER_SET_ROOT = ****
>> DirectoryService/realms/jndi/params/DYNAMIC_GROUP_OBJECT = ****
>> DirectoryService/realms/jndi/params/GROUP_OBJECT = ****
>> DirectoryService/realms/jndi/params/GROUP_ROOT_CONTAINER = ****
>> DirectoryService/realms/jndi/params/GROUP_SEARCH_SCOPE = ****
>> DirectoryService/realms/jndi/params/GROUP_USER_MEMBER_ATTRIB = ****
>> DirectoryService/realms/jndi/params/KEYSTORE_PATH = ****
>> DirectoryService/realms/jndi/params/LOGIN_ATTRIBUTE = ****
>>
>> DirectoryService/realms/jndi/params/MANDATORY_SECURE_ADMIN_CONNECTION
>> = ****
>>
>> DirectoryService/realms/jndi/params/MANDATORY_SECURE_USER_CONNECTION =
>> ****
>> DirectoryService/realms/jndi/params/NAMING_ATTRIBUTE = ****
>> DirectoryService/realms/jndi/params/OBJECT_ATTRIB = ****
>> DirectoryService/realms/jndi/params/PLAIN_PORT = ****
>> DirectoryService/realms/jndi/params/PROVISION_ROOT = ****
>> DirectoryService/realms/jndi/params/ROOT_NAME = ****
>> DirectoryService/realms/jndi/params/SECURE_PORT = ****
>> DirectoryService/realms/jndi/params/USER_GROUP_MEMBER_ATTRIB = ****
>> DirectoryService/realms/jndi/params/USER_OBJECT = ****
>> DirectoryService/realms/jndi/params/USER_ROOT_CONTAINER = ****
>> DirectoryService/realms/jndi/params/USER_SEARCH_SCOPE = ****
>> DirectoryService/realms/jndi/params/USE_DYNAMIC_GROUPS = ****
>> DirectoryService/realms/jndi/params/USE_PUB_ANON = ****
>> DirectoryService/realms/jndi/params/UUID_ATTRIB = ****
>> DirectoryService/realms/jndi/params/UUID_AUX_CLASS = ****
>> RoleService/nrf-compliance-admin-assigned-identity-dn = ****
>> RoleService/nrf-configuration-rdn = ****
>> RoleService/nrf-role-admin-assigned-identity-dn = ****
>> --------------------
>>
>>

> Greetings,
> Yes, the configupdate that is under the osp root install folder, is
> set-up to be used in the case where OSP is deployed without the Apps.
> When you launched this version of configupdate, you should have only
> seen three (3) tabs with the following names:
>
> Identity Vault
> Authentication
> SSO Client
>
> When you press OK using this version of configupdate, it will modify the
> ism properties file a certain way.
>
>
>
> The configupdate that is in the UserApplication root install folder, is
> set-up to handle more cases. With this set-up of configupdate you can
> see either three (3) or four (4) tabs with the following names:
>
> User Application
> Reporting
> Authentication
> SSO Clients
>
>
> *Note: with adding Access Review to the environment, it is possible to
> see up to five (5) tabs*
>
> =================
>
> There can be three (3) different configupdate "installs" on your server
> if you have OSP, Identity Applications, and Identity Reporting all
> installed on the one (1) server.
>
> When you use the different set-ups/installs of configupdate depends upon
> the situation
>
> For Example:
>
> 1) If you only have OSP deployed, then you would utilize the
> configupdate under the osp root install folder. This will be necessary
> to map in the values of the SSO Clients tabs after you have performed
> the other installs.
>
> 2) If you have OSP and Identity Applications deployed together then you
> should utilize the configupdate in the UserApplication root install folder
>
> 3) If you have OSP, Identity Applications, and Identity Reporting
> deployed together then you should utilize the configupdate in the
> UserApplication root install folder
>
>
> If this is not clear in the documentation, then I will submit a note to
> have this updated in the documentation.
>
> We are looking to improve the way one needs to update the environment
> when you are deployed in different configurations
>
> -Distributed Application servers (Each component on its own Tomcat
> OSP
> SSPR
> Identity Applications
> Identity Reporting
>
> -Different Application servers (OSP on Tomcat and the Applications on
> WebSphere)
>
> -Clustered
>
>
>

Greetings,
Point of clarification.

As long as the jars necessary for configupdate are the same in each
"install", then what makes each "set-up" of configupdate behave
differently is how they are configured.

Please be aware that there is a HotFix 1 for configupdate:
https://dl.netiq.com/Download?buildid=U1Ob41FCiD8~



--

Sincerely,
Steven Williams
Lead Software Engineer
Micro Focus
0 Likes
ScorpionSting Absent Member.
Absent Member.

Re: Worked until consultant suggested running osp configupdate


HF1 is in, but going back to UA .sh does not fix broken .properties
file, in fact sections of java ui are missing.


--
-"Also now available in 'G+'
(https://plus.google.com/u/0/112362149544381813153) and 'Website'
(https://www.isam.kiwi/) format".- 😉
------------------------------------------------------------------------
ScorpionSting's Profile: https://forums.netiq.com/member.php?userid=469
View this thread: https://forums.netiq.com/showthread.php?t=54140


Visit my Website for links to Cool Solution articles.
0 Likes
Knowledge Partner
Knowledge Partner

Re: Worked until consultant suggested running osp configupdate

Steven Williams wrote:

> There can be three (3) different configupdate "installs" on your server if
> you have OSP, Identity Applications, and Identity Reporting all installed on
> the one (1) server.
>
> When you use the different set-ups/installs of configupdate depends upon the
> situation
>
> For Example:
>
> 1) If you only have OSP deployed, then you would utilize the configupdate
> under the osp root install folder. This will be necessary to map in the
> values of the SSO Clients tabs after you have performed the other installs.
>
> 2) If you have OSP and Identity Applications deployed together then you
> should utilize the configupdate in the UserApplication root install folder
>
> 3) If you have OSP, Identity Applications, and Identity Reporting deployed
> together then you should utilize the configupdate in the UserApplication root
> install folder


Intuitive.

> If this is not clear in the documentation, then I will submit a note to have
> this updated in the documentation.


How about naming them differently and provide a symlink to the correct version
in a central location, which will be the *only* file/path/command mentioned in
the docs? Or even better: only install the one that's not going to break stuff
in the first place? or ever better: install only one version that can handle
all scenarios.

I really do not get why that many things on the UA side of IDM have to be so
unnecessarily confusing and full of pitfalls...
______________________________________________
https://www.is4it.de/identity-access-management
0 Likes
ScorpionSting Absent Member.
Absent Member.

Re: Worked until consultant suggested running osp configupdate


Really, "all" configupdate's should not look at
ism-configuration.properties and go "oh, this variable is here so I'll
display this section and configure this way", it should go "I see
IDMProv.war, therefore I require ism-configuration.properties to have
all these values"


--
-"Also now available in 'G+'
(https://plus.google.com/u/0/112362149544381813153) and 'Website'
(https://www.isam.kiwi/) format".- 😉
------------------------------------------------------------------------
ScorpionSting's Profile: https://forums.netiq.com/member.php?userid=469
View this thread: https://forums.netiq.com/showthread.php?t=54140


Visit my Website for links to Cool Solution articles.
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.