Skip navigation
All People > Andrew Nguyen > Andrew Nguyen's Tech Tips > 2016 > March
2016

Andrew Nguyen's Tech Tips

March 2016 Previous month Next month
Andrew Nguyen

Bulk Loader 101

Posted by Andrew Nguyen Employee Mar 25, 2016

Bulk Loader comes in a separate install from the Identity Manager Application. This is located in the Provisioning Components zip file. Once you unzip the file, navigate to: Clients -> BulkLoader and run the setup.exe.

Ensure this checklist is complete:

http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec560908.aspx

 

To summarize, Enable Web Services for you environment and the task in which you would require to use the Bulk Loader with. For example, I want to use Bulk Loader on a Create User event. I would enable Web Services for that task.

 

There are sample bulk loader csv in the sample directory. The samples included are:

- feeder_create_users.csv

- feeder_delete_users.csv

- feeder_modify_users.csv

In order to use the JCS from the Connector Server SDK, you would have 2 options:

  1. Shutdown the JCS.exe from the Connector Server
  2. Change port of the Connector Server SDK JCS

Option 1:

Once the JCS.exe is shutdown, the JCS from the Connector Server SDK can be started up since they both are listening on the same ports. 22001 and 22002.

 

Option 2:

 

Suggested option as it won't have an interference with the regular JCS from the Connector Server.

 

For option 2, the file server_osgi_common needs to be modified. This file is located under: ...\Identity Manager\Connector Server SDK\build\apache-servicemix-4.3.1-fuse-00-00\jcs\conf

 

<transportConnectors>

            <transportConnector name="http" uri="http://0.0.0.0:22001" />

            <transportConnector name="https" uri="https://0.0.0.0:22002" />

        </transportConnectors>

 

The ports numbers "22001" and "22002" needs to be changed to another port which aren't being used.

Skins can be changed for Identity Manager through the Identity Management Console. Found on the /iam/immanage/ URL.

 

These are set by the "DefaultConsole" parameter. Navigate to the following links in the immanage page: Home->Environments -> <environment-name> -> Advanced Settings -> Miscellaneous.

 

The default skins that come with identity manager are labelled as:

- ui7 (Current default skin)

ui7.png

- imcss

imcss.png

- ca12

ca12.png

- ca

ca.png

ui7 is the recommened skin to be used as it is the most stable and is used to verify any issues within the product.

Question:

Is Identity Manager supported to meet 508 compliance?

 

Answer:

508 compliance has issues when using the ca12 UI. This is the default UI in CA Identity Manager versions 12.5.x. When using CA Identity Manager 12.6.x, the default UI is ui7. This will resolve the issues CA Identity Manager has with 508 compliance. In versions previous than 12.6.7, "Navaigation - Throughout, tab order goes from top banner to footer. It needs to start reading from the top and continue intuitively."

 

Example: Top banner -> footer -> left menu -> main content

 

Should read as:

Top banner -> left menu -> main content -> footer

 

This issue is resolved in CA Identity Manager 12.6.4 (Defect #: 21558292)

 

CA Identity Manager complies with Section 508 of the US Rehabilitation Act and the Web Content Accessibility Guidelines (WCAG2.0). This support only applies to Windows-based and Mac-based applications. The Text-to-Speech functionality provided by CA Identity Manager allows you to hear command options and text read aloud.

For more information on 508 compliance, please visit:

- https://docops.ca.com/ca-identity-manager/12-6-7/EN/release-notes/accessibility-features

- http://www.ca.com/us/~/media/Files/DataSheets/identity-management-and-governance-solution-for-section-508-compliance.pdf