system administration

Transcription

system administration
Prosentient
Inter-Publish
System
Administration
© Prosentient Systems Pty Ltd 2003
C OMMERCIAL IN C ONFIDENCE
Table of Contents
Introduction........................................................................................................... 1
The Systems Administration Manual ................................................................... 1
Other Reading ...................................................................................................... 1
Inter-Publish Installation.............................................2
Aim........................................................................................................................ 2
Technical Architecture.......................................................................................... 2
Site Set-Up Checklist ........................................................................................... 4
Setting up new sites......................................................7
Aim........................................................................................................................ 7
Website configuration........................................................................................... 7
Site Set-Up Checklist ........................................................................................... 8
Inter-Publish Security and User Management ............11
Aim...................................................................................................................... 11
User Security...................................................................................................... 11
Add a new User.................................................................................................. 12
Grant a User access to Sections ....................................................................... 13
Delete a User ..................................................................................................... 14
Global Updates ...........................................................15
Aim...................................................................................................................... 15
The Global Change page ................................................................................... 15
Customisation Language & Terminology ....................17
Language Localisation and Terminology customisation ................................... 17
Customisation: Tasks & Shortcuts ..............................18
Creating Tasks & Shortcuts to external URL(s) ................................................ 18
Creating Edit/Publish shortcuts.......................................................................... 19
© Prosentient Systems Pty Ltd 2003
Page i
COMMERCIAL IN CONFIDENCE
This document may only be reproduced with the permission Prosentient Systems Pty Ltd
Configuring Microsoft Indexing Server .......................20
Aim...................................................................................................................... 20
Indexing Server Set-up Checklist ...................................................................... 20
FAQ ............................................................................22
FAQ 1: SSL operation in IIS ............................................................................... 22
FAQ 2: Co-existing with IIS/FTP ........................................................................ 25
FAQ 3: Server.CreateObject error ..................................................................... 26
FAQ 4: Object not found error on editing/publishing ......................................... 27
FAQ 5: Inter-Publish will not start ...................................................................... 28
FAQ 6: "Systems Files are out of Date" with multiple reboots .......................... 29
FAQ 7: “Socket” error when you click the REGISTER or CONFIGURE button 31
© Prosentient Systems Pty Ltd 2003
Page ii
COMMERCIAL IN CONFIDENCE
This document may only be reproduced with the permission Prosentient Systems Pty Ltd
Inter-Publish — System Administration
Introduction
The Prosentient Inter-Publish is a Content Management System (CMS) that has been designed to
provide a simple means for you to access and contribute to a pool of knowledge without needing to be
skilled in HTML or Internet document mark-up techniques.
Inter-Publish comprises a database component for the management of information and for the storage
of design layouts that define the presentation of published content. The purpose of the Inter-Publish
application is to build a database of content that can be used for publishing in any specific format that
meets your organisation’s needs, including XML.
The focus of Inter-Publish effective management of your website. It facilitates publishing, indexing
and delivery of all manner of content. Text, multimedia and other content can be coherently organised
and published, with associated attachments to HTML, Email or other formats. Indexing generates
structured indexes of content (by Title, Subject, Date or any other informational element).
Some features of the Inter-Publish Content Management System are:
•
WYSIWYG (What You See Is What You Get) HTML editing facilities
•
Individual and Mass publishing facilities (to HTML or Email destinations)
•
Management of your information as a knowledge resource
•
Managing communication with your clients
The Systems Administration Manual
This manual is intended to assist the configuration of new web sites in conjunction with Inter-Publish.
Guidelines on use of IIS and Indexing Server to optimise interactivity and searching are discussed.
Other Reading
First time users of this software should first review the Inter-Publish Training Manual. Graphical
designers should review the Designers Guide.
© Prosentient Systems Pty Ltd 2003
Page 1
COMMERCIAL IN CONFIDENCE
This document may only be reproduced with the permission Prosentient Systems Pty Ltd
Inter-Publish — System Administration
1
Inter-Publish Installation
Aim
This section provides a checklist for the installation of Inter-Publish on a new publishing system.
Technical Architecture
Microsoft Visual Basic was used to build the server components of the software
The software is designed asa a server-based web-enabled application using an Application
Server model. The service component was developed to a Windows architectural base. A
minimal amount of client-side scripting is used to enhance aesthetic and client-side functional
elements of the application. At the client side the focus is toward using existing platforms and
authoring tools to maximise the integrative elements of the implementation. Most key
functional elements are performed at the server-end
The architectural components of the server are:
Server Operating System
Windows (95 or later)
Server applications:
CMS Web & WebDAV Server – written in Microsoft Visual Basic 6.0
FTP Server – written in Microsoft Visual Basic 6.0
Relational Database: Microsoft Access and SQL Server 2000 tested
(other relational database support would be relatively simple)
© Prosentient Systems Pty Ltd 2003
Page 2
COMMERCIAL IN CONFIDENCE
This document may only be reproduced with the permission Prosentient Systems Pty Ltd
Inter-Publish — System Administration
HTTP SERVER
BROWSERBASED
CONTENT
EDITING
AND
MODELLING
INTERFACE
(eg Internet
Explorer)
with integrated
WEBDAV
SERVER
COMPONENT-ORIENTED
CONTENT CLEARINGHOUSE
(MS-SQL Server or MS Access)
SEARCH
ENGINE
INTERFACES
(WEB, Z3950LIKE
PERSISTENT
SEARCH)
FTP server
WEBDAV
Heterogonous authoring tools
(any platform)
5.3.5 Architectural Limitations
While the client-side interaction has been generalised as far as possible for a reasonable level of platform
independence, some site modelling components are Internet Explorer specific. The integrated HTML editor
requires an ActiveX control – and is, therefore, in most respects Windows and Internet Explorer specific.
In other respects, the content integration through the HTTP, FTP and WebDAV interfaces are platform
independent. Indeed, the focus of the content-editing elements of the prototype has been on integrating with
heterogonous multimedia tools.
© Prosentient Systems Pty Ltd 2003
Page 3
COMMERCIAL IN CONFIDENCE
This document may only be reproduced with the permission Prosentient Systems Pty Ltd
Inter-Publish — System Administration
Site Set-Up Checklist
ACTION
Prerequisites:
• The server used to host the publishing software must be running Windows 98,
Windows 2000 or Windows XP
• Must have Internet Explorer 5 Service Pack 2 or later installed
1
Run the Setup.exe program on the Inter-Publish distribution CD. The following examples
assume your install location is c:\program files\w3cserver
3
By default Inter-Publish will store content in the supplied Access database. If you have
Microsoft SQL server installed, you may create an SQL database called Inter-Publish and
apply schema on your target SQL database using the schema definition on the cd: \InterPublish\sql\Inter-Publish.sql.
4
On an appropriate disk for transient data, create a staging_directory directory for use by
Inter-Publish.
© Prosentient Systems Pty Ltd 2003
Page 4
COMMERCIAL IN CONFIDENCE
This document may only be reproduced with the permission Prosentient Systems Pty Ltd
þ
Inter-Publish — System Administration
5
We recommend you install Inter-Publish as a service. That way it will automatically restart
whenever you restart your server.
Windows 95/98
Run c:\program files \w3cserver\win95service.exe
Windows 2000/xp
Run c:\program files\w3cserver\ w3cserver.exe -install
5
Start Inter-Publish. You may either:
a) run c:\program files\w3cserver\w3cserver.exe
b) net start “ip w3c”
c) Go to the NT services list and start the service
You should see the Inter-Publish console appear:
6
Click on REGISTER to start the registration process. You should have received a registration
code with your license email. For multi-site/client versions of this software you can use
CONFIGURE to add additional client registrations.
Note your Admin username/password. This will be used for all subsequent publishing system
access, and to set up other users on the system.
At the bottom of the configuration screen are the details of your content database. You can
use the default Access database if you wish, or change this configuration to point to your
SQL server database. All passwords specified here will be encrypted on the database.
© Prosentient Systems Pty Ltd 2003
Page 5
COMMERCIAL IN CONFIDENCE
This document may only be reproduced with the permission Prosentient Systems Pty Ltd
Inter-Publish — System Administration
7
If you are using the XML interfacing features, you will need to configure relevant Email
accounts in your Pop-compatible email server. These details are registered against the InterPublish Section, which is taking XML inputs. You must identify in the Section entry the:
Email Server
Email POP User ID
Email POP Password
© Prosentient Systems Pty Ltd 2003
Page 6
COMMERCIAL IN CONFIDENCE
This document may only be reproduced with the permission Prosentient Systems Pty Ltd
Inter-Publish — System Administration
2
Setting up new sites
Aim
This section will introduce the steps required to establish a new website using Inter-Publish
Website configuration
The first stage in website design is a thorough review of requirements. Storyboarding and mapping the
site design, and even some prototyping using a standard web-authoring tool can be advantageous to
assist development of an effective site structure.
Once a site structure is conceived, it can be implemented very simply in Inter-Publish. The site
structure in Inter-Publish should mirror that of the web-site:
Web Sites
Eg: http://www.montageplus.co.uk/about/
Designs
Sections
Collections
Content: Web pages, Images,
Audio, Video
Publishing System Content Structure
© Prosentient Systems Pty Ltd 2003
Page 7
COMMERCIAL IN CONFIDENCE
This document may only be reproduced with the permission Prosentient Systems Pty Ltd
Inter-Publish — System Administration
Site Set-Up Checklist
þ
ACTION
1
Before you proceed with Inter-Publish Section Set-up you will need:
• Be familiar with navigating and using Inter-Publish features
• To have created the relevant home directory on your external web
server (subdirectories can then be created automatically)
• To have the ftp access details for that directory
• Have a System Administrator account on Inter-Publish
2
If this is a new website, you will need to create a new Web Site definition. This
appears as the main heading for the site on the left hand navigation bar.
2
1.
From the Main Menu click on Site Set-up.
2.
Click on the Web Sites link.
3.
Click on the NEW button to create a new website
4.
Change the DivisionID and Division Name to a descriptive name for
the Website.
5.
Click on the SAVE button.
Create a Section entry for each sub-site. From the Main Menu select Section
from the drop-down list and click on the CREATE button.
•
The Section Name should generally be descriptive of both the
Web Site and Sub-site it belongs to: for example if my web site is
called "The Great Dividing Range" then my Section might be
called "The Great Dividing Range - about".
•
Supply here the base URL for the Site or Sub-Site
•
Specify the physical location of your staging_directory.
You will see the Section Set-up page.
3
Click on the browser REFRESH button. You should see the new website and
sections appear on the left hand navigation panel.
4
Against each new sub-site you should now see a Pub/Dest. The Publishing
destination specifies the specific security configuration (usually ftp) for a
particular sub-site. Click on the Pub/Dest link and click Edit to enter the
required publishing details. Supply the Server Name, UserID and Password
for FTP access to each site in the Publishing Destination entry. If you have a
default publishing destination established, your entries should appear here
automatically. A default publishing destination is created with the name
“Default http://mysite” and will be use to obtain default ftp access details for all
subdirectories created thereafter.
Well done! Your site is ready for publishing. The remaining stages involve the
definition of your graphical design templates. The system has a prototype site,
which you can use to "inherit" a set of useful site features. At this stage you
may wish to use the site replication features to copy across these features to
your new site.
To use the site replication features, click on Site Set-up link
from the Main Menu. Click on the Replicate link. You will be asked to map
the source and destination Clients, Web sites and sections. All contents will be
transferred from the source to target sections, with URL's and other text
5
© Prosentient Systems Pty Ltd 2003
Page 8
COMMERCIAL IN CONFIDENCE
This document may only be reproduced with the permission Prosentient Systems Pty Ltd
Inter-Publish — System Administration
changes applied.
6
Your graphical designers should now establish default design templates for
each section.
7
Once the graphical designers have created the default templates, you should
register these defaults in the Section configuration for each sub-site.
8
If any sub-sites will publish Microsoft Active Server Pages as ".htm" pages, you
will need register ".htm" to use the asp scripting functions:
♦ Run the IIS Server Manager
♦ Right click on the site within IIS and click Properties
♦
♦
♦
♦
Click on the Home Directory Tab
Click on the Configuration button
Click on the Add button
Fill out the entry as follows:
♦
♦
♦
Click OK on the above form
Click APPLY then OK to close the Application configuration window.
Click OK to close the Website Properties window.
© Prosentient Systems Pty Ltd 2003
Page 9
COMMERCIAL IN CONFIDENCE
This document may only be reproduced with the permission Prosentient Systems Pty Ltd
Inter-Publish — System Administration
9
If you are using Indexing server on your external website, follow the
instructions in the next section on Indexing Server configuration.
© Prosentient Systems Pty Ltd 2003
Page 10
COMMERCIAL IN CONFIDENCE
This document may only be reproduced with the permission Prosentient Systems Pty Ltd
Inter-Publish — System Administration
3
Inter-Publish Security
and User Management
Aim
This section examines Inter-Publish security configuration and user management.
User Security
The Inter-Publish database is divided into Clients, Divisions (usually known as Web-Sites, eg
http://www.prosentient.com.au/eptraining/English) and Sections (usually sub-sites on a site, eg
http://www.prosentient.com.au/eptraining/English/about). The Inter-Publish client interface manages
security at the Section level. Users can be granted access to specific Sections across any relevant
Web Sites.
Users are limited in access to only those Sections within a specific Client that they have
access to.
There are four classes users in Inter-Publish:
•
•
•
•
Global Administrators - who have access to all clients and sites. No special
configuration is needed for access to specific Sections. Global Administration functions
would generally be restricted to personnel responsible for system maintenance, backup
and administration and those who are establishing new Clients.
System Administrators - who have universal access to all information for a specific
Client. System Administrators are generally those who are responsible for the creation of
new users and establishment of new sites within a given Client.
Editors - who are granted editing and publishing rights to specific Sections but cannot edit
Layouts and Indexes.
Designers - who have full access to editing and publishing both content and designs within
a specific Section.
User Administration is managed through the Access link on the Main Menu.
© Prosentient Systems Pty Ltd 2003
Page 11
COMMERCIAL IN CONFIDENCE
This document may only be reproduced with the permission Prosentient Systems Pty Ltd
Inter-Publish — System Administration
Add a new User
To register a new Inter-Publish user, take the SETUP option from the main menu:
The NEW button allows you to register a new user.
You must then supply the details for the new user:
AuthorID: this will be the logon name of the user
Author First Name & Surname: it is important to supply these details. They are used
when you generate mail out from the system.
Author Email: this will be used for alerts and as the "From" address of emails generated
from the system.
Author Password: you may change this at any time.
Administrator options:
The following options will only appear for Administrators:
System Administrator: A system administrator has no publishing limitations within a
give n client.
Global Administrator: A global administrator may replicate content from other client
sites.
Limited To Author: Specifies that this user will only see documents that they create
& publish.
Click on the SAVE button to register this user.
© Prosentient Systems Pty Ltd 2003
Page 12
COMMERCIAL IN CONFIDENCE
This document may only be reproduced with the permission Prosentient Systems Pty Ltd
Inter-Publish — System Administration
Grant a User access to Sections
Users may be allocated access only to specific sections and divisions of your site. To administer user
access rights, take the SETUP option from the main menu:
You will see a list of currently registered users: Click on the “Sections” link for the author/editor whose
rights you wish to adjust:
The Sections link will take you to a list of sub-sites. You may allocate the user access at one of the
following levels:
Edit: allows the user to edit content but not change layouts/designs.
Design: the user can change layouts as well as content
Site Administrator: a shortcut to granting access to all sections within the
Site, with some additional site set-up privileges.
Click on the SAVE button when you have finished making your changes.
© Prosentient Systems Pty Ltd 2003
Page 13
COMMERCIAL IN CONFIDENCE
This document may only be reproduced with the permission Prosentient Systems Pty Ltd
Inter-Publish — System Administration
Delete a User
To register a new Inter-Publish user, take the SETUP option from the main menu:
You will see a list of currently registered users: Click on the “Edit” against the user you wish to delete.
Click on the Delete button to remove this user. You will be asked to confirm the choice:
Access for this user will be revoked immediately.
© Prosentient Systems Pty Ltd 2003
Page 14
COMMERCIAL IN CONFIDENCE
This document may only be reproduced with the permission Prosentient Systems Pty Ltd
Inter-Publish — System Administration
4
Global Updates
Aim
Inter-Publish has facilities for Inter-Publishing all or part of a site and for global text substitutions based
on complex search and replace rules. Global changes can be applied to all pages for an entire
website, or for specific sub-sections, or for all documents specified by a particular Collection.
The Global Change page
The Global Change function is reached from the Sections maintenance page. From the Home Page
click on the Sections link.
From the list of sections pick a sub-site and click on the Global Change link. The Global Change page
will appear:
© Prosentient Systems Pty Ltd 2003
Page 15
COMMERCIAL IN CONFIDENCE
This document may only be reproduced with the permission Prosentient Systems Pty Ltd
Inter-Publish — System Administration
This page specifies the limits to the global replace. You may select a specific language, document
Type and Element to change. You can then specify a particular section, all sections within a site, or a
collection to be used in conjunction with the Language, Document type and Element limitations that you
have selected. Note that selecting All Text Fields will apply your change to every content field.
You may then specify the original text and replacement text to be used in the replacement process.
The search is case-insensitive but the replaced text will appear exactly as shown in the Replacement
Text textbox.
The "Original text" can contain a range command in the format:
Startstring<<between>>endstring
In this format, any text between a fixed "Startstring" and "endstring" will be counted as a match.
The checkbox add this value to documents which do not have it allows the addition of a new field
to all documents which match your selection criteria.
You can force an update to all web pages (including those that use a layout which has changed) by
checking the checkbox autopublish documents, which have changed.
The training manual has instructions on establishing collections.
This function should be used with great caution. There is no simple undo – you
will have to use the Versions function to recover individual entries if you have
made a mistake.
Avoid changing ambiguous text entries.
The global change will search on partial matches within words, not on whole
words. Be careful of the results of a global change to a term that might be part
of other terms
Eg "late" is also part of "relate", "extrapolate", "inflate", etc
© Prosentient Systems Pty Ltd 2003
Page 16
COMMERCIAL IN CONFIDENCE
This document may only be reproduced with the permission Prosentient Systems Pty Ltd
Inter-Publish — System Administration
5
Customisation
Language & Terminology
Aim
Inter-Publish allows both individual and global customisation of the user experience. At the Client level
the language and terminology of the user interface can be customised. This allows the use of
business-specific terminology to describe structural elements of Inter-Publish (for instance, you may
wish to call Divisions “Web Sites” and “Sections” “Sub-Sites”). It also allows language-specific
translation of terminology and user interface messages, including language-specific images.
Language Localisation and Terminology customisation
To customise the terminology for Inter-P ublish, go into SITE SETUP.
Select the Localisation option under the Customisation heading:
You will see a terminology list for all terms appearing in the user interface. You may edit any one of
these and select a translation alternative or terminology redefinition for this term. For example, you
might want the term “Division” to appear as “Web site”. Find the term “Division” in the list and click on
“Edit”.
Under the heading “Translation” type the term you wish to use, and click Save. The change will only
take effect on the next Inter-Publish restart.
© Prosentient Systems Pty Ltd 2003
Page 17
COMMERCIAL IN CONFIDENCE
This document may only be reproduced with the permission Prosentient Systems Pty Ltd
Inter-Publish — System Administration
6
Customisation:
Tasks & Shortcuts
Aim
Inter-Publish allows both individual and global customisation of the user experience. The individual
user can add shortcuts to functions within Inter-Publish and links to other URL’s and functions that they
wish to perform. These will appear on the Shortcut list on the Home Page.
Creating Tasks & Shortcuts to external URL(s)
To customise the terminology for Inter-Publish, go into SITE SETUP.
Select the Localisation option under the Customisation heading:
You will see a list of current shortcuts. To add a new external shortcut to a URL, take the following
steps:
1.
2.
Click on the NEW button (
)
Give the shortcut a name - this name will appear on the Home Page Shortcuts menu and
select a Section to which the shortcut belongs. All users with access to that section will
see the shortcut, and click on the SAVE button.
© Prosentient Systems Pty Ltd 2003
Page 18
COMMERCIAL IN CONFIDENCE
This document may only be reproduced with the permission Prosentient Systems Pty Ltd
Inter-Publish — System Administration
3.
Define the URL or URL’s to be run when the user clicks on the shortcut:
i) Run this URL - select this option if you want a normal hyperlink to
any external website. Just paste the URL in the
Document/Index to Run field.
ii) Edit this Document. Just paste the Title of the Document for
which you want a shortcut to editing the document.
iii) Publish this Document. Just paste the Title of the Document for
which you need a shortcut to publishing.
iv) Run this Index. Paste the Title of the Index to be included
in the shortcut list.
4. Click on the SAVE button. The Shortcut will now appear.
Creating Edit/Publish shortcuts
Is easy! Find and edit the document to which you wish to have a shortcut. At the bottom of the document you
will see two buttons for creating an edit/publish shortcut for the item:
© Prosentient Systems Pty Ltd 2003
Page 19
COMMERCIAL IN CONFIDENCE
This document may only be reproduced with the permission Prosentient Systems Pty Ltd
Inter-Publish — System Administration
7
Configuring
Microsoft Indexing Server
Aim
This section is intended as a guide to configuring Microsoft Indexing Server for integration with InterPublish advanced search engine ASP integration features.
Indexing Server Set-up Checklist
ACTION
1
2.
3.
þ
Before you proceed with Indexing Server Set-up you will need:
• Be familiar with navigating and using Inter-Publish features
• To have created the relevant search directories on your external web
server
• Have a System Administrator account on Inter-Publish
• Have Administrator access to Indexing Server configuration on the
target web server.
Open the Indexing Server Administration Plug-In. In Widows 2000 run:
♦ Start
♦ Programs
♦ Administrative Tools
♦ Computer Management
♦ Open the Services and Applications tab
♦ Open the Indexing Service tab
Set up a catalogue specific to your new site:
© Prosentient Systems Pty Ltd 2003
Page 20
COMMERCIAL IN CONFIDENCE
This document may only be reproduced with the permission Prosentient Systems Pty Ltd
Inter-Publish — System Administration
4
Open your new Indexing Service site and create a Directory entry pointing to
the location of your web site:
♦ Open your new site entry
♦ Right click on the Directories entry and select Properties
♦ Click on New
♦ Click on Directory
♦ Supply the disk location of your website
5
Make sure Indexing Service is configured to generate abstracts:
♦ Right click on the site name
♦ Click on Properties
♦ Click on the Generation Tab
♦ Uncheck the Inherit above settings from Service checkbox
♦ Check the Generate Abstracts checkbox
♦ Click Apply
♦ Click on the Tracking Tab
♦ Select the tab to show your new website
♦ Click Close
♦ Stop and start the Indexing Services
♦ You should now see Indexing Service indexing your site
contents
♦ Note the directory location of the indexing server catalogue.
Your graphical designers will need this in their file definitions.
Register the Inter-Publish search plugin:
♦ Regsvr32 epsearch.dll
6
© Prosentient Systems Pty Ltd 2003
Page 21
COMMERCIAL IN CONFIDENCE
This document may only be reproduced with the permission Prosentient Systems Pty Ltd
Inter-Publish — System Administration
FAQ
Frequently Asked Questions
FAQ 1: SSL operation in IIS
If you are using Secure Server to protect access to an NT server website, and need to upgrade the
server, you will need to relocate the SSL certificate as well as relocating the Inter-Publish software.
In order to perform the backup, you must first create a new MMC and add the Certificates snap-in. You
can also add the snap-in to another MMC as long as it is opened in Author mode.
Use the following steps to create a new MMC and add the Certificates snap-in:
1.
Click Start , and then click Run.
2.
Type in "MMC.EXE" (without the quotation marks) and click OK.
3.
Click Console in the new MMC you created, and then click Add/Remove Snap-in.
4.
In the new window that appears, click Add.
5.
Highlight Certificates , and then click Add.
6.
Choose the Computer option and click Next.
7.
Select Local Computer on the next screen, and then click OK.
8.
Click Close , and then click OK.
9.
You have now added the Certificates snap-in, which will allow you to work with any certificates
in your computer's certificate store. You may want to save this MMC for later use.
Now that you have added the Certificates snap-in, you can export the key pair that your Web server is
using (the certificate and public key). To do this, perform the following steps:
1.
Open the Certificates (Local Computer) snap-in you added in the last section, navigate to
Personal, and then to Certificates.
2.
You will see your Web server certificate denoted by the CN (Common Name) found in the
Subject field of the certificate (using Internet Explorer 5.0, you can easily view the certificate to
see the Common Name if you are unsure).
3.
Right -click on the server certificate, select All Tasks, and then click Export.
© Prosentient Systems Pty Ltd 2003
Page 22
COMMERCIAL IN CONFIDENCE
This document may only be reproduced with the permission Prosentient Systems Pty Ltd
Inter-Publish — System Administration
4.
When the wizard starts, click Next. Choose to export the private key, and then click Next.
5.
The file format you will want to choose is the Personal Information Exchange (though you
can select from several options). This will create a PFX file. Notice that you can export any
certificates in the certification path by selecting the option on this screen. This is very handy if
your certificate was issued by a non-trusted certificate authority (for example, Microsoft
Certificate Server). Only choose delete the private key if the export is successful to be sure it is
not left on the computer (for example if your migrating from one server to another).
6.
Click Next, and then choose a password to protect the PFX file. You will need to enter the
same password twice to ensure that the password is typed correctly. When you have
completed this step, click Next.
7.
Choose the file name you want to save this as. Do not include an extension in your file name;
the wizard will automatically add the PFX extension for you.
8.
Click Next, and then read the summary. Pay special attention to where the file is being saved
to. If you are sure the information is correct, choose Finish.
9.
You now have a PFX file containing you server certificate and its corresponding private key. Be
sure to protect this file! You may want to move it to a floppy disk and store it somewhere safe
from outside disturbance. Keep in mind, if you run a backup on the server, this file may be
saved in that backup if it is still on the server.
You can now log into the new server. In order to view the Certificates store on the new computer,
perform the following steps:
1.
Click Start, and then click Run.
2.
Type "MMC.EXE" (without the quotation marks) and click OK.
3.
Click Console in the new MMC you created, and then click Add/Remove Snap-in.
4.
In the new window, click Add.
5.
Highlight the Certificates snap-in, and then click Add.
6.
Choose the Computer option and click Next.
7.
Select Local Computer on the next screen, and then click OK.
8.
Click Close , and then click OK.
9.
You have now added the Certificates snap-in, which will allow you to work with any certificates
in your computer's certificate store. You may want to save this MMC for later use.
Now that you have access to the Certificates snap-in, you can import the server certificate into you
computer's certificate store by following these steps:
1.
Open the Certificates (Local Computer) snap-in and navigate to Personal, and then
Certificates.
Note: Certificates may not be listed. If it is not, that is because there are no certificates
installed.
© Prosentient Systems Pty Ltd 2003
Page 23
COMMERCIAL IN CONFIDENCE
This document may only be reproduced with the permission Prosentient Systems Pty Ltd
Inter-Publish — System Administration
2.
Right -click Certificates (or Personal if that option does not exist.)
3.
Choose All Tasks, and then click Import.
4.
When the wizard starts, click Next. Browse to the PFX file you created containing your server
certificate and private key. Click Next.
5.
Enter the password you gave the PFX file when you created it. Be sure the Mark the key as
exportable option is selected if you want to be able to export the key pair again from this
computer. As an added security measure, you may want to leave this option unchecked to
ensure that no one can make a backup of your private key.
6.
Click Next, and then choose the Certificate Store you want to save the certificate to. You
should select Personal because it is a Web server certificate. If you included the certificates in
the certification hierarchy, it will also be added to this store.
7.
Click Next. You should see a summary of screen showing what the wizard is about to do. If this
information is correct, click Finish.
8.
You will now see the server certificate for your Web server in the list of Personal Certificates. It
will be denot ed by the common name of the server (found in the subject section of the
certificate).
Now that you have the certificate backup imported into the certificate store, you can enable Internet
Information Services 5.0 to use that certificate (and the corresponding private key). To do this, perform
the following steps:
1.
Open the Internet Services Manager (under Administrative Tools) and navigate to the Web site
you want to enable secure communications (SSL/TLS) on.
2.
Right -click on the site and click Properties.
3.
You should now see the properties screen for the Web site. Click the Directory Security tab.
4.
Under the Secure Communications section, click Server Certificate.
5.
This will start the Web Site Certificate Wizard. Click Next.
6.
Choose the Assign an existing certificate option and click Next.
7.
You will now see a screen showing that contents of your computer's personal certificate store.
Highlight your Web server certificate (denoted by the common name), and then click Next.
8.
You will now see a summary screen showing you all the details about the certificate you are
installing. Be sure that this information is correct or you may have problems using SSL or TLS
in HTTP communications.
9.
Click Next, and then click OK to exit the wizard.
You should now have an SSL/TLS -enabled Web server. Be sure to protect your PFX files from any
unwanted personnel.
© Prosentient Systems Pty Ltd 2003
Page 24
COMMERCIAL IN CONFIDENCE
This document may only be reproduced with the permission Prosentient Systems Pty Ltd
Inter-Publish — System Administration
FAQ 2: Co-existing with IIS/FTP
By default, Inter-Publish is installed on Internet Port 82. You can configure Inter-Publish to operate on Port 80,
the standard web server port. However, if you are running Microsoft Internet Information Server on the same
server, you may find that Inter-publish failes to launch with a “port already used” message.
By default Microsoft IIS occupies all available addresses when it runs. If you wish to run Inter-Publish on the
standard HTTP port 80, and operate on the same server as IIS, you can configure IIS to operate only on specific
allocated ports (ie, turn off connection pooling).
To turn off connection pooling:
1. Go to the command prompt and navigate to the Inetpub\Adminscripts folder.
For instance if your IIS installation is located on your C: drive type:
CD\Inetpub\Adminscripts
2. Type the following line:
cscript adsutil.vbs set w3svc/disablesocketpooling true
cscript adsutil.vbs set msftpsvc/disablesocketpooling true
3. The command should display the following:
disablesocketpooling: (BOOLEAN) True
4. Stop and start the IISAdmin service.
5. Change the web site to operate on a specific IP address rather than “all available”
6. Restart the WWW service.
Note: To enable socket pooling, type the same line substituting “false” for “true”:
cscript adsutil.vbs set w3svc/disablesocketpooling false
© Prosentient Systems Pty Ltd 2003
Page 25
COMMERCIAL IN CONFIDENCE
This document may only be reproduced with the permission Prosentient Systems Pty Ltd
Inter-Publish — System Administration
FAQ 3: Server.CreateObject error
When you instantiate a Visual Basic component from an Active Server Pages (ASP) page, you may receive the
following error:
Server object error 'ASP 0178 : 80070005'
Server.CreateObject Access Error
The call to Server.CreateObject failed while checking permissions. Access is denied to this object.
With Visual Studio 6.0 Service Pack 5 (SP5), you may receive the following error message:
Error number: -2147024891
ASP 0178 Server.CreateObject Access Error
The call to Server.CreateObject failed while checking permissions.
This error may occur after you install a new Visual Basic component on your Web server using a Standard Setup
Package that was created on a computer with Microsoft Visual Studio 6.0 SP4 or SP5.
CAUSE
The authenticated user for the Visual Basic (VB) run-time file (Msvbvm60.dll) does not have sufficient
permissions. The authenticated user is the IUSR_ computername account when you use anonymous access or the
user that is authenticated with the Web page.
RESOLUTION
To resolve this problem, assign Windows NT File System (NTFS) Read and Execute file permissions to the
Everyone group (or to the appropriate users) for VB run time (Msvbvm60.dll). VB run time is usually located in
the Winnt\System32 folder.
© Prosentient Systems Pty Ltd 2003
Page 26
COMMERCIAL IN CONFIDENCE
This document may only be reproduced with the permission Prosentient Systems Pty Ltd
Inter-Publish — System Administration
FAQ 4: Object not found error on editing/publishing
CAUSE
Some system objects failed to register during installation
RESOLUTION:
Try registering the following objects:
C:\winnt\system32\regsvr32 c:\winnt\system32\ipdaem40.ocx
C:\winnt\system32\regsvr32 c:\winnt\system32\ipport40.ocx
C:\winnt\system32\regsvr32 c:\winnt\system32\netcod40.ocx
C:\winnt\system32\regsvr32 c:\winnt\system32\smtp40.ocx
C:\winnt\system32\regsvr32 c:\winnt\system32\pop40.ocx
© Prosentient Systems Pty Ltd 2003
Page 27
COMMERCIAL IN CONFIDENCE
This document may only be reproduced with the permission Prosentient Systems Pty Ltd
Inter-Publish — System Administration
FAQ 5: Inter-Publish will not start
POSSIBLE CAUSE
You do not have MS XML services installed on the PC, or the XML services are for the wrong version.
RESOLUTION:
Backup your system before applying this fix.
In the windows system directory (\windows\system or \ winnt\system32) take the following steps:
a) rename the file msxml3.dll to oldmsxml3.dll
b) rerun the setupxml.exe program on the installation disk.
© Prosentient Systems Pty Ltd 2003
Page 28
COMMERCIAL IN CONFIDENCE
This document may only be reproduced with the permission Prosentient Systems Pty Ltd
Inter-Publish — System Administration
FAQ 6: "Systems Files are out of Date" with multiple
reboots
Symptoms
When you install a Microsoft Visual Basic application, you may receive the following message:
Setup cannot continue because some system files are out of date on your system. Click OK if you would like
setup to update these files for you now. You will need to restart Windows before you can run setup again.
Click cancel to exit setup without updating system files.
After Windows restarts and you begin the installation again, the error message appears again.
Cause
Both installation programs (ASW and PDW) use the same method to delay the replacement of in-use system files
until reboot. For any system files that are in use, the new files are saved as temporary files in the Temp folder. In
order to replace the existing files with the .tmp files, the system will use the Wininit.ini file on WIN 9x systems.
On Windows NT and Windows 2000, the system will call the MoveFileEx function with the
MOVEFILE_REPLACE_EXISTING flag. This function places the file replacement instructions in the following
registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations
If something interferes with this replace and rename operation, these files are not updated. Therefore, once the
computer reboots and restarts the installation program, the same error message appears.
There are a number of reasons why this can happen, but the two most common are as follows:
The .tmp files are being deleted.
The Temp folder is on a different drive or partition from the operating system. By default, the operating system is
installed to either the Windows or Winnt folder.
Resolution
The following are resolutions to this problem:
The following are resolutions to this problem:
1.
Copy the TEMP and TMP environment variables to a folder that is in the same drive partition as
the Windows system files. To do this, open a command prompt window and type the following at
the prompt:
Set TMP=C:\TEMP
Set TEMP=C:\TEMP
This will save the TEMP and TMP environment variables to a folder named "Temp" that resides
on the C: drive.
NOTE: The folder must exist prior to carrying out these steps.
Once these environment variables are set, the application should then install and continue past
the message on reboot.
2.
If your Autoexec.bat file contains the following line (or similar):
If exists c:\temp \*.tmp del c:\temp \*.tmp
comment it out by placing "REM" in front of it.
© Prosentient Systems Pty Ltd 2003
Page 29
COMMERCIAL IN CONFIDENCE
This document may only be reproduced with the permission Prosentient Systems Pty Ltd
Inter-Publish — System Administration
3.
Disable any Anti-virus software (or other memory resident programs) and try running Setup
again. Often the best way to accomplish this is to run setup in Safe Mode. It may also be
necessary to copy all of the setup files to a temporary folder on the hard drive disk and run
Setup.exe from there.
4.
Leftover files from a failed Setup attempt can also cause this problem. If found, delete the
msftqws.pdw subfolder and its contents from the Temp folder. Also look in the Windows or
Winnt folder for Setup1.exe and any *.CAB files from previous installs , and delete them. This
should be done after each failed install.
5.
Some logon scripts can cause this problem, so try to run Setup before logging on to the network.
6.
Make sure you are deploying the same file versions that you are using on your development
machine. The wizards have a special folder where they look first for files to package. If found, a
file is used from this source instead of the file your system is running.
For Visual Basic 6.0, it is especially important to make sure that you are deploying the proper
version of Mdac_Typ.exe. The version of this file should match the Reference to "Microsoft
ActiveX Data Objects 2.x Library" in your project. The default locations for this folder are as
follows:
For Visual Basic 5.0:
C:\Program Files\DevStudio\ VB\setupkit\kitfil32\sys32
For Visual Basic 6.0:
C:\Program Files\Microsoft Visual Studio\ VB98\Wizards\PDWizard\ Redist
7.
The system files that may need to be updated are listed in the Bootstrap or Bootstrap Files
section of the Setup.lst file created with your package. These files can also be installed separately
from self-extracting files found on Microsoft's support web site. Please see the References
section for information about obtaining these files.
8.
You can also edit the Setup.lst file. Look in the Setup1 Files or Files section for files to be copied
to either $(WinSysPath) or $(WinSysPathSysFile). For example, Msvcrt.dll and Mfc42.dll. You
can copy these lines to the end of the Bootstrap or Bootstrap Files section. You must renumber
these lines so that the File numbers are sequential, for example "File1=...", File2=..." and so on.
If these lines are removed from their original section, the remaining lines must be renumbered to
maintain a sequential list.
See also on the Microsoft support website:
Q140570 HOWTO: Move Files That Are Currently in Use
Q174135 PRB: Setup Cannot Continue...System Files Are Out of Date
Q189743 INFO: Description of Setup.lst Sections
Q180071 FILE: Msvbvm50.exe Installs Visual Basic 5.0 Run-Time Files
Q192461 FILE: Visual Basic 6.0 Sample Installs Run-Time Files
Q290887 FILE: VBRun60sp5.exe Installs Visual Basic 6.0 SP5 Run-Time Files
Q279764 PRB: Multiple "System Files Are Out of Date" Errors When Visual Basic 6.0 Application
Installed on Windows 2000 Computer
© Prosentient Systems Pty Ltd 2003
Page 30
COMMERCIAL IN CONFIDENCE
This document may only be reproduced with the permission Prosentient Systems Pty Ltd
Inter-Publish — System Administration
FAQ 7: “Socket” error when you click the REGISTER or
CONFIGURE button
POSSIBLE CAUSE
Your server does not recognise local host or will not allow access to the default installation port 81.
RESOLUTION (1):
Port 81 is already occupied
Use NOTEPAD to edit the configuration file in your installation directory called epublish.ini. Try a different port
(eg 82) – change the following line FROM:
<WebServerPort>81</WebServerPort>
to
<WebServerPort>82</WebServerPort>
© Prosentient Systems Pty Ltd 2003
Page 31
COMMERCIAL IN CONFIDENCE
This document may only be reproduced with the permission Prosentient Systems Pty Ltd