Script for starting OIM/JBoss as a windows service

You can use this in conjunction with JavaService.exe to launch OIM's JBoss as a service (http://forge.objectweb.org/projects/javaservice/).You need to update this with your proper environment settings.

@echo off

SETLOCAL

set JAVA_HOME=C:\j2sdk1.4.2_14
set JBOSS_HOME=C:\jboss-4.0.3SP1
set OIM_HOME=c:\oracle\xellerate
set NAME=OIMService
set JVMOPTIONS=-DXL.HomeDir=C:\oracle\xellerate -Djava.awt.headless=true

SET javaservice=%OIM_HOME%\bin\JavaService.exe
SET logdir=%OIM_HOME%\logs
SET jbossjar=%JBOSS_HOME%\bin\run.jar
SET toolsjar=%JAVA_HOME%\lib\tools.jar
SET jvmdll=%JAVA_HOME%\jre\bin\server\jvm.dll
SET svcmode=-auto
SET description=Oracle Identity Manager
SET dependsopt=

"%javaservice%" -install %NAME% "%jvmdll%" -Djava.class.path="%jbossjar%;%toolsjar%" %JVMOPTIONS% -Xms128M -Xmx512M -start org.jboss.Main -stop org.jboss.Main -method systemExit -out "%logdir%\service_out.log" -err "%logdir%\service_err.log" -current "%JBOSS_HOME%\bin" %dependopt% %svcmode% -overwrite -startup 6 -description "%description%"

ENDLOCAL

@pause

Delete related to OIM Users

OIM do not allow for the deletion of users for reporting and auditing reasons. In
addition, the data model is very complex and the USR entries are involved in
almost every table in some fashion which makes it very dangerous to simply
remove the users from USR table resulting in unintended consequences and
negating the validity of any development or testing.

However, we can mark the users as deleted and then reuse the user IDs. Or, we can change the userid for the users you no longer need to indicate that they are no longer valid if we do not want to enable userid reuse.

If some one want to create a clean database ,he would create a new database, install OIM against it, and then migrate the connectors and integrations to the new OIM server using the Deployment Manager.

STEPS


In the manage users screen of the Administrative Console we can delete a full page of users
by:
- clicking on the "Delete" checkbox in the top row of the table to select the delete option for all of the users in the page
- and then clicking on the "Delete" button at the bottom of the page.

By default the page will only display 10 users at a time but the number of rows displayed can be changed to
as high as 50 rows by changing the "global.displayrecordNum.value" in the
xlDefaultAdmin.properties file.
To reuse UserIDs:
- Open the Design Console
- Goto the Administration - System Configuration form
- Search for the Keyword "XL.UserIDReuse" and set the value to TRUE

This will allow you to reuse the UserIDs of deleted users.

Customization Related to Redirect in OIM

This summary is not available. Please click here to view the post.

Include a Link Below in OIM on left panel

Menu link is retrieved from the database through the menu items created from design console
example:
(Form Information screen):
Class Name: My Menu.Menu 1
Description: My Menu Menu 1
Type: menuitem
- On the UI, the menus are grouped and the names globalized from the corresponding entries in xlWebAdmin.properties file
menuGroup.My-Menu=My Menu
menuItem.My-Menu.Menu-1=Menu 1


- /pages will have a new jsp page added with a 'tiles:insert' definition code for the entry
example: (/pages/SamplePage.jsp)
<%@ taglib uri="/WEB-INF/tld/struts-tiles.tld" prefix="tiles" %>
- tiles-defs.xml will have an entry with the definition name, referring to the definition code defined in the /pages jsp code
- The 'title' can have a code with a corresponding entry in the xlWebAdmin.properties file. This will be the title shown on the web page title bar
- The 'body' will refer to a jsp page to be created in the /tiles folder
example:
In tiles-defs.xml:






In xlWebAdmin.properties:
samplepage.title.showpage=Sample Page Title - A new jsp to be added to /tiles folder with the name used in the tiles-defs.xml entry
example: /tiles/SamplePageTiles.jsp
- struts-config.xml file will have two entries:
- one for form bean in the section, that will have the bean properties required to store data for the logic in the new functionality to be added.
example:
type="com.thortech.xl.webclient.actions.SampleForm" /> - one for the action class in the section, that is used for performing all the java logic before forwarding to a jsp page with the display contents.
example:
type="com.thortech.xl.webclient.actions.SampleAction"
validate="false"
input="/pages/SamplePage.jsp"
scope="session"
path="/sample"
parameter="method">



- In the xlDefaultAdmin.properties file put an entry that will be used to forward to the corresponding method in the java class:
- menuItem.My-Menu.Menu-1.link=sample.do?methodCode

- In the xlWebAdmin.properties file put the entry with the value as the one defined after '?' in previous step:
- sample.message.selection.method1=methodCode
- In the custom action class have the struts documented standard method getKeyMethodMap() with the following content:
Map methodMap = super.getKeyMethodMap(); methodMap.put("sample.message.selection.method1", "method1");
- Define the method with the name as 'method1()' and put the logic and the forward in that.

How We Can Make User ID field Non-Required On Create User Form

1.Edit FormMetaData.xml from \xellerate\config directory

2. Change optional attribute value "false to "true" under section in FormMetaData.xml.
Here < > are there for Form name and Attribute Reference
Form name="3"
!-- User ID --
AttributeReference editable="true" optional="true">-16 /AttributeReference

3. Save FormMetaData.xml and Restart the Application Server.