Moving Packages/Components to Production

Would you like to deploy components to another server without using the development tool? It's easy to move components from one server to another if you understand Jaguar repository. Jaguar stores everything in two main directories: Repository and INI. These directories are so important you should back them up before making any major changes and also after successfully adding or making changes. PowerObjects suggest backing up Jaguar Repository and INI after a successful install so you wont need to reinstall if you make an error removing demo components from Jaguar.
To move a component to another server you need to move three parts and modify one file on the server you are moving to. The pieces to be moved are Package, Component and IDL. The file that will be modified is Jaguar.props.

Lets dig into detail. Jaguar is installed in c:\program files\Sybase\jaguar cts 3.5 and an environment variable is setup to point to the Jaguar directory. The environment variable is jaguar. You can change to the Jaguar directory by typing at a DOS prompt the following:

C:\>CD %jaguar%

Looking inside the repository we see many directories. We will be moving files from Component, Packages and IDL as stated earlier. The last thing we will do is modify the Jaguar.props file in Server directory.

---

Components

Inside the component directory you will find a directory for every package that is in Jaguar. When we move components from one server to another we are moving the package that the component exists in. Note you can move just a component.

In this exercise we will move the components in packages. To move these components you must copy this whole directory and all the files under the directory.

By expanding the directory I can see it has one component, named n_rs. In side this directory you can see the actual code. You will get a directory structure C1, C2, C3 etc. You only need to keep the largest number directory.

So before moving the package/component to another servers you should remove extra directories.

Trick to Moving Components

The easiest way to move files is to use WinZip. Simply zip up the files and directories using directory location and you can easily move to another machine and unzip. To let WinZip do all the work simply create a directory called deploy and create three sub folders: Component, Package and IDL as follows.

Now we will just copy the needed files into the deploy folder location and zip. The we can unzip on the new server under %jaguar%.

Moving Component Information

Highlight your directory under %jaguar%\Component (we are moving demo) and copy to Component directory under c:\deploy.

Note I removed extra components under this directory before I copied, i.e., I deleted C1.

Moving Package Information

The package information is a props file that contains all the information about the package. The package props file will have the same name as you package you are moving. Highlight your props file under %jaguar%\Package (we are moving demo.props) and copy it to Package directory under c:\deploy.

Moving IDL Information

IDL has a directory and a props file. You need to move both. Copy your directory and props file from %jaguar%\IDL (we are moving demo and demo.props) to the IDL directory under c:\deploy.

Zipping Our Deploy

Now that we have copied all these files we can zip up the directory so it's ready to deploy. You want to zip up deploy so the zip file contains the directory structure and directory names, i.e., Component. Package and IDL.

By coping all the files to the correct directory structure the zipped file has all the directories setup. Notice the path in the WinZip Deploy.zip file.

Again to deploy this to the server you simply extract using folder names to %jaguar%\Repository. After expanding the zip file on the new server you need to modify Jaguar.props file before you can call the component.

Modifying Jaguar.props

Jaguar reads the Jaguar.props file to initialize. This file tells the server what components are registered along with many other things. Below is the props file. The Jaguar.props file is located in %jaguar%\Server. Special note: We are modifying the Jaguar.props file on the new server.

The property we care about is com.sybase.jaguar.server.packages. This tells Jaguar what Packages to server up. Packages can be loaded in Jaguar, but not installed in the server. The first process we did was load the package and components into Jaguar this process is installing the Package in the Server. So to ad your new package move your cursor to the end of the property and add your package name (We are adding demo). After adding the package name save the file and restart Jaguar.

Before

com.sybase.jaguar.server.packages=
webreport,timetrack,webmenu,eportal,
jagtools,xml

View Your New Component

Start Jaguar Manager on the new server and logon. You will see your newly deployed component under Servers\Jaguar\Installed Packages here.