• Net X 360 App
• Netx360 Download For Mac
• Netx360 For Mac

1. The MAC address comes from the acronym for Media Access Control. It is a 48-bit identifier (6 blocks of two hexadecimal characters (8 bits)) that uniquely corresponds to a card or network device. It is a 48-bit identifier (6 blocks of two hexadecimal characters (8 bits)) that uniquely corresponds to a card or network device.
2. ‎IMPORTANT INFORMATION FOR USERS - To use NetXInvestor™ mobile, you must be a client with an account at a financial institution that provides its clients access to their account information via the NetXInvestor website. The financial institution also has to specifically activate the NetXInvestor™ mob.

The NetX I/O application comes in two different forms:

1. Desktop App (Mac OS and Windows)
2. CLI Tool (Linux, Mac OS, Windows)

Netx360 Click the Download Free Trial button above and get a 14-day, fully-functional trial of CrossOver. After you've downloaded CrossOver check out our YouTube tutorial video to the left, or visit the CrossOver Chrome OS walkthrough for specific steps.

This article will familiarize you with the CLI (command-line interface) version. While the Desktop version makes it easy to set up multiple syncs, along with drag and drop importing, there are cases where you'll want to programmatically drive NetX I/O. For example, the CLI allows you to set up various sync point on a workgroup file server. It runs 'headless' (no user interface), and can be easily wrapped in shell scripts and scheduled via cron (or others). The NetX I/O CLI is packages as a Jar file, and is executed with Java.

Installation

This outlines the steps needed to start running the NetX I/O command-line tool. This illustrates setting it up in 'sync' mode, but if you want to use the tool in WatchedFolder or any other mode, the steps are almost the same.

Windows users: NetX I/O requires the Microsoft Visual C++ Redistributable to be installed before it can run. For instructions on how to obtain this package, see https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads.

Step 1: Make sure JDK is installed locally

You can test this on Linux or Mac by typing: 'java -version' to check the Java version. Like this:

If the version printed is anything other than '1.8.x', you will need to download a supported version of Java from Oracle: https://www.oracle.com/java/technologies/javase/javase8-archive-downloads.html

Step 2: Download the NetX I/O jar file

You can download the appropriate version (eg 'netxio-4.0.xxx.jar') from our Service Portal, found in the /Modules/NetX I/O folder.

Step 3: Create a work location folder

Create a folder on your workstation for NetX I/O to write files. For the sake of illustration, let's say you're on a Mac, and you create a NetXIO folder inside your home directory:

Step 4: Copy over the jar file

Copy the netxio-3.0.xxx.jar file into your work location folder. Eg:

Step 5: Create your sync folder

The storage location you created in Step 3 is simply for managing administrative files. Now you need to choose or create a new folder that will be the root of all the synced sub-folders and files. Again, to illustrate, we'll add one off the Desktop; here for example:

Really, you can call this anything you like, and it can live anywhere. Just choose something convenient to use. Do NOT nest the work location folder inside of your sync folder.

Step 6: Create (or choose) your sync folder (in NetX)

Net X 360 App

You can choose any folder that is not a top-level folder. However, please choose wisely: it's better choose a folder whose sub-structure is not very large. You can, but the sync times, bandwidth, and local storage requirements will obviously increase. Make sure that you are choosing a folder that the account you are running NetX under has appropriate access permissions.

For our example, we'll choose this folder in NetX:

Step 7: Create (or choose) a user (in NetX)

NetX I/O logs into NetX using supplied credentials for a pre-existing user, and actions will be performed on behalf of that user. It's best to create a separate account for your NetX I/O user. If you were to log in to NetX and then log out as the same user logged in via NetX I/O, it disrupts the processes in I/O. If you're running NetX I/O in Sync mode, you must configure it to run with an Administrator-level user. For Watched Folder mode, a Producer-level user (or higher) is required. You will need to know the username and password for that user you want to log into NetX with.

Step 8: Start NetX I/O

On a Mac, you can open a terminal, and type the following:

Ensure the 'cp' directive is placed before the class (com.netxposure.external.client.io.NetxIO), or it will be interpreted as a parameter to the class. Instead, this is intended for Java. Also, this process could potentially use a large amount of RAM (depending on the total sync size; it will need to hold the entire local state map in memory, twice to compare). So in this example the Java heap is set to start with 512MB (-Xms512M) and can utilize up to 1024MB (-Xmx1024M). This is just an example.

Most of this should now be familiar to you, including the library directory, the username, password, folder, directory and local storage. But to formalize this, here's each flag with corresponding details (please refer to the Usage article for more details and options):

If you start NetX I/O using the terminal, you may want to background that process, because not doing so and closing the terminal will quit NetX I/O. Additionally, you may also want to add this command to your workstation startup items. There are many ways to deploy this tool more robustly, but that's out of scope for this quick start. This article's purpose is simply to get you up and running quickly.

Be aware of the capacity of the underlying storage when configuring the 'localStorageDir' setting. If imports encounter significant errors, failed import files will be copied to the 'lost and found' directory under this path. If that storage facility runs out of space, that will lead to secondary (and critical) errors with NetX I/O.

If the user account running I/O does not have appropriate access permissions to the NetX folders it is trying to sync, an error will be received:

Step 9: Start using the sync

Drop folders and/or files into your local sync folder, and/or import new files into NetX. Wait for the loop time, and then see the folders and files replicated on the other side. Enjoy!

Built-in help

Netx360 Download For Mac

You can obtain details on all the NetX I/O by running the CLI tool with the '-help' flag:

Merge and Sync modes are experimental and are not supported for use in mission-critical environments. Use at your own risk.

Running multiple NetX I/O processes on a single workstation

There are cases where you may want to run multiple instances of NetX I/O on a single workstation — and that's perfectly fine. However please ensure that each instance uses its own local storage and sync folders. Do not attempt to run multiple instances of NetX I/O CLI with a shared local storage directory!

If you're using a config file (see details below), and order to identify the various processes running presumably in the background, you can add a -D parameter to java. The '-D' is normally a mechanism for passing name+value pairs to the JVM. However, the JVM is happy to ignore directives it doesn't understand. So you can add something like 'clientId=35' to the command-line argument so that if you need to query the process table (speaking specifically of Unix platforms here — Linux and Mac), you can see that argument there.

If you want to do this, you must add the '-D' flag before the reference to com.netxposure.external.client.io.NetxIO. Eg:

Doing this means that if you type this on a Mac:

You might see something like this:

Using a config file instead of command-line arguments

Netx360 For Mac

You can also set all your NetX I/O options within a configuration file. In this scenario, you only set the configuration file (the '-config' option) in the command-line. Like this:

Here's what an example configuration file might look like:

Note that option names are separated from their corresponding values with an equals sign (=). Also, do not wrap config values with quotes (like you might do on the command-line). Additionally, please note that command-line arguments that require no arguments — like 'debug' in this example — can be set with a value of 'true'.

I/O lock file behavior

What happens with NetX I/O CLI if the last execution is still running when cron tries to execute again? The lock file should stop it from executing concurrently. NetX I/O writes a lock file IF there's a configured 'localStorageDir'. There, it will write a tmp file with a timestamp. And that will regulate how often another NetX I/O process — configured with the same localStorageDir — can run. For 'loop' based tasks, the time-lock is twice as long as the loop. If not, it's 30 mins. This file is then periodically updated throughout the processing of the run. The reason for the timestamp is so that if NetX I/O terminates unexpectedly and the lock file is left there, later runs of other I/O processes can note that the lock file itself is 'stale' and proceed regardless.