LCFM Native has created a gateway solution for your app. This allows it to communicate with the original FileMaker solution, and pass data back and forth between your new Native app and your original solution. Both the Gateway, and your original solution, must be hosted on your FileMaker Server.
Open the Gateway File
Click on the arrow to open the gateway solution LCFM Native has created from your original file. You can also find this by going to your project folder that LCFM has created (by default this will be in the Documents folder) and opening the file named "<yoursolutionnamehere>interface.fmp12".
When you open the interface solution, you will be asked for a username and password. This is the username and password you set on your original solution, because FileMaker is trying to open both the original and the gateway solution, using the original solution as a datastore. The new gateway solution does not yet have a password, we will need to set it.
Go to File>Manage>Security
Set the same password as you used for your original solution for your full access Admin account. Remember, both the original account and the new one you are creating must be full access Admin accounts. If they are not, while the extraction and app build may complete successfully, you may find there is missing data, or you cannot access areas of your app.
Note: The username of the full access account must also match that for the original solution. If it is not Admin, you must explicitly set up a matching full Admin account with a matching username and password.
The fmrest permissions have been set up for you already by LCFM during creation of this interface file.
Upload to Your FM Server
You now need to upload your gateway solution to your FileMaker Server. Go to File>Sharing>Upload to FileMaker Server.
In Favorite Hosts, select your FileMaker Server. if you don't have a server set up, please see the lesson on Setting Up FileMaker in the "Before you start" section.
I've selected my localhost server, and I get this message. Because I am just testing locally, I just check Always permit connection (1) and connect (2). Obviously, if you are deploying a live solution on a remote server, you need to ensure you have the appropriate SSL certificate set up.
Enter your Console name and password. This is not the same as your solution username and password, it is what you set when you set up your FileMaker Server. In this particular case, I've been keeping things simple by using Admin everywhere but this is NOT best practice and you should certainly not do this in a live situation!
You're now ready to move on to the next step.