Test_Login is a command line utility supplied with the Cradle Suite to help diagnose connection problems between the Cradle client and CDS (Cradle Database Server).
At a command prompt cd %CRADLEHOME%\bin\exe\windows\or cd $CRADLEHOME/bin/exe/linux-ia32 or linux-x86_64
Execute test_login.exe or ./test_login.exe
Agree to continue with 'y'
For a basic test select 3 to login to the DEMO project as MANAGER
Select 7 to start the test
This will then tell you the method being used to find the CDS for now press 'y'
Move through the stages pressing 'y' each time and observe the result
If all is well the process will complete without errors.
If there is a problem an error will be raised (for example if a connection can’t be established because the CDS is not accessible or running Stage 1 would fail. At this point a user could try different CDS connection methods to diagnose the issue.
The ability to try different users and projects allow elimination of problematic installations or bad users.
Environment Variable or Command-line Switch Stack-tracing
As with many complex products Cradle monitors its internal operation and on the rare occasion that something goes wrong it writes information to a log. CRADLE_ERRORSTACK controls how much information is logged internally and output on these occasions.
If in the unfortunate case a Cradle tool crashes, there will often be a log produced in the %CRADLEHOME%\logs\errors directory. This will enable 3SLSupport to diagnose simple cases such as a lack of memory on the machine. If the case is more complex, the development team may need to know at which point the program was processing at the time the error occurred. CRADLE_ERRORSTACK will enable additional internal logging that will output a simple execution stack trace into the log. This can aid diagnosis and resolution.
Switching Stack Trace On and Off
CRADLE_ERRORSTACK is an environment variable. You can set it via the control panel’s Advanced system settings (see the screenshot). Or you could start the Cradle tool from within a command shell, (On Windows® press windows key type cmd and then in the shell set CRADLE_ERRORSTACK=true, then launch the tool e.g. "%CRADLEHOME%\bin\exe\windows\work.exe". You can also set a -errorstack parameter to your command line option, i.e. work.exe -errorstack to start WorkBench with the stack on.
Should I leave CRADLE_ERRORSTACK on?
Generally there is no need to leave the stack trace on all the the time. There is a small performance hit if you do, so unless you are having problems we don’t advise you leave it enabled.
What if that still does not sort the issue?
3SL Support may ask you to turn on tracing which produces a complete execution trail from the product. This has a large overhead and uses disk space and is only in used in the very trickiest of issues. Rest assured, it’s unlikely you’ll have to use it, but if you do there is a post here that explains tracing.
What is a silent install and how do I do it with Cradle?
Silent installs are installations which do not require user interaction.
To perform a silent installation you will need to create a “setup.iss” file, this is created when making your recording for the silent installation by opening the command prompt and running setup.exe -r. After completing the installation you will have the “setup.iss” file in your system drive e.g C:\Windows.
You can now perform a silent installation with your recorded settings!
On the machine you would like to do the silent installation, place your setup.iss file in the same directory as the setup.exe. For full installations or server only installs, you will also need your security code which you place within a text file such as “code.txt“. You must only enter the Security Code on the first line and add a carriage return. For client only installs the file can be blank.
Now you have your files ready, open the command prompt navigate to your setup.exe directory and enter the following setup.exe code.txt -s
You are now running your silent installation!
Remember when you have finished you will need to restart the machine.
Please note this does not work with Toolsuite
If you would like more information on this please go to Cradle Documentation – Installation Guide – Windows and to Chapter 8. Or click here for Installation Types
Multiple Cradle Database Server (CDS) Environments
Cradle supports multiple Cradle database servers, in a single environment, based on the CDS Host Access List. The following file contains a list of the TCP/IP hostnames of the hosts that the CDS will respond to:
Windows – %CRADLEHOME%\admin\cds_hosts
Linux – $CRADLEHOME/admin/cds_hosts
The file is empty by default, which mean a CDS will respond to all hosts.
Two or more Cradle systems may be installed and operate in the same network by ensuring that each CDS has a non-empty Host Access List that defines the lists of hosts that are to be serviced by that CDS. Multiple Cradle systems are consequently achieved by ensuring that the hosts used to run the CDSs appear in the Host Access List of only one CDS.
Clients Connecting to Multiple CDS
Each Cradle client such as WorkBench may be executed on a host which is in the Host Access List of more than one CDS. In this case, WorkBench should be told which CDS it is to connect to, for example by using the command-line option: -cds hostname
Methods of connecting Cradle tools to a CDS
There are several methods of specifying which CDS, when you have multiple Cradle database servers, a client is to use, or alternatively a client can attempt automatic CDS discovery.
-cds command line option
Cradle tools for example the WorkBench client, supports a -cds command line option that takes an argument which is interpreted to be either the hostname or IP address of the machine where the CDS is executing.
If invoked with this command line option, the WorkBench client does not attempt CDS discovery via broadcast, but instead attempts to link directly to the CDS on the specified machine.
CRADLE_CDS_HOST environment variable
If a -cds command line option has not been specified, the WorkBench client tests for the presence of a CRADLE_CDS_HOST environment variable, and if defined, uses its value as the hostname or IP address of the host executing the CDS.
In this case, WorkBench does not attempt CDS discovery via broadcast, but instead attempts to link directly to the CDS on the specified machine.
Automatic CDS discovery by broadcast
If a CDS host has not been specified through other means (such as via the –cds command-line option, or CRADLE_CDS_HOST environment variable), a Cradle client such as WorkBench will attempt to locate a CDS automatically by broadcasting. If the client can connect to two or more CDSs and is using this method, the client will connect to which ever CDS responds quickest.
For a more in-depth look at environments with multiple Cradle database servers, please refer to our online help.
We’ve expanded the writing team to include authors from elsewhere in the 3SL team. Because this is a blog, there is more emphasis on people’s personal insights into the Cradle product. This should make the style and tone more varied and hopefully more interesting to read.
As you may have already seen the 3SL-Blog is groaning full of new articles. These are mainly “Hints and Tips” and longer RM/SE articles. Increasingly we’ve found that some of the support questions that arrive here in 3SL towers are very similar. To that end we’re publishing them under the FAQ section.
If you have a burning question and would like to see an article covering a particular topic, drop us a line at email@example.com and we’ll see what we can do. On the other hand, if you have a novel use of Cradle that you’re happy to share with us, drop us a line with the article, screen shots and accreditation details and we may feature it.
Non Graphic Interfaces
There is widespread understanding of the WorkBench and even Web Access interaction with Cradle. It is, after all the main way we interact with the data. However, there are many occasions when we want some of the data from Cradle but don’t want to or can’t use a screen to interact. This month we’re highlighting c_table.
This command line utility can be used to produce Reports, Matrices, Metrics, Graphs or Queries in a tabular form. This can be an HTML, RTF, CSV or SVG output. If every morning you need to go into a meeting, or stand at your ‘toolbox talk’ with a printed report detailing the number of ‘Issues’ with a category of ‘Raised’ you can do this by running one command. Creating a desktop short cut to run the command / batch file you need not start WorkBench just to run the query and publish the result. Even more cunningly a script could be triggered at 8:00am every morning to create the document for you. Our blog article “Batch File Reporting in Cradle” adds more detail.
If you are working or bidding on large infrastructure projects, Cradle is now available through the CompeteFor procurement portal. Whatever the size of your Requirements Management or Systems Engineering task, Cradle is there from Concept to Creation.
If you frequently run the same item commands, or you want to guide users to use a particular subset of commands, add them to the Cradle ‘View’. These are termed “View commands”.
When defining a Cradle Views, you can add commands to appear at the ‘Item icon’. When the view is run this enables different users to be guided to commands for their role in the project. Combined with a phase and they can, run the appropriate query and they can get straight into creating children, linked items, updating link details, or whatever is appropriate for their role. Spending a little while now, arranging the process steps for your users can give a significant gain in productivity.