An access gate is required instead of a standard webgate when you need to control access to a resource where OAM doesnot provide out of the box solution.
In addition to the creation of access gate profile in the Access Console, you would also need Access Server SDK to invoke Access System.
To do this, follow this approach.
1. Create the access gate profile with the hostname where you use client to invoke OAM Access System.
2. Install Access Server SDK in the client machine. Specify the access gate details in the install wizard.
3. Run ConfigureAccessGate tool present in the folder /AccessSDK_InstallDir/oblix/tools/ as shown below.
D:\oracle\oam10143\AccessServerSDK\oblix\tools\configureAccessGate>configureAccessGate.exe -i D:\oracle\oam10143\AccessServerSDK -t AccessGate -w TomcatAccessGate -m simple -P welcome1 -h accessSvr_hostname -p 6021 -a accessServer
Change the details as per your environment.
4. In your client code, specify the Access SDK location pointing the jobaccess.jar to the jar file located in above folder. Don’t try to copy the jar file to any other folder in your local machine and point that, this will not invoke the ASDK at runtime.
5. Write your code to use classes present in com.oblix.access.* for invoking Access SDK API. If you want to invoke policy Manager API then use the classes present in com.oblix.accessmgr.*.
There are few code samples that will be available in ASDK install folder /AccessSDK_InstallDir/samples.
I am engulfed in Oracle Identity & Access Management domain. I have expertise on providing the optimized solutions for user provisioning, web access management, Single Sign-On and federation capabilities etc., I am also well versed with complex integrations within Identity Management and other product domains. I have expertise on building demos and implementation experience on products Oracle Access Manager, Oracle Adaptive Access Manager, Oracle Entitlement Server, Oracle Virtual Directory, Oracle Internet Directory etc., Look @ my blog: http://talkidentity.blogspot.com