test

Oracle Waveset 8.1.1 Release Notes

Chapter 7 Documentation Additions and Corrections

This section contains new and corrected information that was required after the Oracle Waveset 8.1.1 documentation set was published.

Identity Manager 8.1 Deployment Reference

This section contains new information and documentation corrections for Oracle Waveset 8.1.1 Deployment Reference.

Issues Common to Both Workflows and Forms

The Forms and Workflow chapters of this guide are missing the following discussion about assigning scope to <Variable> elements: (ID-14915)

Identity Manager assigns a scope to all <Variable> elements when the element is declared. If you do not assign a value to the scope attribute, Identity Manager assigns it a value of local, which means that the variable can be accessed only within the XPRESS section that is declared in.

Additional Variable attributes that define scope include:

input -- Declares that the <Variable> element has local scope and that the value can be initialized by the caller.

output -- Declares that the <Variable> element has local scope but can be returned to the caller.

external -- Declares a <Variable> that has non-local scope - that is, assignments to this variable will result in assignment to this variable in the scope it was first declared in.

The following discussion of the Identity Manager whitelist feature is missing from this chapter. (ID-19474)

The Identity Manager whitelist feature makes it possible to check forms and workflows that use the SaveNoValidate action against a list of IDs or form names. Identity Manager checks the whitelist for either form names or form-owner IDs.) The list of IDs, called saveNoValidateAllowedFormsAndWorkflows, is located in the security attribute in the System Configuration object. If the form name or owner ID is on the whitelist, the form or workflow can use the SaveNoValidate action. If the form name or the owner ID is not on the list, the form or workflow is processed using a Save action. If the list is not present, all forms and workflows can be processed as SaveNoValidate.

To implement this feature in your deployment, you must add any forms or workflows using SaveNoValidate to the saveNoValidateAllowedFormsAndWorkflows list in the System Configuration object. To see the IDs or form names that you must add, check the syslog or turn trace level 4 on for com.waveset.ui.util.GenericEditForm and submit any custom forms or workflows that use SaveNoValidate. A warning including the ID will be logged. If you are getting “null” form names in the syslog, confirm that the form in the TaskDefinition that was run has a name attribute.

Workflow-Related Issues

The Workflow chapter is missing the following discussion of the handleNativeChangeToAccountAttributes workflow (ID-3275):

Whenever Oracle Waveset detects a native change (that is, a change not performed through Oracle Waveset) to the values of an auditable attribute of a resource account, it responds by running the handleNativeChangeToAccountAttributes workflow, which is associated with this System Configuration object attribute:

<Attribute name='process'>
  <Object>
    <Attribute name='handleNativeChangeToAccountAttributes' value='Audit Native
      Change To Account Attributes'/>
  </Object>
</Attribute>

This workflow logs the native change events to the event log if you have enabled the Changes Outside Lighthouse audit filter. Otherwise, Identity Manager ignores the event. Warning: Be careful which methods you call from any workflow that replaces the default workflow listed above.

Because Identity Manager launches this workflow whenever a resource account fetch reveals a native change, it must not invoke any method or workflow that would trigger another fetch of the same resource account. For example, an infinite loop will result if you call any WorkflowServices method that assembles the user view: getView(User),checkoutView(User) and possibly checkinView(User).

The fact that Identity Manager handles each native change by running a workflow allows you to hook the native change event, and to handle that native change however you see fit by replacing or adding to the default native change workflow. For example, you might choose to send email to an administrator or a user, to record the event in a database, to queue an update that would back out the native change, or even to pull that native change into and push it back out to the other resources.

The Workflow chapter of this guide is missing the following description of how to specify the subject or administrator of a source adapter task. (ID-19694).

You can assign a subject or administrator to a Source adapter task and designate the server on which it runs by editing the following attributes of the system configuration object. source.subject specifies the login name of administrator designated as the owner of this task. sources.host specifies the server on which the task runs. The new values in the configuration object are by default:

<Attribute name='sources'>
           <Object>
             <Attribute name='hosts'/> <!-- any host is the default -->
           <Attribute name='subject' value='Configurator'/>
         </Object>
         </Attribute>

Identity Manager 8.1 Resource Reference

This section contains new information and documentation corrections for Oracle Waveset 8.1.1 Resources Reference.

The discussion of identity connectors is missing the following information about how ConnectorAdapter implements the run() method: The arguments passed to the runResourceAction service are passed to the script (defined in the ResourceAction) as direct script variables. (ID-19856)

Identity Manager 8.1 Service Provider Deployment Guide

This section contains new information and documentation corrections for Oracle Waveset Service Provider 8.1.1 Deployment.

Developing Customer Adapters

The ResourceAttribute element may contain a ValidationPolicy element. A validation policy ensures the value a user specifies on the Resource Parameters page meets the requirements defined in a separate policy object.

The following sample causes the adapter to use the Port Policy to ensure the specified value is valid. The default Port Policy checks the value is an integer between 1 and 65536.

<ResourceAttribute name=.Port. value="123">
   <ValidationPolicy>
      <ObjectRef type="Policy" id="#ID#PortPolicy" name="Port Policy"/>
   </ValidationPolicy>
</ResourceAttribute>

Identity Manager IDE Frequently Asked Questions (FAQ)

This FAQ answers some commonly asked questions related to using the Identity Manager IDE.

The information is organized into these categories:

Using NetBeans

Question:

Which version of Netbeans should I use?

Answer:

Use the Netbeans version referenced in the Oracle Waveset product documentation provided for the Netbeans plugin version you are using.

Note –

Always use the exact version referenced because even patch releases can cause major functionality to break.

Question:

The Netbeans plugin was working, I did something, and now it is no longer working. What could be causing this problem?

Answer:

This problem is commonly caused by a corrupt file in your .netbeans directory. Generally, deleting your .netbeans directory and re-installing the NetBeans plugin resolves the problem. (Deleting the .netbeans directory effectively uninstalls the NetBeans plugin. You lose all of your user settings, but the contents of your project will be safe.)

    The steps are as follows:

  1. Shutdown NetBeans.

  2. Delete the .netbeans directory.

  3. Start NetBeans.

  4. Install the NetBeans plugin.

  5. Restart NetBeans.

Working with Projects

Question:

Building and running a project is taking a very long time, and the Identity Manager IDE seems to be copying a lot of files. What could be causing this problem?

Answer:

This problem can occur for the following reasons:

Question:

Now that I have created an Identity Manager project, what files should be checked into source control?

Answer:

See the “CVS Best Practices” section in the Identity Manager IDE README.txt for information.

Question:

What are the best practices for using project management in CVS?

Answer:

See the “CVS Best Practices” section in the Identity Manager IDE README.txt for information.

Question:

When are objects imported into the repository?

Answer:

See Working with the Repository for information.

Question:

How do I add a new JAR to the project?

Answer:

See the “How to add a new JAR dependency” section in the Identity Manager IDE README.txt.

Working with the Repository

Question:

Which repository should I use for my sandbox repository?

Answer:

Use the embedded repository for your sandbox— particularly if you are using Oracle Waveset 7.1 (or higher), which has an HsSQL repository available. You lose functionality if you do not use the embedded repository.

Refer to the “Working with the Repository” section in the Identity Manager IDE README.txt for more information.

Question:

When are objects imported automatically?

Answer:

You have to configure Identity Manager IDE to import objects automatically.

The steps are as follows:

  1. Select Repository > Manage Embedded Repository from the IdM menu.

  2. Enable the Automatically Publish Identity Manager Objects option on the Manage Embedded Repository dialog.

    Note –

    This option is not available for Identity Manager Project (Remote) or if you specify your own repository.

  3. Select Project > Run Project or Project > Debug Project.

    The Identity Manager IDE automatically imports all objects that have changed since the last time you ran the project.

    Tip –

    Automatically publishing Identity Manager objects increases the time needed to start the server. To minimize server start time, disable this option and explicitly upload objects to the repository.

Question:

What is the most effective way to upload objects?

Answer:

Use one of the following methods to upload modified objects:

Either method uploads the object or objects directly to the server, so there is no cache latency issue and it is much faster than using Run Project or Debug Project. The Upload Objects feature is available regardless of which repository you are using.

Using the Identity Manager IDE Debugger

Note –

The Netbeans embedded application server automatically shuts down whenever you perform any of the following project operations:

Question:

The Identity Manager IDE Debugger is sluggish. What could be causing this problem?

Answer:

To improve the Debugger’s performance:

Question:

I cannot set a breakpoint in the Debugger. What could be causing this problem?

Answer:

The following conditions might prevent you from setting a breakpoint:

Question:

I set a breakpoint in the Debugger and it is not suspending on the breakpoint. What could be causing this problem?

Answer:

There are two things to check:

Working with Rules

Question:

When developing rules in Netbeans, why is design mode not available for a Rule Library?

Answer:

The design mode functionality is available from the explorer tree in Projects view. Use the following steps:

  1. Expand the library node and right-click a rule.

  2. When the pop-up menu displays, select Properties and then click Body.

Localization Scope

Historically, Oracle Waveset does not localize resource objects and functions, primarily because they are mostly samples that get loaded (through init.xml) during initialization of Oracle Waveset, and because the attributes of object types can vary between actual customer deployments, depending on the level of customizations. Following is a list of areas where users might encounter English: (ID-16349)

Online Help

This section contains documentation corrections for online help.

The “Configure Reports” help page contains the following sentence, which should be disregarded:

Fonts should also be added to the JVM in order for graphs to display properly.

The sentence is incorrect. Adding fonts to the JVM is not necessary in order to properly render text in the PDF report.