Enabling, Disabling, and Monitoring Logging for Oracle Internet Directory Garbage Collectors

Enabling Logging for Oracle Internet Directory Garbage Collectors If you enable logging for garbage collectors, then the directory server writes the information into a file in the file system. This information includes: The job identifier A job description of the garbage collector The number of entries purged The operation status The time stamp Any errors(…)

Modifying Oracle Internet Directory Garbage Collectors

 Modifying a Garbage Collector by Using Oracle Directory Manager To modify a garbage collector: In the navigator pane, expand in succession Oracle Internet Directory Servers, directory server instance, Garbage Collection Management, then select the garbage collector you want to configure. The Garbage Collector Window appears in the right pane. In the Garbage Collector window, enter the values for this garbage(…)

Change Log Purging in Multimaster Replication

Both replication and Oracle Directory Integration Platform use change logs to propagate information from a supplier directory to a consumer directory. All change logs are stored in the table ods_chg_log. In addition, replication change logs are stored in asr_chg_log. When the change log garbage collector runs, it purges change logs that are no longer needed by any(…)

Garbage Collector Entries and the Oracle Internet Directory Statistics Collector Entry

Garbage collector entries, each with attributes specifying how it is to behave, are located in the entry cn=purgeconfig, which is located immediately below the entry cn=subconfigsubentry. The Oracle Internet Directory statistics collector entry, with its attributes, is also located in the entry cn=purgeconfig, immediately below the entry cn=subconfigsubentry. Figure 26-2 shows the location of these entries.

How Oracle Internet Directory Garbage Collection Works

garbage collector operation that purges change log entries. The garbage collection process is as follows:   An LDAP client sends to the directory server a request for a particular garbage collection operation. The operation could be, for example, to purge the entries of tombstones, change logs, or audit logs. The directory server passes the request(…)

Oracle Garbage Collection Plug-in

Garbage collection in Oracle Internet Directory relies on a garbage collection plug-in that receives requests to manage garbage collectors. This plug-in is installed with Oracle Internet Directory, and is enabled by default. The entry for this plug-in is cn=plugin,cn=subconfigsubentry. This plug-in has three triggers: The DN of the plug-in trigger used to create a garbage collection(…)

Home Interface

The home interface defines the methods that allow a client to create and find an entity bean. The SavingsAccountHome interface follows: import java.util.Collection; import java.math.BigDecimal; import java.rmi.RemoteException; import javax.ejb.*; public interface SavingsAccountHome extends EJBHome { public SavingsAccount create(String id, String firstName, String lastName, BigDecimal balance) throws RemoteException, CreateException; public SavingsAccount findByPrimaryKey(String id) throws FinderException, RemoteException; public Collection(…)

Business Methods

The business methods contain the business logic that you want to encapsulate within the entity beans. Usually, the business methods do not access the database, allowing you to separate the business logic from the database access code. The SavingsAccountBean class contains the following business methods: public void debit(BigDecimal amount) throws InsufficientBalanceException { if (balance.compareTo(amount) == -1) {(…)

Finder Methods

The finder methods allow clients to locate entity beans. The SavingsAccountClient program locates entity beans with three finder methods: SavingsAccount jones = home.findByPrimaryKey(“836”); … Collection c = home.findByLastName(“Smith”); … Collection c = home.findInRange(20.00, 99.00); For every finder method available to a client, the entity bean class must implement a corresponding method that begins with the prefix ejbFind. The SavingsAccountBean class,(…)

EntityBean Interface

The Entity Beans interface extends the EnterpriseBean interface, which extends the Serializable interface. The EntityBean interface declares a number of methods, such asejbActivate and ejbLoad, which you must implement in your entity bean class. These methods are discussed in later sections. The ejbCreate Method When the client invokes a create method, the EJB container invokes the corresponding ejbCreate method. Typically, an ejbCreate method in an entity bean performs the following tasks: Inserts(…)