The number of visitors are stable since the relaunch of crazyapple.com.
318 unique page visitors from 32 countries with ar average visit duration of more than 3:20 Minutes.
The users with the longest visit duration came from Brazil (00:20:28), Switzerland (00:12:03), Hong Kong (00:09:20), Russia (00:06:36) and Germany (00:05:11).
And – of course – the e20-120 exam questions was the most clicked content.
Table: TopTen Page Visitors
Land/Gebiet
Visitors
Pages/Visitors
Germany
75
3,26
United States
63
1,58
India
49
2,47
France
41
3,36
Australia
18
1,17
United Kingdom
15
3,4
Hong Kong
15
9,8
Canada
14
2,25
Philippines
14
1,25
Turkey
13
1
317
2,65
If you have any questions or good ideas please leave a comment below this article.
You can use external systems or technologies using a variety of transmission protocols (e.g. SMTP, FTP or Java Messaging Services).
Correlation identifiers are similar to the r_object_id attribute and implemented as a 32 character string containing hexadecimal letters.
The Process Integrator handel two types of communication:
Synchronous – a request is sent and the response is immediately received (no real time, negligible delay)
Asynchronous a request is sent, but the answer might never be received or will be received at a later time
Correlation ID vs. Correlation Set
Correlation ID explained using the example of the email activity.
The correcation idenifier can be embedded in the subject header of an outgoing email. The email inbound activity parsed the Subject header and extract the correlaction identifier.
The correlation identifier is embedded in the email subject. The correlation ID must be set in the Input Message Mapping window of the SMTP activity.The name of the correlation ID, in this example $transaction must be set in the email inbound activity.
Positve:easy and fast to use Negative:Subject header of the incomming email could only contain the correlation identifier and no other additional text. If the matching process instance is not found a correlation error occurs:
ERROR com.documentum.bps.email.inbound.runtime.EmailTask - Could not process the message for 'Process - simple_email_action Activity - Email Inbound - Step'
Listener: 'Process - simple_email_action Activity - Email Inbound - Step'
Workflow: 'null' - 'null'
Workitem: 'null'
Process: 'simple_email_action' - '4bde75d18000853d'
Activity: 'Email Inbound - Step' - '4cde75d1800082b2' - Activity Template: 'Email Inbound - Step'
com.documentum.bps.inbound.WorkflowNotAvailableException: Workflow not found
Correlation Set
Only process variables or properties of the SDT are selectable.
The correlation set can be defined in the Process Properties in the Advanced tab. The set can contain process variables and structured data taypes. Process Parameters or Package informations are not allowed and available.
The Process integrator will always attempt to use a correlation identifier (not correlation set). If the ID is not available the preconfigured correlation set will be used.
Remember: a correltion identifier in the email subject is not an effective way to match the correct process instance.
Best practice is to create a additional set of Process variables. One of these variables is named message_ID or transaction_ID and contains the internal identifier of the outbound SMTP activity. In the email inbound step the email attribute Reference will be mapped to the Correlation Set attribute transaction_ID (ref. screenshot).
Displayed the second page of the activity Inspector of the Email inbound activity. The attribute ‘Reference’ is mapped to the correlaction set attribute ‘transaction_ID’
Upgrading your Content Server on Windows Server OS
The current version of xCelerated Composition Platform (xCP) is version 1.5 (6.6 release). It is not possible to update the entire software platfrom 1.5 to 1.6 (6.7 release).
Note: Due to changes in the licensing of some 3rd party components that are used in the xCP Developer Edition, the 1.6 release has been delayed. Please watch this page for an announcement of its availability.
The first step is to upgrade the Content Server from the released version 6.6 to the current version 6.7 SP1. Here is the upgrade checklist with additional screenshots and comments.
checklist
Back up the repository.
Back up customized formats(dm_format objects)
Content Server 6.7 SP1 start installation
Run the consistency checker job or dmbasic syntax (optional, if you are not upgrading an new xCP installation)
Disable all jobs in the Documentum Administrator
Shut down the repository and the connection broker (docbroker) in the Server Manager
Shut down the Documentum Java Method Server services. Switch the start up method from automatic to manual to ensure that the services does not start automatically after a host restart.
Start the installation
install xPlore or FAST search engine (FAST is not supported)
Content Server 6.7 SP1 select search engine
select upgraderepository and docbrocker
Content Server 6.7 SP1 upgrade repository
don’t select create additional repository or docbrocker and finish the section
Content Server 6.7 summary information
finish installation, check install logfile in the source folder
restart the environment (check Java memory size in Windows Task Manager, check the Documentum Services in the Windows Services, check the log files in the new JBoss 5.1 folder)
stop the Application Server Service
deploy JBoss war files for Taskspace, Administrator etc. in the deploy folder
restart Application Server Service
install DAR applications (Taskspace, Administrator etc.) using Composer 6.7 DARInstaller
xCP 1.x compatible
