SAP connector

Transforma EMP type do idoc.


----

Employee Type

import java.util.HashMap;
import oracle.iam.connectors.common.transform.Transformation;

import common.utils.CustLogger;
import common.utils.Constants11g;

public class EmployeeTypeTransform implements Transformation {
 
    private CustLogger logger = new CustLogger("OIMCP.SAPH");
    private String sClassName = getClass().getName();
         
    public Object transform(HashMap hmUserDetails, HashMap hmEntitlementDetails,String sField) {

     String sMethodName = "transform";
     logger.setMethodStartLog(sClassName, sMethodName);
     String sEmpType = Constants11g.EMP_TYPE_FULL_TIME;
   
     if(null != hmUserDetails) {
  
        //Declare and initialize user details from recon
        String sResourceType = (String)hmUserDetails.get("Resource Type");
          
        logger.info(sClassName, sMethodName, "Resource Type: " + sResourceType);
             
        //Verifies user Resource Type and sets Employee Type
            if (sResourceType.equalsIgnoreCase(Constants11g.RES_TYPE_INT) ) {
                sEmpType = Constants11g.EMP_TYPE_EMPLOYEE;
            } else if(sResourceType.equals(Constants11g.RES_TYPE_CON)) {
                sEmpType = Constants11g.EMP_TYPE_CONSULTANT;
            } else if(sResourceType.equals(Constants11g.RES_TYPE_PAR)) {
                sEmpType = Constants11g.EMP_TYPE_PARTNER;
            }
        
        logger.info(sClassName, sMethodName, "Setting Employee Type to : " + sEmpType);
     }
   
    return sEmpType;
  
 }

Configurei 2 Lookups para ativar a transformacao:

- Lookup.SAP.HRMS.ReconTransformation

Employee Type

package.classEmployeeTypeTransform

 
- Lookup.SAP.HRMS.Configuration

Use Transformation For Recon:

Yes

 

Sao

Hierarquia de versoes de forms

select level, lpad(sdl_label,Length(sdl_label) + LEVEL  -1,'-') VERSION , sdl_create
  from (select * from sdl
where sdk_key = 41 and sdl_current_version is not null ) a
  start with a.sdl_parent_version is null
  connect by prior a.sdl_current_version=a.sdl_parent_version;

Forms Hierarchy

Deleting Application Instances

Deleting Application Instances

OIM 11g R2

An application instance can be deleted in any one of the following ways:

• Deleting the application instance from the Application Instances section of the Oracle Identity System Administration.
  
• Deleting the IT resource, which is a constituent of the application instance.
  

When you delete an application instance by using any one these methods, the application instance is not hard-deleted from Oracle Identity Manager. The application instance is soft-deleted. This is because accounts provisioned as a result of the application instance might exist in the target system. Therefore, after deleting an application instance, you must run a scheduled job to achieve the following:

• Unpublish the application instance from the entity publication
  
• Unpublish the associated entitlements from the entity publication
  
• Revoke, or hard-delete, or mark as deleted all the accounts for the application instance
  

To delete an application instance:

1. In Oracle Identity System Administration, under Configuration, click Application Instances. The Application Instances page is displayed with a list of application instances that are published to your organization.
   
2. Search and select the application instance that you want to delete.
   
3. From the Actions menu, select Delete. Alternatively, click Delete on the toolbar. A message box is displayed asking for confirmation.
   
4. Click Delete to confirm. The application instance is soft-deleted in Oracle Identity Manager.
   You can also delete an application instance by deleting the IT resource of the application instance. For information about deleting IT resources, see "Managing IT Resources" in the Oracle Fusion Middleware Developer's Guide for Oracle Identity Manager.
   
5. Run the Application Instance Post Delete Processing Job scheduled job. This scheduled job can be run in any one of the following modes:
   
   • Revoke: This mode is used when the application instance is deleted, but the provisioned accounts in the target system still exist. Using the Revoke mode deletes the accounts from the target system.
     
   • Delete: This mode is used when the target system no longer exists, and there are no traces of the accounts in Oracle Identity Manager. Using the Delete mode hard-deletes the accounts from all provisioning tasks and targets, and subsequently from Oracle Identity Manager.
     
   • Decommission: This mode is used when the target system no longer exists and the provisioned accounts cannot be revoked from the target system. Using the Decommission mode changes the account status to Revoke without keeping the accounts in Oracle Identity Manager in provisioned state.
    
6. Run the Catalog Synchronization Job scheduled job. This scheduled job identifies the soft-deleted application instances, and removes them from the catalog.

FA

OVM 2.2
Linux 5.5

DRAFT - Projeto W

Hyperion SSO com OAM (11.1.2)
http://docs.oracle.com/cd/E17236_01/epm.1112/epm_security_11121/frameset.htm?ch03s02.html
Clicando em Contents, localizado em cima à esquerda.

Oracle Transportation Management 6.2
Arquitetura
http://docs.oracle.com/cd/E20111_01/otm/acrobat/technicalarchitecture.pdf

Guia de Administracao
http://docs.oracle.com/cd/E20111_01/otm/acrobat/administration.pdf
- Informações sobre LDAP e SSO

Integracao com OAM(MY ORACLE SUPPORT)
- Note Metalink: Does OTM 6.2 Support Integration With OAM 11g [ID 1418374.1] Yes.

IMAGEM OAM11g

Documento para integração com o OAM (Está OAM10g, mas o procedimento é similar a outras aplicações que
se integram com o OAM 11g.) (MY ORACLE SUPPORT)

https://support.oracle.com/CSP/main/article?cmd=show&type=ATT&id=796594.1:oam_integration62

 Oracle eBusiness Suite
Fonte: https://blogs.oracle.com/stevenChan/entry/oracle_access_manager_11_11

Integração com o OAM 11g (MY ORACLE SUPPORT)
Integrating Oracle E-Business Suite Release 12 with Oracle Access Manager 11gR1 (11.1.1.5) using Oracle E-Business Suite AccessGate [ID 1309013.1]

Peoplesoft
http://coreidng.blogspot.com/

weblogic.properties

A) /home/oracle/metadata/export
from_loc = A
to_loc=A
metadata-files=B

No MDS:
B) /metadata/iam-features-requestactions/model-data/ModifyUserDataset.xml

Criar diretório em:
A+B(sem o xml)

- Exportar OIM_ORACLE_HOME
appserver = Instancia do WLS (oim_server1)

Para UDF novos

lookup.usr_process_triggers