Connect Alfresco Content Services with SAP in less than 30 minutes!

• Protocol: HTTP
• IP-Address: Use the Public DNS name or the IPv4-address of the current EC2 instance (you can find it in your AWS console)
• Port: 8080
• Alfresco Share User: admin (lowercase)
• Alfresco Share Passwort: The current EC2 instance id (you can find it in your AWS console)

Example: http://<ec2-instance-public-dns-name>:8080/share

To get an overview about the pre-configured connexas content installation, just navigate to the connexas Administration Panel in Alfresco Share: Admin Tools -> connexas. There is one pre-defined SAP system configuration which uses an asterisk as name in section “SAP Content Repositories”. This means, in SAP you can choose any name for a content repository and also connect as many content repositories as desired. But it also means, with this pre-configured EC2 instance there is no additional data-replication is possible. If you want to test the connection from Alfresco to SAP, there is need to to adapt some more settings (detailed information are available in our configuration guide). The root folder in Alfresco for all documents arriving from SAP is “SAP_Documents” within a site called “connexas”. You can just click on the folder name to jump to the site directory immediately.

• Document Area: ArchiveLink
• Version No.: 0047
• HTTP Server: Public DNS name or IPv4-address of the current EC2 instance (you can find it in your AWS console)
• HTTP Port: 8080
• HTTP Script: alfresco/service/com/pernexas/archivelink

After creating the content repository, a certificate has to be send to establish a connection. This can be easily done in t-code OAC0 as well (use related mail icon). The certificate can only be enabled in Alfresco. To do so, login to Alfresco Share (see above), open the connexas Administration Panel, scroll down to the content repository (you’ve created before) and hit the “Enable” button. That’s it! The connection is now established and can be used.
Now, go ahead and create a new document type (t-code OAC2) and the related linking to the content repository (t-code OAC3) matching the required use-case. Then, open a business object and attach a document via the GOS menu -> “Store business document”.