BOOST 3. Beta1 Initial release as a standalone product see Hibernate Annotations changelog for previous informations Release Notes - Hibernate Search - Version 3. Parameter rather than o. Mit einem Experten sprechen. Thanks for helping keep SourceForge clean. X You seem to have CSS turned off. Briefly describe the problem required :. Upload screenshot of ad required :. These IDs are used to create file system paths in storage locations to ensure that they do not conflict with other repositories.

However, if you create two repositories to have same Repository ID and point to same file location path, they might overwrite each others' data. This is because, for a particular storage path, the system assumes that it has full access to that path which includes the Repository ID. Documentum Server installation creates the default content storage area called the data directory for storing content files. After the initial installation, you can add additional storage areas and the business rules for distributing content among them by using Documentum Administrator.

Ensure that the location you choose for the storage area has sufficient free space for the content files that will be added to it. On Linux, the port numbers can be any unused port numbers greater than Linux reserves port numbers up to for system use. Identify available ports to be used by Documentum Server and its components. Make sure none of the reserved ports are being used for other purposes. However, the information exchanged between them is encrypted. Determine which connection mode you want to use for the connection broker and the repository respectively.

Documentum Server has a number optional modules or extended features that require separate licenses. You activate a module by entering its license key in the Documentum Server configuration program. Once activated, you can enable the extended feature for a repository when you configure the repository. Identify which optional modules to activate during Documentum Server installation and configuration and obtain license keys for those modules.

Caution: If you plan to use remote key management for your repository, you must activate the Trusted Content Services TCS module before you configure Documentum Server. If the TCS license is not present, you cannot create a repository that uses remote key management, and you cannot enable it at a later time. Some of these optional modules, once activated, apply to all Documentum Server instances in an installation so that all the repositories can access the extended features; the others are individually activated for Documentum Server instances, which means extended features can only be enabled for repositories managed by the Documentum Server instance with the corresponding modules activated.

The three broad areas of enhancements that make up High-Volume Server are: — Lightweight system objects — Batch operations and currency scoping — Database Partitioning Note: Database partitioning option is not available while creating new repository during the Documentum Server installation.

You can create a SnapLock volume in one of two modes: Enterprise and Compliance. The difference between the two modes is that on the Compliance SnapLock volume, a default and minimum retention of 30 years is applied to the content files created in that volume.

Content Storage Services enables you to define business rules to govern where content files are stored. Once you activate this module, you can use the event-based retention capabilities out of the box. However, if you want to use this module to manage retained data stored on a Centera device, you need another license to use the event-based retention capabilities and hold capabilities on that device.

Documentum Server Fundamentals Guide and Documentum Server Administration and Configuration Guide contains more information on modules and instructions on how to configure and use them.

Pre-installation requirements and tasks Ensure that your system meets the system requirements and perform prerequisite tasks based on your installation plan before installing Documentum Server. Note: It is recommended that you apply the latest operating system,. NET Framework, and related component patches.

For example, operating system library updates,. NET Framework updates and so on. XWindows must be installed on the Linux hosts to run the graphical installation program. The xterm program may be installed in various locations depending on the operating system and software packages installed. A relational database management system is a prerequisite to installing Documentum Server. The database stores metadata of content objects in the Documentum Server repository.

For example, you can install Documentum Server on a Windows host and use a database installed on a Linux host. In a production environment, the database is almost always installed on a different host than the Documentum Server host for better performance.

On a Windows host, the installer updates the system path automatically. Regardless of the database you use with Documentum Server, obtain the database administrator's username and password.

You might need this information while configuring the repository. Documentum Server installation sometimes requires a restart of the computer. After the restart, installation does not proceed correctly unless the database starts automatically. Configure the database based on the results after profiling the database usage. Caution: Install the database in case-sensitive mode with row-level locking enabled.

If you installed SQL Server in case-insensitive mode, you need to reconfigure the database before you install or upgrade Documentum Server. Configure the database based on the results after profiling the database usage and by monitoring database reports such as AWR report, Oracle Alert log, Query execution plans, and so on.

The value of the variable must be set to an integer for example, 4 which is used as Degree of Parallelism DOP while creating indexes in Oracle database. INI to 7. INI to localhost. For example: — Use local for Linux domain socket connections only: local all all trust — IPv4 local connections: host all all No attempt is made to store new or updated rows according to their index order.

Open the postgresql. Enabling data partition in PostgreSQL database 1. Run the following command in IAPI:. Stop the Documentum Server. Start the Documentum Server. If none of the supertypes are partitioned, then you have to enable data partition for the corresponding type. Continue from Step 3 of the Enabling data partition in PostgreSQL database, page 96 procedure to create a partitionable type.

Tuning PostgreSQL database 1. Restart the PostgreSQL instance. Run the query to check index fragmentation: with indexBloat as. Ignore empty or small tables 8KB or few KB tables. The installation owner account is an operating system account with appropriate permissions to install Documentum Server and create repositories. The installation owner account may be a local account on the Documentum Server host or a domain account in the domain where Documentum Server is installed.

The account must be a member of the Administrators group on the local host. Documentum Server runs under the installation owner account. The installation owner can perform all administrative and maintenance tasks associated with Documentum Server and repositories. You can create an operating system account to use exclusively for Documentum Server installation and repository configuration.

You can use a single operating system account as installation owner for multiple Documentum Server installations on the network. The first character must be a letter. The installation owner password consist of letters, numbers, dashes, underscores, or periods. Installer checks for these rights and grants them if necessary.

The installation owner must have Full Control permission on the directories into which Documentum Server is being installed, including data and share directories. The installation owner must also have write permission on the directory from which installer is run. To support external password validation, set up a group account whose members are the installation owner, any other Documentum Server administrators, and repository owners.

This will be the group that owns the external password validation program. Documentum Server requires the installation owner's email address and SMTP server information to send email notifications to the installation owner.

During installation or upgrade, you need to provide this information and installer will attempt to connect to the SMTP server. Set up an email account for the installation owner and obtain the host name or IP address of the computer hosting the SMTP server Documentum Server can connect to. The repository owner account is a database user account that Documentum Server uses to connect to the database.

This account owns all objects in the database and gives Documentum Server access to the database tables underlying the repository. Each repository must have a unique repository owner. The configuration program automatically grants the account proper privileges.

Ensure that the repository owner has the Create Any Database privilege. The Resource privilege encompasses creating and maintaining database objects. The repository owner also must have permission to create any view, resource, and unlimited tablespace. The tablespace created by the repository owner for tables or indexes must be designated the default, while the standard Oracle temporary tablespace must be the default for any temporary tables that the repository owner creates.

The name of the temporary tablespace must be valid for the Oracle configuration used. The repository must also have the Select Catalog Role privilege. To use Microsoft Cluster Services, the repository owner must have an account in the domain in which you install the repository. Repository users are the end users in the repository. If LDAP authentication or inline password authentication is used, this is not a requirement. This method disables the Teredo Tunneling Pseudo-Interface.

This will provide the correct operating system runtime libraries for the Documentum Server and other utilities. In the installation owner's environment, set environment variables that identify the directories into which Documentum Server will be installed. The variables must be set in the installation owner's environment. You can create the Documentum Server installation directory before installing the server, or you can allow the installer to create the directory for you during installation.

If you allow the installer to create the directory, ensure that the directory name you provide during the installation matches the one specified in the environment variable. Symbolic links symlinks are not supported. Do not use them in the installation directory or any other environment variable used by Documentum Server. This restriction also applies to environment variables used to specify the database location.

However, the symbolic links for Java upgrade is supported. The name of the installation directory must not contain spaces. On Linux, you need to set certain environment variables in the installation owner's environment. If you do not use the Documentum Server configuration program, you need to manually set all environment variables.

Alternatively, set the variables in a file called by the. The services file must contain two entries for each repository running on a host. Manually create the service name entries in the services file before you install the Documentum Server. The repository does not have default service names or default port numbers.

The service name you put in the services file must be the same name you will provide during repository configuration, which is then used to create the server. The service name for the repository can be the same as the repository name, but this is not required. The services file must include entries that designate two consecutive port numbers: one for native connections, and the other for secure SSL connections.

In the following repository service entries example, repository service is named repo1. If you have multiple repositories on a single host, create a services file entry for each repository. Ensure that the repositories use different names and port numbers. Take a copy of existing policy files from the Java home directory and save it in another directory. A connection request through SSL waits for a random number to be created and a delay is noticed. To avoid the delay, you can enable or disable the random generator on the Linux machine.

The repository owner database user does not need to have a Windows account. Oracle database aliases TNS aliases are defined by entries in the tnsnames. Configure the tnsnames. After you create the alias, test the alias by connecting to the Oracle database.

Entries in the tnsnames. If the first entry in the tnsnames. Ensure that the first entry in the tnsnames. Documentum Server supports only those features that are natively supported per the Documentum Server design. If it does not, an error occurs.

You must provide the read write permission. The server host locale and the server code page need not be same. If the host locale is set to French, a client that connects to the Documentum Server without specifying a client locale is served French data dictionary labels.

If the host locale is one of the languages supported by Documentum, the data dictionary information for that locale is loaded. Otherwise, the server defaults to loading the English data dictionary information. Installing additional data dictionary information can affect server performance, and Documentum only supports the languages that are shipped with Documentum Server.

Preparing for remote key management You can upgrade repository to add remote key management RKM support any time. When you create a repository, you can choose to manage the repository encryption keys locally, or to manage them with a remote key management server. For local key management, the encryption keys are encrypted and stored in the database used for the repository metadata.

In releases prior to 7. For remote key management, the encryption keys are stored in a remote key management server. Beginning with release 7. The remote key management can be enabled for all the repositories during the installation or post-installation. If you plan to use remote key management, the crypto policy key on RKM must match the key created for Documentum Server. DPM uses an X.

In the DPM administration application, a repository that is using remote key management appears in the list of DPM clients. High-latency connections will cause performance problems and may cause timeouts. If you attempt to start a remote key management Documentum Server, and the DPM server is not available, Documentum Server will fail to start.

The proximity must be less than You will set up DPM to support remote key management for a repository by specifying DPM identities, an identity group, and key classes. Identities represent Documentum Server instances, an identity group represents a repository, and key classes represent the repository keys.

DPM uses the concept of an identity. In the context of Documentum Server, every Documentum Server instance process is a separate identity. In order to use remote key management, you need to configure identities in DPM and create or obtain a unique certificate for each identity.

The certificate is used to authenticate a request for keys from a Documentum Server instance. For example, one common scenario is to have Documentum Servers on a single host controlling multiple repositories.

Server A is one identity, and Server B is a second, separate identity. Another common scenario is two Documentum Servers on two different hosts serving a common repository. ServerC1 and ServerC2 are two separate identities. Separate, unique certificates are used to authenticate requests for keys from ServerC1 and from ServerC2, even though DPM returns the same RepositoryC keys for either request.

Another scenario, is to have multiple Documentum Servers on one host serving a common repository. Again, each Documentum Server is a separate identity. Server D1 requires a unique certificate for its identity, and Server D2 requires a unique certificate for its identity. In the context of DPM, identity groups are a way of grouping related identities together. For remote key management using DPM, we use identity groups to keep all the identities used for a repository together.

For this reason, it is recommended that you name the identity group with the name of the repository it represents. From the examples, we put the identities for Server C1 and Server C2 into an identity group. We'll call that identity group Repository C so we know it contains all the identities used for Repository C.

It contains all the identities for Repository D. In the context of remote key management for Documentum Server, the DPM key classes contain the keys for the repository. Each repository has its own set of keys managed by DPM. When keys are created, they are associated with an identity group and any identities in that identity group can access the keys. That is why we create an identity group for each repository, and why we associate the identities for each Documentum Server that serves that repository with that identity group.

In that way, any Documentum Server that serves that repository can get the repository keys. In the earlier examples, the key classes for Repository C are associated with identity group Repository C. Both Documentum Servers can access the keys for Repository C.

In the same way, the key classes for Repository D are associated with identity group Repository D, and the two Documentum Server identities, for Server D1 and Server D2, are associated with identity group Repository D. It is the master key for Documentum Server. It is used to access all the other keys.

The names of the key classes in DPM must be unique, so it is recommended that you name them for the repository that uses them. Never use the same key class name for different repositories. Each identity requires its own certificate. Before you configure a repository for remote key management, you must obtain a certificate for all the identities you need for your particular installation.

You will supply the certificate when you create an identity in DPM, and supply that same certificate when you configure a Documentum Server that corresponds to that identity. You will also need the root certificate for the certificate authority of the identity certificate when you configure Documentum Server.

Obtain the certificate from your preferred certificate authority. Generally, you will get versions of your certificate in a few different formats from the vendor. Each format uses a different file extension.

When you create the DPM identity, you will use the certificate with the. When you configure Documentum Server, you will use the certificate with the. Create the identity group for the repository. Enter repository for Name. Select Save. Create the identities for each Documentum Server for the repository. Select the one identity group named repository created earlier for Identity Groups. For Roles, select Operational User.

For Identity Certificate, select Browse to navigate to the. Repeat the steps a to f to create any additional identities needed for this repository. Create the DBK key class for the repository.

Select the identity group named repository created earlier for Identity Group. Select Next. For Class Attributes, select Next do not set any class attributes. For Attribute Specifications, select Next do not set any attribute specifications. Review the new key class values in the following table, then select Finish. Set all the other values for these two key classes the same as in the previous step. Create the PPK key class.

After you have created the identity group, the identities, and the key classes, DPM is ready to support remote key management for a repository. During repository configuration, if you have installed a TCS license, you will have the option of providing the information required for the repository to use remote key management. Preparing installation package Download the Documentum Server software for your operating system and database.

Ensure that you have execute permission on the serverSetup. In addition to the existing connectivity options, a new connectivity mode is available. In this mode, certifications are used to verify SSL servers. In the OOTB setup, the secure mode will continue to use anonymous mode by default. In the anonymous SSL mode, certificates are not used. In addition, both end parties are trusted and not verified. Note: A trust store is a file containing certificates from trusted servers.

No verification is provided to the SSL clients. Certificates are not provided. You must purchase certificates from a Certificate Authority CA. Perform the following steps to procure a certificate: 1.

You will receive certificate signed by a CA and a private key with CA certificate chain. Such certificates are known as self-signed certificates and are generally used for testing. The keystore must be in the PKCS 12 format. If certificates are in the PKCS 12 format, no additional configuration is required. Proceed to configure the connection broker, server, and DFC. The PKCS 12 keystore is provided with a password for security.

If the CA has provided the certificate in this format, the password will also be available. Note: This is similar to how the Database password is stored on the Documentum Server machine. If the password is encrypted, it will be specific to the Documentum Server where it was encrypted.

It cannot be copied to any other Documentum Server that has a different aek. JKS is a widely-used specialized keystore format standardized by Java. Note: The keystore is a file containing the certificate and private key. The trust store contains all certificates that the SSL client can trust. The certificate list includes the list of all root and intermediate CAs. It is optional to store the leaf certificates connection broker certificate if you obtained it from CA. The certificate chain is adequate to validate the leaf certificate.

If the certificates are self-signed and do not include a certificate chain, then all the certificates must be stored in the trust store. However, if the certificates are self-signed and include a certificate chain, then all certificates, except the leaf certificate, must be stored in the trust store.

Configuration is a one-time activity. The connection broker works as a SSL server. It requires details of the keystore and the keystore password. RSA library supports these ciphers. Note: The ciphers that work depends on the Java version and it's capabilities. Copy the certificates from primary Documentum Server to secondary Documentum Server. It requires details about the keystore, keystore password, and trust store.

Documentum Server settings are stored in the server. It requires details about the trust store. DFC settings are stored in the dfc.

Parameter Name Description dfc. Sample: dfc. During the configuration of connection broker and Documentum Server, the installer will prompt you for Certificate details which will be used for configuration. All the components in a setup must use a consistent secure mode. For example, the Documentum Server, connection broker, and DFC must be in the anonymous default mode or all components must be in the certificate mode.

I'm trying to export data from some of my tables, but I'm getting sql exceptions on invalid column name. I've traced the problem to the fact that I have the same table name 'procedure' used in two different schemas. The getColumns of DatabaseTableMetaData is picking up the colunms from both schemas and combining them to create the select statement, but since the tables are defined differently, I get the invalid column error.

I actually connect to the db as one of the schema owners, so I had hoped it would only pick the tables owned by that id. Seems like there should be a way to set a schema name for this whole process. Has anyone looked at this? I tried qualifying the table names, but that seemed to cause other errors. Otherwise, I'm sure I can tweak the code to allow specification of single schema. I'm brand new to dbUnit, so I don't know if it's possible to contribute code or if everything is being done by Mr.

Cary Mader. You need to have the JDBC 2. I need to add something about this in the DbUnit documentation. The ant build file distributed with version 1. I created a new build file from scratch, which is available from the CVS repository. Subject: [dbunit-user] dbUnit build fails I've tried to run ant build tasks for dbUnit v1. They fail without additional manipulation of build. Is this intentional? McAuley em I have fixed the problem. It was very simple in the end but took a little time for me to figure out.

This pool of connections was under the control of a transaction manager and therefore any operations do not necessarily commit straight away. The two choices I had were to setup a second datasource, not under transaction management, or to run the command: connection. A very simple solution, and probably highlighting my lack of experiences with databases! All the best, Tim. I've tried to run ant build tasks for dbUnit v1.

Yes, but what else is DbUnit supposed to do? In order to refresh the data, it needs to check for rows that already exist so that it can update them. In the absence of a primary key, how can it check for row existence? I suppose DbUnit could assume that if a row exists with all the same values, then it doesn't need to insert it, but if you didn't want duplicate data in your table, wouldn't you have specified a primary key?

Is there some reason you can't define a primary key for the table? The key might include all columns. Has anyone else run into this problem? There is not a primary key identified on the view. Hi, In a follow up to my post last night, I seem to have narrowed down the problem a little but am still at a loss. Basically dbunit does not seem to like using the JBoss database pool. Have a look at the four methods I tried below and see if anything makes sense.

Only method 2 works. Any ideas? Tim PS When I first saw this I thought I had solved my problem, but it didn't seem to work. DataSource ctx. Driver" ; javax. As pointed out by Jeremy, the clearParameters call was not necessary. I commented out the call in the DbUnit code. The modification is available from the CVS repository since today. If anybody has solved this problem or even knows exactly what it is - drivers?

I developed DbUnit with Oracle and never had this problem. Hi, I am trying to get Postgres working with JBoss and Postgres and have some weird behaviour so far. Maybe someone could point out what's going wrong. This worked okay. Next I setup a test case for use within JBoss using cactus. The code of it is below. I am using the database connection pool used by JBoss and can currently retrieve the names of the columns in the database ok.

The test does not return any errors and seems to have run okay. No information is put into the database. The tables are already setup by JBoss. Initially I had to get the latest stable JDBC driver for postgres due to an error saying that the batch was empty and it had nothing to do, but that seems to have been resolved with the new drivers.

If anyone has any ideas, I'd appreciate hearing them. All the best, Tim Setup JBoss You must run automated tests only on dedicated databases since your tests will thrash your existing data. This means one database per developer and one more for nightly build integration.

You need another database for your "independent testers" which is the "populated development database" suggested by Richard. It's absolutely true. Briefly describe the problem required :.

Upload screenshot of ad required :. Jul 3. Aug 1. Sep 9. Oct 3. Jan 1. Feb 4. Mar 1. Apr May 2. Jun 5. Aug Sep Nov 2. Dec Jan Feb Mar May Jun Jul Oct Nov 6. Jan 5. Nov Jun 6. Jan 9. Mar 7. Apr 2. May 5. Jul 6. Sep 4. Jan 3. Mar 6. May 1. Aug 2.