Remote Server Setup- Standalone

The Remote Server setup in CFBuilder has been a topic of discussion on the forums and the response received for the remote setup hasnt been very positive. I tried to answer as many questions on the forum as I could but still there always remains some ambiguity.The documentation team has worked very hard to be explanatory but looks like it isn’t enough.
This is yet another try to simplify things.
I want the readers here to co-operate with me for two things:
1. Please dont have any pre-followed process or assumptions in your mind before reading this post or the following ones on the same topic.
2. Try to follow the steps mentioned here to set up a remote server(may be just a mock) to get the satisfaction that you could actually connect to one. :)
Instead of talking in general about a remote server setup I am going to split this to explain the setup for Standalone Servers and MultiServers.
So those of you who are not interested in Standalone can skip this one and read the following post.
Setting up a Standalone Remote Server:
What do you need: A Remote Server, A local CFBuilder installation, AdminServerComponents.zip
Setup: Unzip the AdminserverComponents.zip in the remote CF Server Home directory. Example: C:\ColdFusion8
Disclaimer: In case your remote server is CF9-beta you don’t need this .zip file. Just directly goto Step A3 below.
Procedure:
Steps: On the Remote Machine:
A1. Connect to your remote machine(lets call it ‘bhakti04′) and ensure that the files adminstart.bat, adminstart.sh, admin_jvm.config have been extracted to {CFServer_Home}\runtime\bin
A2. Change the security Properties file located at {CFServer_Home}\runtime\lib and change the
jrun.subnet.restriction and jrun.trusted.hosts to *. This is done that there is unrestricted
access to your remote CF Server. You could even add the IP of the machine on which CfBuilder is running. But for the demo purpose I am going to make it *.
A3. Goto {CFServer_Home}\runtime\bin and run the adminstart.bat(for Windows) or adminstart.sh(for MAC). A console will open and admin will start. Check the port on which the
admin is running.I am going to assume its ‘2910’ for further steps.

Steps: On the CFBuilder:

B1. Open the Add server Wizard.
B2. Fill the wizard fields as follows:
Screen 1:
Server Name: This is a user friendly name you want to give the remote server. I am going to call it. “Bhakti’s Desktop”
Description: The description for this server. I am going to say, ” This is a Standalone CF 8 server”
Host Name: The IP address or machine name. In my case, “bhakti04″
IsRemote: This should get automatically selected after entering the host name as “bhakti04″
Webserver port: The port on which your remote CF Server is running. Since my remote server is running on 8500, that would be my entry.
Context Root: Not Applicable for Standalone
Application Server Name: Not Applicable for Standalone
RDS UserName: User Name of the RDS Server. This is the uname/pasword you specified for RDS while installing ColdFusion Server. If you dont enter this, your remote datasources and files will not be available to CFBuilder. My RDS Uname is ‘admin’
RDS Password: RDS Password. ‘admin’ in my case.
Screen 2:
Naming Port: This is the naming port of the admin server.In step A3 I asked you to keep a note of this one. Default is 2910 and so is it in my case.
User Name: This is the JNDI User Name. You can find it in jrun-users.xml at {CFServer_Home}\runtime\servers\admin\SERVER-INF
Password: This is the JNDI password. Found at same as above.
Document Root: Document root of the CF Remote Server. Precisely the location where your CFIDE resides. Its “C:\ColdFusion8\wwwroot” in my case. Other examples: C:\Inetpub\wwwroot or \opt\htdocs\wwwroot
B3. Hit Finish
You might see the status as ‘Unknown’ for a second or so. In such cases you will also see the “Getting Server Status” in the bottom right corner.After the “Getting Server Status” action is completed, the status should be seen as “Running”.
In case your status is “Unknown” even after the above mentioned operation is over, just switch to the console to check if any error is thrown.
I have tried to prepare a list of the kind of errors thrown while connecting to Remote Server
and how to recover from them.
1. jrunx.rmi.RemoteInvocationHandler; ….. – We used to have a Version field earlier in Server Wizard. But that was creating a confusion. In the proocess of removing it and using some logic, this message gets Thrown. It is an absolutley HARMLESS message and can be *IGNORED*
2. Unable to fetch server mappings. Reason: null – Again this message is a bug from our side. It is a Harmless message and can be IGNORED.
3. The connection to the remote JNDI server on Host XYZ at port 2910 has failed(as have all backup hosts listed, if any) – please verify thet the server is running and the NamingService is available. – This message is thrown if your admin server is not running on the remote machine. You need to ensure if step A3 is performed.
4. One case where the status is “Unknown” and the console says “Server is available, getting server status”. The Status still remains unknown after that.- Connect to the remote machine and check the console of the admin that we ran in step A3. If it says “Security Alert….. ” then your Security.properties is not set properly. Check what you need to do in Step A2 above.
Apart from all these if you face any other issues then please feel free to add them as a
comment.
Will write the post for Multi Server in a couple of Hours.