This is a recommendations checklist to ensure that you ( and your Macintosh Server ) are fully prepared for your Extensis Portfolio installation. Please ensure that you have read this document in its entirety prior initiating your Portfolio installation.
HARDWARE SPECIFICATIONS
1. Recommended Apple Macintosh Server hardware specifications:
|
Total Assets |
Users |
CPU Cores |
RAM |
BOOT |
DATA |
Drive Speed |
|
< 50,000 |
3 |
4 |
16GB |
100GB |
125GB |
60 MB/s |
|
< 500,000 |
5 |
4 |
16GB |
100GB |
250GB |
180 MB/s |
|
< 1 Million |
10 |
8 |
16GB |
150GB |
500GB |
250 MB/s |
|
< 5 Million |
25 |
12 |
24GB |
500GB |
2.5TB |
250 MB/s |
|
< 10 Million |
50 |
24 |
32GB |
1TB |
5TB |
250 MB/s |
Note that this table assumes 3(three) total active catalogs per Portfolio instance.
OPERATING SYSTEM
2. [_] Apple Macintosh OSX versions 14.x through 10.11.x are compatible with Portfolio 3 installations. Ensure that you have performed all of the latest Apple Macintosh Server Updates and have rebooted the server prior to your scheduled Portfolio installation.
LICENSING
3. [_] Portfolio requires a direct outbound connection ( h ttps://cwsg.extensis.com via TCP Port 443 ) to initially establish product licensing and note that Web/Security proxies are not supported. Please ensure that the assigned Extensis Account Administrator is able to properly authenticate to the Extensis Website ( https://secure.extensis.com/loginpage ) and that all purchased Portfolio product modules appear within the My Products.
OUTBOUND INTERNET URLS
4. [_] Outbound Internet URLs :
|
Description |
URL |
Notes |
|
Portfolio Admin - RTI ; Portfolio Web / Desktop - ReachOut |
|
Optional |
|
Portfolio Admin - Licensing |
|
Required to initially establish product licensing. |
|
Portfolio Admin - Diagnostics |
https://extensis-portfolio-diagnostic-u ploads.s3-us-east-1.amazonaws.com |
Required for diagnostic reporting functionality. |
|
Portfolio Web / Desktop - Smart Keywording |
|
Required for Smart Keywording functionality. |
|
Portfolio Web / Desktop - Basemap |
http://server.arcgisonline.com ; http://services.arcgisonline.com |
Required for geospatial functionality. |
|
Portfolio Admin / Web / Desktop - Help |
http://helpdocs.extensis.com/portfoli o/<version>/<interface>/<language>/C ontent/Home.htm |
Required for Help functionality ( Client Side ). |
|
Portfolio Web / Desktop - Feedback |
|
Required for feedback functionality ( Client Side ). |
FILE SHARING PROTOCOL
5. [_] Portfolio does not fully support “Watched Folders” residing on DFS ( Distributed Files Shares ). Portfolio will be able to initially ingest assets stored on DFS , but will not immediately recognize files or folder changes due to protocol differences in DFS versus standard SMB 0.
-
- Watched Folders residing on DFS shares will need to be configured for a timed synchronization interval ( g. “Every 1 Minute” ).
RAM
6. [_] Apple Macintosh OSX is extremely sensitive to aftermarket ( non Apple installed ) Although OSX may boot properly, Portfolio’s ElasticSearch database and MediaEngine will not operate properly on a server that has memory issues. Please ensure that you have a minimum of 16GB of memory installed and have verified that there are no memory issues, prior
to initiating the Portfolio installation process. Verify that the “Status” for all installed memory is “OK” within OSX’s System Information utility ( “Applications” > “Utilities” > “System Information” ; “Hardware” > “Memory” ). If the Portfolio installation target has less than 16GB of installed memory and/or the System Information utility is reporting “Memory” > “Status” : “ECC Errors”, do not proceed with the Portfolio installation.
DRIVE SPACE
7. [_] Portfolio must be installed on the “boot” drive ( typically named “Macintosh HD” ). Ensure that you have enough available drive space for the OSX Operating System, Extensis Portfolio application ( ~1GB ), Extensis Portfolio Catalogs, supplemental software, and various future A 100 GB boot partition is the recommended bare minimum for new Portfolio installs on OSX.
8. [_] For Portfolio 3 running on OSX version 11.x ( or higher ) , the various folder settings with the Portfolio Admin interface must be configured for internal hard drives. Configuring any of the various folder settings with the Portfolio Admin interface for “attached” storage devices (
e.g. a Promise RAID unit attached via Thunderbolt ) will likely result in "ghost" / "phantom" / "duplicate" mount points within "/Volumes" ( h ttps://support.apple.com/en-us/HT203258 ).
9. [_] Portfolio automatically creates “Preview” files (stored as “.jpg” or “.mp4” within a special folder structure) which are used for rapid, full-screen viewing of documents, images, and video Previews are typically stored on the same file server where the original assets also reside, but must be located in a predetermined folder structure outside of any of your original asset folder structures. Please ensure that you have allotted enough drive space on your file server for Portfolio Preview files.
- A Portfolio Catalog consisting mostly of document and images will consume approximately 20GB of drive space per 100K items for Previews (using the default preview setting of 1600 pixels).
- A more video centric Portfolio Catalog (making use of the default setting of 480p video previews) can easily surpass 500GB of drive space (or more) per 100K items for Previews.
10. Immediately after installation, the location of “The Vault” ( Portfolio Admin > Global Settings > Portfolio Vault Configuration > Portfolio Vault Folder ) should be changed from "/Library/Extensis/Portfolio/mongodb/" to an alternate ( non-boot drive ) location ( e.g. "/Volumes/Example RAID HD/Extensis Portfolio VAULT/” ).
- * The location of the Vault must appear to OSX as an internal hard drive ( see item 6 above) and the drive speed should not fall below 60 MB/s.
11. [_] Portfolio has the capability to automatically create scheduled Backup Archives (stored as “portfolio_yyyy-mm-ddThh-mm-ss.xxxZ.zip”) which can be used for rapid restoration.
Backup Archives are typically stored on the same file server where the original assets reside, but must be located in a pre-determined folder structure outside of any of your original asset folder structures. Please ensure that you have allotted enough drive space on your file server for your Portfolio Backup Archives.
- * A Portfolio Backup Archive will consume approximately 25GB to 4GB of drive space per 100K total items.
- * Portfolio’s internal backup routine does NOT backup the contents of the Vault.
12. An example drive configuration / folder structure for initially Cataloging a grand total of ~ 50,000 original assets ( consuming ~ 1TB of drive space ) would be as follows :
“Macintosh HD” ( Boot ) 250GB ( Macintosh OSX 10.11.x, Portfolio base + logs + work folders )
“Data RAID HD” ( Data ) 2TB
\/_/ - ASSETS ( Shared ; Originals - Portfolio Watched Folder based Catalogs )
\/_/ - Extensis Portfolio Backups
\/_/ - Extensis Portfolio Logs
\/_/ - Extensis Portfolio Previews
\/_/ - Extensis Portfolio VAULT ( Originals - Portfolio Vault based Catalogs )
\/_/ - Extensis Portfolio Work
DRIVE SPEED
13. [_] “Enterprise Class” hard drives typically benchmark at 180 - 250 MBps (or faster) and this is the expectation for new Portfolio installationsThe following OSX Terminal commands will test both the WRITE and READ speeds of the boot drive:
WRITE (MB/s)
dd if=/dev/zero bs=1024k of=tstfile count=1024 2>&1 | grep sec | awk '{print $1 / 1024 / 1024 /
$5, "MB/sec" }'
READ (MB/s)
sudo purge && dd if=tstfile bs=1024k of=/dev/null count=1024 2>&1 | grep sec | awk '{print $1
/ 1024 / 1024 / $5, "MB/sec" }' && rm tstfile
14. [_] Ideally, the assets that Portfolio is going to be cataloging should appear as a locally attached drive (e.g. a physically attached drive array or a SAN share attached to the Portfolio via Fibre Channel). If the original assets (files) that Portfolio is going to be cataloging do not appear as residing locally to Portfolio itself (e.g. a share residing on a SAN located elsewhere on the Local Area Network), ensure that Portfolio has 1000 Mbps or greater network connectivity and Read/Write/Modify access to these assets via SMB.
-
-
-
- If you intend to create one or more Portfolio Catalogs which are “watching” file structures of greater than 200,000 files, it is strongly recommended that the files appear as residing on locally attached drives to Portfolio itself. Attempting to “marry” a Portfolio Catalog to extremely large + complex folder structures (greater than 500,000 files) via AFP or SMB over your corporate LAN/WAN can result in sluggish “ingest” performance as well as add considerable (and constant) network “chatter”.
-
-
15. [_] If the original assets (files) that Portfolio is going to be cataloging reside on a standalone NAS device (e.g. a Drobo unit), note that sluggish read/write access (less than 60MBps/480 Mbps) will have a dramatic impact on various operations within Portfolio (cataloging, batch conversion, video transcoding, metadata embedding, ). If you intend to have your Portfolio catalog assets residing on a standalone NAS device, please ensure that you have thoroughly tested the share access speed between your NAS device, Portfolio, and your various user workstations prior to proceeding with your Portfolio installation.
NETWORKING
16. [_] Extensis Portfolio Suite LAN/WAN/Internet Firewall Considerations:
Portfolio makes use of the following TCP Listeners:
|
TCP Port |
Description |
|
8090 |
Portfolio Web / Desktop / Flow / API |
|
8091 |
Portfolio Administration |
|
9443 |
Portfolio Web / Desktop / Flow / API – SECURE – [ OPTIONAL; requires internal SSL Certificate installation; see item 18 ] |
|
9453 |
Portfolio Administration – SECURE – [ OPTIONAL; requires internal SSL Certificate installation; see item 18 ] |
|
9877 |
Portfolio Media Engine – [ OPTIONAL ] |
NetPublish Server makes use of the following TCP Listeners:
|
TCP Port |
Description |
|
8085 |
Portfolio NetPublish |
|
8095 |
Portfolio NetPublish – SECURE – [ OPTIONAL; requires internal SSL Certificate installation; see item 18 ] |
File Services make use of the following TCP Listeners:
|
TCP Port |
Description |
|
445 |
SMB – [ OPTIONAL ] |
|
548 |
AFP – Apple (Macintosh) Filing Protocol |
17. [_] Firewall “Port Forwarding” considerations for Web Client and/or NetPublish users requiring access via the Internet:
|
TCP Port |
Description |
|
8085 |
Portfolio NetPublish |
|
8090 |
Portfolio Web / Express / Flow / API |
|
8095 |
Portfolio NetPublish – SECURE – [ OPTIONAL; requires internal SSL Certificate installation; see item 18 ] |
|
9443 |
Portfolio Web / Desktop / Flow / API – SECURE – [ OPTIONAL; requires internal SSL Certificate installation; see item 18 ] |
SECURITY
18. [_] If your Corporate T. policy requires access to network resources via secure HTTPS (instead of HTTP), note that Reverse Proxy ( Apache, Microsoft IIS, NGINX, etc. ) is the recommended method for maximum flexibility + ease of SSL certificate management :
Example Reverse Proxy : NetPublish Website
https://images.example.com/website_name >> http://10.1.1.11:8085/website_name
Example Reverse Proxy : Portfolio Web / Express / Flow / API
https://images.example.com >> http://10.1.1.11:8090
★ Extensis Portfolio — Internet Access : Firewall + Reverse Proxy Considerations
19. [_] If your corporate T. policy requires a resident anti-virus scanner to be installed on the Apple Macintosh server where Portfolio will also reside, consider installing the anti-virus application after Portfolio has been successfully installed and tested. If installing anti-virus after Portfolio Server is not possible, you will need to completely disable the resident Anti-Virus scanner prior to the Portfolio installation. Also, after installing resident anti-virus, the Portfolio directories may need to be excluded from the resident scans:
https://help.extensis.com/hc/en-us/articles/115007401228
REQUIRED SUPPLEMENTAL APPLICATIONS
20. [_] Ensure that the latest version of Google Chrome ( http://www.google.com/chrome/ ) has been installed and that Chrome’s built-in instance of the Adobe Flash Player has been updated ( chrome://components/ ) .
Google Chrome Offline Installer ( 64bit )
https://enterprise.google.com/chrome/chrome-browser/
-
- Download the Chrome DMG for Mac
Adobe Flash - Google Chrome – PPAPI – Offline :
https://fpdownload.macromedia.com/pub/flashplayer/latest/help/install_flash_player_osx_ppapi.dmg
As an alternative to installing Google Chrome , you may instead choose to install Mozilla Firefox
along with a separate instance of the Adobe Flash Player :
Mozilla Firefox Offline Installer ( 64bit )
https://download.mozilla.org/?product=firefox-latest-ssl&os=osx&lang=en-US
Adobe Flash - Mozilla Firefox – NPAPI – Offline :
https://fpdownload.macromedia.com/pub/flashplayer/latest/help/install_flash_player_osx.dmg
21. [_] Additional helper application installers (Download — Do Not Install):
Adobe DNG Converter:
http://www.adobe.com/go/dng_converter_mac
EXTENSIS INSTALLERS & DOCUMENTATION
22. [_] Extensis Portfolio installers and documentation (Download — Do Not Install):
Portfolio 3 (v 3.6) Macintosh
https://bin.extensis.com/portfolio/Portfolio3-M-3-6-2.zip
Portfolio Desktop Client (v 3.6) Macintosh
https://bin.extensis.com/portfolio/Portfolio3-Desktop-M-3-6-2.zip
Portfolio Flow - Android
http://play.google.com/store/apps/details?id=com.extensis.portfolio.uploader
Portfolio Flow - iOS
https://itunes.apple.com/us/app/portfolio-flow/id731629362?mt=8
Portfolio Documentation
https://www.extensis.com/support/portfolio-3/
POST-INSTALLATION
23. [_] The Portfolio Administration interface makes use of a small PostgreSQL database to keep track of the various Portfolio Users, Catalogs, and Catalog After Portfolio has been successfully installed, be prepared to modify the “/etc/hosts” file to ensure that PostgreSQL is able to function without issue. The modification process is outlined in detail via the following Extensis KB Article: https://help.extensis.com/hc/en-us/articles/115007397848-Administrator-login-does-n ot-work-after-installing-Portfolio-Mac-
24. [_] The Portfolio MediaEngine currently requires an active user session to properly process files. To avoid Cataloging issues, ensure that there is an active session logged on at all times. For OSX versions 10.12.x and below , selecting “Application” > “Utilities” > “Keychain Access” ; “Preferences…” > “Show keychain status in menu bar” will allow you quickly lock the session by simply clicking the lock icon within the OSX menu bar and then selecting Lock Screen. For OSX versions 10.13.x and higher , screen locking can quickly be enabled by simply clicking the Apple icon and then Lock Screen.