Best Of
Re: Migration from one S3 object storage to another S3 storage
Since objects accessed via S3 is through url, you should be able to copy the contents to another bucket without issue (this is what migrate_content job would do). Before you actually do the copy, I would read the Documentum Admin (DA) guide on how to configure a new S3 store object from within DA. It will ask your for all the relevant bucket information for bucket c. After you copy the objects over bucket c, you will need to update a_storage_type for all the documents that are point to bucket B to point to bucket C. Note this attribute stores the name of the storage object created in DA (not necessarily name of bucket C).
Curious though, why are you creating a new bucket to begin with? You should be able to change the S3 storage type on existing bucket.
Curious though, why are you creating a new bucket to begin with? You should be able to change the S3 storage type on existing bucket.
Re: Default click Overview page
This is where you can Enable Document Overview Page when users clicks on a document Name - ?func=admin.documentoverview
Uldis
1
Re: Unable to connect from Composer 7.3 to Content Server 7.3: "Server communication failure"
I had the same issue and found it is due to modified java security file at jre/lib/security/java.security. Once I restored to the default values, composer started working.
Check the JRE used by composer and ensure that the content of java.security file has default values.
In your case, I am expecting one or more of the below keys have been modified to prevent anon ciphers or other ciphers used in secure communications. Just restore the java.security file and retry again after restarting composer.
jdk.certpath.disabledAlgorithms jdk.jar.disabledAlgorithms jdk.tls.disabledAlgorithms (most likely this key)
Re: Run job two times a day
Two times per day but within minutes of each other? That's a strange requirement. Can you explain why you need this?
One solution I can think of is to make a copy of the dm_LDAP job and schedule both to run once per day, but the second one a few minutes later than the other one. Of course, there's no guarantee that the first one will be finished before the second one starts. You may also want to look at job sequences.
Re: Run job two times a day
We actually do something similar. We run LDAP sync job once a day and then run a custom job (10 mins afterwards) that modifies the newly created user objects to enable them to use customized SSO profile. Since my client doesnt have a need to create user accounts more than once a day, any updates that our custom job doesnt catch the first day, will be caught the second day.