Not too much;-) At least not much the average user will see.
We added Remote Deployment support for the Sun Java System Portal Server 6.3 on top of the Application Server 8.1. If you happen to want to play with that on Solaris or Linux. Remote deployment is not really a good description, because the Portal Server and Creator have to be on the same machine.
We tested it with the Java Enterprise System 3 and the upcomming JES 4. The newer version has a couple of problems fixed so I would suggest to wait for that if you can.
But there is one big problem. The Portal Server was not designed to interact well with tools like Creator. The only way we found to deploy to it, is to run a script as the user under which the Portal Server was originally installed (usually root).
There are two ways to handle that problem:
Use the sudo command to run the deploy-script. That’s the solution I would prefer. But it needs some preparation. More about that below.
Run Creator completely as root (root seems to be the default user for Java Enterprise System/Portal Server installs). But Creator was not really intended or tested for that.
Setting up the sudo environment
The sudo setup has to be done by the admin/root of your system! So, please switch to root before you try to do any of the following steps.
Sudo is installed by default on most Linux systems. Or if not, you can usually find it on your installation media.
Solaris does not have sudo out-of-the-box. You can build it yourself (Find the sources here!) or you can find a prebuilt package on the Companion CD (Solaris Freeware download).
The Creator EA2 will look in /usr/bin and /bin for sudo (Sorry, I realized too late that there is the Sun FreeWare package which installs the binary into /opt/sfw/bin. That path is already added for the next version of our sources.), so please make sure, the command is found there (ln -s might be your friend;-)
Use the visudo command to add a line to the sudoers file. It should look like:
<creator_user> ALL = NOPASSWD: <creator_home>/rave2.0/bin/ps6-deploy.sh
<creator_user> should be your normal user and <creator_home> the directory, where this user installed Creator.
That line in the sudoers file will allow the user to run one shell script as root without requiring a password. I suggest that you look at the script to make sure, we did not miss anything bad!
If you don’t add this line and Creator finds the sudo command, Creator will try to use sudo anyhow and that would ask for a password on the terminal where you started Creator, if you started Creator in a terminal! I don’t know what sudowould do when it was not run in a tty!
Deploying to a Portal Server
After sudois set up (or if you are running as root), simply add a Portal Server to the Remote Servers node in the Server Navigator.
Develop and test your portlet as you normally would and in the end, use the Deploy to Remote Server context action and select the added Portal Server. That should do it.
Ok, again: If you want to play with the Portal Server, feel free. But this was not extensively tested for EA2!
An alternative to using sudo would be to use RBAC on Solaris. RBAC is similar to sudo but it is a core part of Solaris and is much more flexible – particularly in Solaris 10 where you can give out individual privileges rather than full root (or other uid/gid) access.
yes, I’ve heard about RBAC, but so far I did not use it. So I don’t really know much about it:-( The other problem is that that would only work on S10 or above. And we don’t currently distinguish between OS/version’s.
I hope we can work out a better way for the next version of Portal Server;-)