Frequently Asked Questions (FAQ)

Nesstar Publisher

 

Nesstar Publisher

What are the software/hardware installation requirements?

A minimum of 1GB of hard disk space is recommended for installation and local data storage, and that you have 2 GB or more of free hard disk space on the disk where the TEMP directory is located. More space may be required for very large datasets.

1 GHz or faster processor, and 512 MB memory or more is recommended.  Large datasets may require more memory.

Minimum 1024x768 resolution, 1280x1024 or higher recommended.

OS: Windows XP/2000/Vista/Win 7

Will I be able to use publisher in Linux?

There are no immediate plans to develop/release Linux version of Nesstar Publisher.

But, we have had reports that Nesstar Publisher has been run successfully under Wine on Linux. Note that this has not been tested by us, and that running Nesstar Publisher under Wine will not be supported by us (due to the many versions of Wine and distros running Wine).

Which version of the DDI Nesstar Version 4 supports?

Nesstar Publisher v4.0 supports DDI 1.2.2 with some support for DDI 2.1. We are working on adding DDI 2.5 to later versions of Nesstar Publisher.

Why do I get the error message ‘corrupt installation detected’ ?

Make sure you have administrative rights to the machine on which you are trying to install the Nesstar Publisher.

Why can I add a Nesstar Server but not publish to it?

Any user of the server can access the ‘Manage Server’ component. Only admin and publisher users (users with administrative rights) can publish.

How do I publish to a secure server?

Please consult the latest version of the general 'Getting Started Guide' and 'Publisher User Guide' for information on publishing to a secure server. You can download the guides from our publisher help site.

Where is the File Description part of the DDI in the Publisher?

Some of the fields from the File Description section of the DDI are not relevant for NSDstat format files, and cannot be found within Publisher. Others are automatically generated from the dataset itself and can therefore not be edited, but others can be added to a Publisher Template in the usual way. Please refer to the Publisher User Guide for further information.

How do I add documentation such as .pdf or .doc files in the Nesstar Publisher?

Documents can be added to a Nesstar Server and then linked to from Publisher by:

1. Copying the file into the directory \Nesstar-Server-xx\jboss\deploy\server\default\root.war\

2. Then adding a link to this file in within Publisher by using just the document name in the following format: /document_name.doc

Why does it occasionally take a long time to import a small file ?

The following are possible causes of this:

1. Lack of  space on your hard drive. The data are best imported into Publisher from the hard disk of your PC or from a network drive to which you are allowed to save files.

2. Lack of temporary space or no permission to write to a drive. As soon as a file is being imported, Publisher will create a tempory copy of itself, and you will need space and permission to write to this area.  To specify where temp files are stored see File | Preferences in Publisher.

3. Problems with your network connection. It is also possible that the problem occurred because of a temporary loss in connection to your network, if the file is on a network drive.

4. Your dataset contains a large number of alphanumeric variables. Importing a file that contains alphanumeric (string) variables longer than 8 characters may slow the import process.

Does the Publisher support non-English characters?

To avoid any problems the Nesstar Server and Publisher machines should use the same character set. When downloading the datasets the same character set that was used when the NSDstat file was created should also be used.

If no short string variables have been used in any datasets, or if the short string variables only contain ASCII characters, then the datasets can be used on all machines without regard to character set.

Are the variables that are longer than 8 characters shortened to 8 characters when exported from Nesstar4.0 into SAS variables?

  In Nesstar4.0, the variables that are longer than 8 characters are no longer shortened when exported into SAS variables.

Where can I find the Nesstar Exporter Excel Macro mentioned in section 10 of the Publisher User Guide "Nesstar Cubes"?

The Nesstar Exporter Excel Macro can be downloaded from the publisher help site.


How do I publish cubes using old NSDstat file?

              Please refer to the step-by-step guide regarding publishing cubes using old NSDstat file.

 

 Do I need to update my templates created in earlier editions of Nesstar Publisher to make them compatible with Nesstar Publisher 4.0?

One has to export the templates from Publisher 3.5 as per the following steps
  1. Go to menu option [Documentation | Template ]
  2. Select the custom template.
  3. Click on Export option.
To import the custom templates into Nesstar Publisher 4.0 using the below steps
  1. Goto [Documentation | Template ]
  2. Click on Import option
  3. Browse to and select the custom template file.
  4. The Publisher 4.0 will create 4.0 compatible multilingual templates.

 What is .missRecode file?

When writing Statistica, all missing values, user- or system-missing, must be recoded into a new value. The reason is that Statistica has only this representation of missing values. Hence when exporting datasets into STATA-8 ( *.dta) or Statistica ( *.sta) categories being defined as missing in source file will not have the category definition transferred into the Statistica file. A  *.missRecode file is created, this file documents the missing value recodings done by the publisher.

Note: Whenever a .dta is shared with other users the .missrecode file also needs to be shared if it is more than 1KB in size. The .missRecode file can be opened using a text editor ( eg. notepad).

 How do I import certificates in Nesstar Publisher

If your Nesstar Server uses a certificate signed by someone the Nesstar Publisher does not know about (typically this happens when using a self-signed certificate, but the same procedure applies in other situations too), you will need to import the certificate into the Nesstar Publisher's keystore to be able to use SSL.

Included in the Nesstar Publisher distribution there is a batch file called importcerts.bat. Simply copy any certificate(s) you want imported in .cer or .pem format to the Nesstar Publisher root folder and then run this bat file. You will need to restart the Nesstar Publisher after having imported new keys for the changes to take effect.

If the Nesstar Server you are trying to connect to uses a self-signed certificate, you will need to get the .pem file from the server. If you have access to the server, you can copy it from config/ssl/ in the installed server. It will be named after the server name, and should be the only .pem file in that folder. If you do not have access to the server yourself, ask the server administrator to get it for you.

If the Nesstar server does not use a self signed certificate, and you still have problems with SSL, this most likely means that the certificate is signed by a certificate signing authorithy that was too new or to obscure to be included in the default keystore that ships with the Nesstar Publisher. In this case, ask your Nesstar server adminsistrator to send you the root certificate in .pem or .cer format and follow the procedure described above to import it into the Publisher keystore.