System requirements

The use of the Objective 3Sixty platform requires specific software be installed on your system in order to run. Also, your system must have sufficient hardware to perform most efficiently. It must at the least meet the minimum hardware requirements listed below to conduct integrations.

Hardware requirements

3Sixty performance is based on a number of factors:

• Number of CPUs and speed

• Network bandwidth and latency

• RAM assigned to the operating system and 3Sixty (Tomcat) itself

• Hard drive disk speeds and latency

3Sixty uses a database for configuration, job state, and auditing data. Auditing data can also be configured to go to a log file.

Finally, 3Sixty will be integrating 2 or more products. Performance will be determined by the above factors, but also by the performance of each system being integrated. Note: 3Sixty is an I/O intensive application and therefore should be provisioned accordingly. Recommend SSD or NVMe based back end storage with enough capacity to index the entire contents of the source data.

Software requirements

Following are the software requirements to run Objective 3Sixty.

*Required to install and run 3Sixty				*Only needed if using SSO			Only needed if using Remote agents	Only needed if using 3Sixty RAG
3Sixty	Oracle	Tomcat	MongoDB	SCIM	Rabbit MQ	AOE	SDK	3sixty RAG	Remote Agent - 3sixty RAG	Python
Version 5.2.x	JRE 17+	Version 10	Version 7.x	Version 2.0.x	Version 4.0.x	Version 4.1.x	Version 1.8.x	Version 1.1.x	Version 1.8.x	Version 3.11.x
Version 5.0.x	JRE 17+	Version 10	Version 7.x	Version 1.0.x	Version 4.0.x	Version 4.1.x	Version 1.2.x
Version 4.5.x	JRE 17+	Version 10	Version 6.x	Version 1.0.x	Version 4.0.x	Version 4.1.x	Version 1.2.x
Version 4.4.x	JRE 17+	Version 10	Version 4.x	Version 1.0.x	Version 4.0.x	Version 4.1.x	Version 1.1.x

Network and firewall requirements

• For 3Sixty Admin:

  • Listen (TCP) Ports 80 and/or 443

  • Communicates with MongoDB on (TCP) ports 27017, 27018, & 27019

  • Communicates with Discovery on (TCP) port(s) 443 and/or 8443

  • Optional: Communicates with Active Directory on ports: (TCP, UDP) 445, (TCP, UDP) 88, (UDP) 389, (TCP, UDP) 53

  • Optional: Communicates with LDAP on (TCP) 389, (TCP) 636

  Note:  Communicates with CMIS and/or ECM platforms using vendor documented ports and procedures.

• For Discovery:

  • Listen TCP Ports 443 and/or 8443

  • Communicates with 3Sixty Admin on (TCP) ports 80/443

• For MongoDB:

  • Listen Ports 27017, 27018, & 27019

Certificates

For 3Sixty Admin and Discovery refer to Tomcat SSL for documentation on how to generate and enable SSL certificates.

Access and permissions

For 3Sixty Admin and Discovery:

• Windows Local or Domain user with Read/Write permissions to Install and Tomcat Temp directory

• Linux Local or LDAP user with Read/Write permissions to Install and Tomcat Temp directory

Passwords and encryption

• Database password

  • In the simflofy-global.properties file there is an option to encrypt the database password: simflofy.encrypt.db.passwords=false

  • Setting this to true will encrypt passwords using 3Sixty's default encryption.

• Connector passwords

  • All fields marked as passwords in the 3Sixty UI are encrypted in the database and never returned to the User Interface.

• Encryption strength

  • By default, 3Sixty will use whatever the default encryption strength is for Java. If you wish to use the more secure AES 256, you will need to do 2 things:

  • In the simflofy-global.properties file, set this setting: simflofy.aes256.encryption=true

  • Install the JCEK policy file. JCE Unlimited Strength Jurisdiction Policy Files 7 Download

  • For 256 you need the unlimited Strength Jurisdiction Policy file below. In some countries you will not be able to use this file. AES-256 Encryption with Java and JCEKS

Supported browser platforms for client access

The client uses a web browser to access 3Sixty Admin and Disovery. The following browsers are supported:

• Chrome (latest)

• Firefox (latest)

• Safari (latest)