Does Archivelink need port 445 (SMB) Into OnBase, or just http over 80?

[Joe_Pineda]

When SAP creates a document in OnBase via Archivelink, the SAP program uses an http call into OnBase. But, is port 445 (SMB) also needed? Does SAP actually need to move the file from wherever it is into OnBase? Or is the OnBase document the result of only an http call that OnBase "decodes" from a binary string or something like that?

I think SAP calls the CreateWorkItem method in OnBase Archivelink, but I don't have visibility into that method to know if there is an actual file move from a source folder into the OB diskgroup volume.

[Bakau_Onafuwa · Accepted solution]

Hi Joe,

Port 445 is not required (to be opened) for OnBase ArchiveLink to work; you only need either the port for HTTP / HTTPS  to be opened for ArchiveLink (depending on the port configuration in the TCode: OAC0).

Based on your configurations in SAP,  the SAP ArchiveLink functionalities integrates with OnBase ArchiveLink; this integration allows attachments (from SAP Business Documents e.g. FB60 - Invoices) to be sent to OnBase for archiving. 

OnBase stores / archives the attachments in the appropriate disk group per your configuration.

Thank You

[Bakau_Onafuwa · Accepted solution]

Hi Joe,

Port 445 is not required (to be opened) for OnBase ArchiveLink to work; you only need either the port for HTTP / HTTPS  to be opened for ArchiveLink (depending on the port configuration in the TCode: OAC0).

Based on your configurations in SAP,  the SAP ArchiveLink functionalities integrates with OnBase ArchiveLink; this integration allows attachments (from SAP Business Documents e.g. FB60 - Invoices) to be sent to OnBase for archiving. 

OnBase stores / archives the attachments in the appropriate disk group per your configuration.

Thank You

[Brian_Karcher · Accepted solution]

Joe, to add some more info: "Does SAP actually need to move the file from wherever it is into OnBase?"  No. The files are static in OnBase. When our users attach files from SAP, the file is marked as "archived".

"Or is the OnBase document the result of only an http call that OnBase "decodes" from a binary string or something like that?" Yes it is only via http (or https) as Bakau mentions. Viewing the document is essentially like DocPop-- a stream of bytes over http.