OrgPublisher 11 Client and Web Administration for Server 2003 Installation Guide

(1)

OrgPublisher

11 Client and

Administration Web

for Server 2003

Installation

Guide

(2)

Table of Contents

OrgPublisher Installation

The purpose of this document is to provide the information needed to

successfully install OrgPublisher on a workstation (referred to as an OrgPublisher Client installation) or to install OrgPublisher with Web Administration.

If installing OrgPublisher with Web Administration, refer to the instructions corresponding to the type of server where OrgPublisher is to be installed.

Windows Server 2003 – installation instructions for this server is included in this document.

Windows Server 2008 Windows Server 2008 R2

OrgPublisher Client versus OrgPublisher Web

Administration Installation

Each OrgPublisher license covers one installation of OrgPublisher which can be activated by either:

1. Installing OrgPublisher on a workstation (referred to as OrgPublisher Client installation).

2. Installing OrgPublisher on a server with Web Administration.

One Web Administration OrgPublisher license allows up to five chart administrators to access the OrgPublisher Web Administration access.

OrgPublisher Client OrgPublisher Web Administration Installation • User desktop (uncommon)

• Server – Chart

administrator access via:

o VPN

o Remote desktop o Server login

• Server

• Chart administrator is provided a link to access

• License allows for 5 simultaneous connections Primary

Purpose • Centralize all charting activities to one or two users:

o Data connection to one or more data sources

o Formatting o Publishing o Scheduling o One-off chart

creation

• Data connection to one or more data sources

generated by IT on the Web Administration Server

• Access to data source provided by a link to multiple administrators:

o To format and manually publishing the chart to multiple people

o Save a copy of the data for single

(5)

OrgPublisher Installation OrgPublisher Client OrgPublisher Web

Administration

one-off chart creation Chart

Manageme nt

• Chart administrator has

total control • Chart administrator has restricted control

Scheduling • Chart administrator can schedule the publishing of the chart

• Chart administrator requests the setup of the publishing schedule by IT group responsible for the Web Adminsitration Server

Data • Chart administrator can access data from any source

• Chart administrator can use .csv files prepared in order specified by

OrgPublisher

• ODB compliant data sources

Field Mapping &

Multiple Data Sources

• Chart administrator can create multiple charts from a single .csv data

extraction by mapping fields with the built-in connector

• Chart administrator can map additional .csv source files into an existing chart

• Chart administrator can only map needed fields and bring in secondary data sources that are ODB compliant

• If a secondary data source is needed for the chart that is provided as a .csv file, the IT group responsible for the Web Administrator Server must set this up for the chart administrator. This is done by logging on to the server and using the client to create the connection mappings Published

Chart Location

• Chart administrator controls where the charts are published

• All source data files and published charts are stored automatically in specific folders

established at installation

Role Requirements for Installation

The type of permissions required to successfully install OrgPublisher varies depending on the chosen installation method.

(6)

OrgPublisher Installation

OrgPublisher Client Role Requirements

• The user must be an administrator on the workstation where installing OrgPublisher.

OrgPublisher with Web Adminsitration Role Requirements

• The user must be an administrator on Web Adminsitration

• The administrator on the Domain Controller must complete Creating the Global Group (OPWeb_GG) on the Domain Controller.

OrgPublisher System Requirements

Prerequisites for Installation

The following items are required to ensure the installation process is successful.

• Valid license key information to activate OrgPublisher, which includes:

– License Key: provided via email

– Registered Company Name: company name, exactly as it appears in the license key email

• If upgrading from a previous version of OrgPublisher, review the OrgPublisher Upgrade Considerations prior to installation.

• If installing OrgPublisher with Web Adminsitration, complete the following items prior to installation:

– Confirm the server meets all Web Adminsitration server requirements – Complete the setup of the Global Group (OPWeb_GG) described in

Configuring Groups

Note: Both OrgPublisher Client and OrgPublisher Web Adminsitration installation options are available with the OrgPublisher trial.

Note: if an error displays during the OrgPublisher Client

installation, this indicates the user is not an administrator on the workstation. Contact a member of the IT department with

administrator permissions to complete the OrgPublisher Client installation.

Note: The OrgPublisher Web Adminsitration Server is disabled for Windows® Vista® operating system.

Note: The administrator on the server must have administrator on the Domain Controller create the Global Group (OPWeb_GG).

(7)

About Installing the OrgPublisher Trial

About Installing the OrgPublisher

Trial

To download a trial of OrgPublisher, visit the web site link at:

OrgPublisher Premier trial Download

After submitting a trial download request, an email message with an

OrgPublisher trial product key is sent to activate and begin the OrgPublisher trial.

The OrgPublisher Client and OrgPublisher Web Adminsitration installation methods are available using the OrgPublisher trial.

After purchasing the retail version of OrgPublisher, a new email message is sent to the registered owner containing the following license key information:

• New retail license key

• Registered company name

• Download instructions

The full version of OrgPublisher can be enabled by entering the new retail license key into the existing OrgPublisher trial using the following directions.

Converting the OrgPublisher trial to the Retail

Version

Convert the OrgPublisher trial to the full retail version suing one of these methods.

Activation Option 1

While your trial version is in effect, each time OrgPublisher is opened, the OrgPublisher Trial Version dialog opens:

Figure 1.

1. Click Enter New Key.

The License Key Entry dialog opens.

2. From the e-mail you received with your License Key, copy and paste the following information:

(8)

About Installing the OrgPublisher Trial – Registered Company Name

Figure 2.

Click OK.

3. Close and reopen OrgPublisher so that the change takes effect.

Activation Option 2

1. Open the OrgPublisher trial.

2. From the Help menu, select License Information.

The Licensing Information dialog opens.

Figure 3 3. Click Enter new key.

The License Key Entry dialog opens.

Figure 4

4. From the email, copy and paste the following information:

– Retail License key

– Registered Company Name

(9)

About Installing the OrgPublisher Trial Click OK.

5. Close and reopen OrgPublisher so that the change takes effect.

(10)

OrgPublisher Client Installation

Prior to installation, review the following information:

• Prerequisites for Installation

• Role Requirements

• System Requirements

1. From the computer where OrgPublisher will be installed, click the OrgPublisher download link within the license key email. Select the download link for the language of the OrgPublisher application preferred.

2. The download prompt opens. Click Run to begin the installation or Save to save the executable file and begin installation later.

Figure 3.

The Activation Information dialog opens.

Figure 5

3. Copy and paste the License key and your Registered Company Name from the email into the appropriate fields.

Click Next. The Welcome! dialog opens.

Note: The retail/trial license key unlocks the appropriate

connectors or Premier functionality. Download the OrgPublisher Premier Trial.

Note:These values must be exactly as they appear in the license key email to avoid invalid key errors.

(11)

OrgPublisher Client Installation Click Next again. The License Agreement dialog opens.

Figure 7

4. Read and accept the agreement by clicking Agree.

The Registration Information dialog box opens.

Figure 8

5. Type the Registered user’s full name and the Registered user’s company name. Click Next.

The Installation Option dialog opens.

Figure 9 6. Select OrgPublisher Install and click Next.

The Select Destination Directory dialog opens.

(12)

OrgPublisher Client Installation

Figure 10

7. Accept the default path, or type or Browse to a different path installation directory path. Click Next.

An

Installing window opens and provides a progress status as OrgPublisher is installed.

The Installation Completed dialog opens to confirm that OrgPublisher installed successfully.

Figure 4.

8. Select or clear options, as preferred:

• Create OrgPublisher icon(s) on your Desktop

• Launch OrgPublisher now

• View Getting Started Guide Click Finish.

The OrgPublisher Client is now installed.

Note: If an error message displays at this point in the installation, contact a member of the IT department who can login with

administrator permissions to complete the installation.

Note: The OrgPublisher Getting Started guide and User Manual also can be access in the application through Help menu options.

(13)

OrgPublisher Web Administration Installation

OrgPublisher Web Administration

Installation

Prior to installation, review the following information:

• Prerequisites for Installation

• Role Requirements

• System Requirements

Verify the type of server where OrgPublisher with Web Administration will be installed. The directions in this guide are valid only with Windows® Server 2003.

You can access OrgPublisher Web Installation for:

• Windows® Server 2008

• Windows® Server 2008 R2

Installing OrgPublisher Web Administration for

Windows® 2003 Server

1. On the server, click the download link within the license key email message.

Select the download link for the language of the OrgPublisher application preferred.

2. Click Run in the download prompt to begin the installation, or Save to save the executable file and begin the installation later.

Figure 5.

The OrgPublisher Installation wizard opens to the Activation Information dialog.

Note: The retail/trial license key unlocks the appropriate

connectors or Premier functionality. Download the OrgPublisher Premier Trial.

(14)

Figure 6.

3. Copy and paste the License Key and the Registered Company Name in the appropriate fields.

Click Next. Click Next again in the Welcome dialog.

The Licese Agreement dialog opens.

Figure 7.

4. Read and accept the agreement by clicking Agree.

The Registration Information dialog opens.

Figure 8.

Note:These values must be exactly as they appear in the license key email to avoid invalid key errors.

(15)

OrgPublisher Web Administration Installation 5. Type the:

– Registered user’s full name – Registered user’s company name Click Next.

The Custom Installation Option dialog opens.

Figure 9.

6. Select the OrgPublisher Custom Install radio button and click Next.

The Select Web Administration Destination Directory dialog opens.

Figure 12

7. Type \opweb at the end of your path, C:\inetpub\wwwroot.

Click Next. The Enter the Web Administration URL dialog opens.

Note: If this path is not entered correctly, OrgPublisher displays an error meesage when launching Web Administration.

(16)

Figure 10.

8. Type /opweb at the end of the URL path, http://ServerName.

Click Next.

The Select Destination Directory dialog opens.

Figure 14

9. Accept the default path (C:\Program Files\OrgPubX) or type or Browse to the directory path for installation.

Click Next. The application installation begins.

When the install is complete, the Installation Completed dialog opens.

Note: The ServerName is the server name where OrgPublisher is being installed. The URL is a virtual path that points to the physical path entered in the previous step.

If this path is not entered correctly, OrgPublisher displays an error message when launching Web Administration.

(17)

Figure 11.

10. Select Launch OrgPublisher now in order to create a DCOM entry.

OrgPublisher opens. Close the application.

11. Browse to the Web Administration Destination Directory path c:\inetpub\wwwroot\opweb, as entered in step 6 above.

The following folders and files are created by the Web Administration installation:

– ArchivedCharts folder – PublishedCharts folder – SearchDictionary folder – SourceCharts folder – OPAdmin.htm – OPAdmin.js – OPAdmin.opw – Remoteserver.dll

Figure 16

Note: Launching OrgPublisher is required to create the DCOM entry, which is needed later in the Web Administration installation.

(18)

Configuring Groups

The following groups are required to set up access to OrgPublisher Web Administration.

Create a Global Group on the Domain Controller

1. Create a global group titled OPWeb_GG by adding the OrgPublisher chart administrators to the global group.

Figure 12.

2. Create a local group on the Web server by clicking Start on the taskbar, then All Programs, Administrative Tools, and Computer Management.

3. Expand Local Users and Groups in the left pane of the Computer Management window and select Groups.

4. Select Action, then New Group.

Note: The OPWeb_GG group must be created by an administrator on the Domain Controller.

Note: The OPWeb_LG group must be set up by an administrator on the Server. Setup of the OPWeb_LG group must be

completed prior to moving on with the installation.

(19)

Figure 13.

The New Group dialog opens.

5. Type OPWeb_LG in the Group Name field and click Add.

6. Select the Domain Global Group (OPWeb_GG) and click OK.

7. In the New Group dialog, select Create. The OPWeb_LG group appears in the list of Local Groups.

Figure 14.

Setting NTFS Permissions

NTFS permissions must be configured to access and secure OrgPublisher Web Administration.

Setting NTFS Permission for the OPWeb Folder

1. Navigate to C:\inetpub\wwwroot.

2. Right-click on the opweb folder and select Properties.

(20)

OrgPublisher Web Administration Installation 3. Select the Security tab and click Edit.

4. Click Add and then, in the resulting dialog, click Locations.

5. In the Locations dialog, change the Location to Server.

Figure 16.

Click OK.

6. In the Select Users or Groups dialog, click Advanced, then Find Now.

Figure 17.

7. Select the following groups from the search results.

– Loca Administrators – OPWeb_LG

– Network Service

– IIS_WPG (Workers Process Group) Click OK to add the groups.

8. Set the following NTFS permissions for the OPWeb folder.

– Local Administrators group Full control

– OPWeb_LG group Modify

– Network Service group Read and Execute

– IIS_WPG group Read and Execute

9. Remove the Everyone group from this folder.

Setting NTFS Permissions for the SourceCharts Folder

1. Navigate to C:\inetpub\wwwroot\opweb.

2. Right-click on the SourceCharts folder and select Properties.

(21)

OrgPublisher Web Administration Installation 3. Repeat steps 3 – 9 in the Setting NTFS Permission for the OPWeb Folder

procedure for the SourceCharts folder.

Setting NTFS Permissions for the AchivedCharts Folder

2. Right-click on the ArchivedCharts folder and select Properties.

3. Repeat steps 3 – 9 in the Setting NTFS Permission for the OPWeb Folder procedure for the ArchivedCharts folder.

Setting NTFS Permissions for the SearchDictionary Folder

2. Right-click on the SearchDictionary folder and select Properties.

3. Repeat steps 3 – 9 in the Setting NTFS Permission for the OPWeb Folder procedure for the SearchDictionary folder.

Setting NTFS Permissions for the Published Charts Folder

1. Navigate to C:\inetpub\wwwroot\opweb.

2. Right-click on the PublishedCharts folder and select Properties.

3. Repeat steps 3 – 6 in the Setting NTFS Permission for the OPWeb Folder procedure for the PublishedCharts folder.

4. Select the following groups from the search results:

– Local Administrators – OPWeb_LG

– Network Service – IIS_WPG

– Users

Click OK to add the groups.

5. Set the following NTFS permissions for the PublishedCharts folder:

– Local Administrators group Full Control

– OPWeb_LG group Modify

– Network Service group Read and Execute

– IIS_WPG group Read and Execute

– Users group Read and Execute

6. Verify that the Everyone group in this folder has only Read and Execute permissions. Removing the Everyone group is not required as long as the permissions are only set for Read and Execute.

(22)

Web Administration NTFS Rights

Figure 18.

(23)

Web Administration NTFS Rights

(24)

Configure Internet Information Services (IIS)

Configure Internet Information

Services (IIS)

Creating the OrgPublisher Application Pool

1. In IIS, expand the Server, then Application Pools.

2. Right-click on Application Pools and select New, then Application Pool.

Figure 19.

3. Type OrgPublisher in the Application pool ID field and select Use default settings for new application pool.

Figure 20.

Configuring the OPWeb Directory in IIS

1. In IIS, expand Web Sites. Right-click on the OPWeb folder and select Properties.

(25)

Figure 21.

The OPWeb Properties dialog opens.

2. Select Read in the Local path section.

Figure 22.

3. In the Application settings section, click the drop-down arrow in the Execute permissions field and select Scripts and Executables.

4. Click the drop-down arrow in the Application pool field and select OrgPublisher.

5. Select the Directory Security tab.

6. Click Edit in the Authentication Methods dialog, and verify the Enable anonymous access check box is CLEARED.

(26)

Figure 23.

7. Select Integrated Windows authentication in the Authenticated access section.

8. Select the HTTP Headers tab and click MIME Types in the MIME types section.

9. In the resulting dialog, click New.

Figure 24.

10. Type .ocp in the Extension field.

11. Type application/orgpublisher in the MIME type field.

12. Click OK three time to to close the OPWeb Properties dialog.

(27)

Configuring the SourceCharts Folder in IIS

1. In IIS, expand the OPWeb virtual directory, right-click on SourceCharts and select Properties. The SourceCharts Properties dialog opens at the Directory tab.

2. Select the Read check box in the Local path section.

5. Click Edit in the Authentication and access control section. The Authentication Methods dialog opens.

6. Verify that the Enable anonymous access check box is CLEARED.

7. Select Integrated Windows authentication in the Authenticated access section, and click OK until you close the SourceCharts Properties dialog.

Configuring the ArchivedCharts Folder in IIS

1. In IIS, expand the OPWeb virtual directory, right-click on ArchivedCharts and select Properties. The ArchivedCharts Properties dialog opens at the Directory tab.

7. Select Integrated Windows authentication in the Authenticated access section, and click OK until you close the ArchivedCharts Properties dialog.

Configuring the SearchDictionary Folder in IIS

1. In IIS, expand the OPWeb virtual directory, right-click on SearchDictionary and select Properties. The SearchDictionary Properties dialog opens at the Directory tab.

7. Select Integrated Windows authentication in the Authenticated access section, and click OK until you close the SearchDictionary Properties dialog.

Configuring the PublishedCharts Folder in IIS

1. In IIS, expand the OPWeb virtual directory, right-click on PublishedCharts and select Properties. The PublishedCharts Properties dialog opens at the Directory tab.

(28)

Configure Internet Information Services (IIS) 3. In the Application settings section, click the drop-down arrow in the Execute

permissions field and select Scripts and Executables.

Figure 25.

6. Verify that the Enable anonymous access check box is SELECTED.

7. In the User name field, verify that the IUSR account is selected.

8. Select Integrated Windows authentication in the Authenticated access section, and click OK until you close the Authentication Methods dialog.

9. Select the HTTP Headers tab and click MIME Types in the MIME types section.

Figure 26.

10. Click New in the resulting window.

11. Type .ocp in the Extension field in the MIME Type dialog.

12. Type application/orgpublisher in the MIME type field.

(29)

13. Click OK three times to close the PublishedCharts Properties dialog.

Enabling All Unknown ISAPI Extensions

1. In IIS, select the Web Service Extensions folder.

2. In the Web Service Extensions list, right-click on All Unknown ISAPI Extensions and select Allow.

3. At the security prompt, click Yes to enable all unknown ISAPI extensions.

Figure 27.

When Allow All Unknown ISAPI Extensions is

Restricted

The directions below are intended for organizations that cannot set All Unknown ISAPI Extensions to Allow. When a new chart is published, a dll file is produced. This is visible in the ECharts folder (C:\inetpub\wwwroot\ECharts).

Note: These steps enable ALL Unknown ISAPI extensions to run on the web server. If your IT security policy restricts allowing all ISAPI extensions, please refer to When Allow ALL Unknown ISAPI Extensions is Restricted section for an alternate configuration.

The directions in this section require a one-time setup by the Web Server administrator. Using the alternate setup, the Web Server administrator must enable each chart .dll web extension each time a new chart is published by the chart administrator.

If you are unsure which setup to use, contact your Domain

administrator to clarify which directions meet the requirements of your IT security policy.

(30)

Figure 28.

Configure the chart.dll each time a new EChart is published (producing a new chrt.dll). The Web Server administrator must follow the directions below.

1. Open IIS and select Web Service Extensions.

2. Under Tasks, click Add a new Web service extension. The New Web Service Extension dialog opens.

3. In the Extensions name field, type the new dll name (example:

PacificEastern.dll).

4. Click Add.

The New Web Service Extension dialog opens.

5. Type the path to the new chart dll in the Extension name field then click OK.

Example: C:\inetpub\wwwroot\ECharts\PacificEastern.dll

Note: If you followed the directions in the section above, Enable All Unknown ISAPI Extensions, skip this section and continue with Setting Up DCOM Permissions.

Using the configuration in this section, the Web Server administrator must enable each chart.dll web extension when new charts are

published by the chart administrator. You will not be able to complete this section until and EChart has been published.

If you are unsure which setup to use, contact your Domain

administrator to clarify which directions meet the requirements of your IT security policy.

Note: Each time a new chart is published (and a new dll is produced), the administrator must follow Steps 1-6 in this section. If not done, end users cannot view the EChart.

(31)

Figure 29.

6. Select the Set extension status to Allowed check box. Click OK.

Setting Up the Remoteserver.dll Web Extension

1. Open IIS and click Web Service Extensions.

2. In the Tasks section, click Add a new Web service extension.

3. In the Extension name field, type remoteserver.dll and click Add.

4. Type C:\inetpub\wwwroot\opweb\remoteserver.dll and select the Set extension status to Allowed check box.

Figure 30.

Setting Up the Published Chart.dll

When a new chart is published, a .dll file is produced. This file is visible in the PublishedCharts folder (C:\inetpub\wwwroot\opweb\PublishedCharts).

Note: If you have not yet published a chart to the PublishedCharts folder, proceed to Setting Up DCOM Permissions.

(32)

Figure 31.

1. Open IIS and click Web Services Extensions.

2. Under Tasks, click Add a new Web service extension. The New Web Service Extension dialog opens.

3. The the new dll name in the Extension name field and click Add.

Figure 32.

The Add file dialog opens.

4. Type or Browse to the path to the new chart dll and click OK.

5. Select the Set extension status to Allowed check box and click OK.

Setting Up DCOM Permissions

1. Launch OrgPublisher on the server. Close the application after it opens.

2. In the taskbar, click Start and select Run.

3. Type dcomcnfg in the Open field and click OK.

Note: Each time a new chart is published (and a new dll is

produced), the administrator must follw steps 1–5 of this procedure to allow the dll. If not, users are unable to view the EChart.

(33)

Figure 33.

4. Expand Component Services, Computers, and My Computer, then click DCOM Config.

5. Navigate to OrgPublisher X Document and right-click on Properties.

Figure 34.

The OrgPublisher X Document Properties dialog opens.

6. Select the Security tab and click Edit in the Launch and Activation Permissions section.

Note: if you installed a previous version of OrgPublisher on your computer, you see OrgPublisher X Document, where X is the previous version number. Use that document version.

(34)

Configure Internet Information Services (IIS) 7. Click Add, then Locations, and change the Location to the Server.

Figure 36.

8. Click Advanced in the Select Users or Groups dialog, then click Find Now.

Figure 37.

9. Add the following groups from the search results:

– Local Administrators – Local Interactive – Local IUSR – Local IWAM – Local Network

– Local Network Services – Local OPWeb_LG

– Local System

Figure 38.

(35)

10. Enable the following Launch and Activation Permissions:

– Local OPWeb_LG group All options

– Local Administrators group Local Launch

– Local Interactive group Local Launch

– Local IUSR account Local Launch

– Local IWAM account Local Launch

– Local Local Network group Local Launch

– Local System group Local Launch

11. Click Edit in the Access Permissions section.

Figure 39.

12. Click Add, then click Locations and change the Location to Server.

Figure 40.

13. In the Select Users or Groups dialog, click Advanced, then Find Now.

Figure 41.

(36)

Configure Internet Information Services (IIS) 14. Select the following grousp from the search results:

– Local Administrators – Local Interactive – Local IUSR – Local IWAM – Local Network

– Local Network Services – Local OPWeb_LG

– Local System

Figure 42.

15. Enable the following Access Permissions:

– Local OPWeb_LG group Both options

– Local Administrators group Local Access

– Local Interactive group Local Access

– Local IUSR account Local Access

– Local IWAM account Local Access

– Local Local Network group Local Access

– Local System group Local Access

Click OK to close the Access Permissions dialog. Click OK again to close the OrgPublisher X Document dialog.

Note: The Windows® 2003 OrgPublisher Web Administration setup is complete. Proceed to test Web Administration and EChart

publishing to verify a successful installation and configuration.

(37)

Test OrgPublisher Web Administration

The following tests will help you determine if Web Administration is configured correctly. If you can perform the tasks successfully, the OrgPublisher Web Administrationinstallation has been successful.

If error messages display while testing, review:

• NTFS permissions

• IIS configurations

• DCOM settings

• Troubleshooting tips

If you still cannot successfully publish an EChart, contact Product Support.

Prerequisites for Testing EChart Publishing

• We recommend that you test Web Administration on a workstation. In

addition, the Web server administrator may want to add their user account to the OPWeb_LG group for the purpose of accessing Web Administration with the same rights as the chart administrators.

• Users must have a Web Administration pluginx viewer, orgpub.ocx, in order to open an OrgPublisher Web Administration. Users are prompted to download the file when opening the chart for the first time.

• Users must be administrators on their machines in order to install the pluginx viewer.

• You can also refer to the OrgPublisher Implementation Guide for additional information on pluginx controls.

Testing Web Administration

1. Open Internet Explorer and type the URL for OrgPublisher Web Administration:

http://<servername>/opweb/opadmin.htm.

2. If prompted, install the Web Adminsitration pluginx file from the web site.

OrgPublisher opens.

Note: <servername> is the name of the server on which OrgPublisher is installed.

(38)

Figure 43.

Prerequisites for Testing Web Administration

Publishing to EChart Rich Client

• We recommend that you test Web Administration on a workstation. In

addition, the Web server administrator may want to add their user account to the OPWeb_LG group for the purpose of accessing Web Administration with the same rights as the chart administrators.

• Users must have a pluginx viewer, orgpub.ocx, in order to open an OrgPublisher EChart Rich Client. Users are prompted to download the file when opening the chart for the first time.

• Users must be administrators on their machines in order to install the pluginx viewer.

• You can also refer to the OrgPublisher Implementation Guide for additional information on pluginx controls.

Testing Publishing an EChart Rich Client Chart

1. In the Web Adminsitration URL (http://<servername>/opweb/opadmin.htm), select File then New.

The Select a Chart to Open dialog opens. Click New.

Figure 44.

The New Chart Wizard opens.

2. Select Organizational Chart and click Next.

Note: Click OK if a message displays that reads No charts exist yet.

(39)

Figure 45.

3. Select Empty chart and click Next.

Figure 46.

4. Clear the Launch the style wizard check box and click Finish.

Figure 47.

5. In the OrgPublisher toolbar, click the Insert Box Containing a Person button.

Figure 48.

6. Drop the box in the chart white space.

(40)

Test OrgPublisher Web Administration 7. Click the Publish button in the toolbar. The Publishing Wizard opens.

Figure 50.

8. Select Advanced Mode and click Next.

Figure 51.

Click Next again.

9. Type the Name of the test chart and click Next.

Figure 52.

10. Select Interactive Org Chart and click Next.

Figure 53.

11. Select EChart and click Next.

(41)

Figure 54.

12. Type the physical path to the ECharts folder on your server and click Next.

Figure 55.

13. Select Rich client using PluginX and click Next.

Figure 56.

14. Type the URL to the virtual path of the ECharts folder.

Figure 57.

15. Click Next through several dialogs until you reach the dialog with the publish options. Click Publish now.

(42)

Figure 58.

16. Type a chart name when prompted and click OK.

Figure 59.

17. Click the URL in the EChart Link Summary dialog.

Figure 60.

18. Install the pluginx viewer from the web site, if prompted.

The chart opens in the browser.

Note: If you did not enable all unknown ISAPI extensions in the server setup, you must configure the chart dll before you can view the published chart.

Refer to When Allow ISAPI Extensions is Restricted

(43)

Figure 61.

(44)

Web Administration Next Steps

Review the items below so your chart administrators have what they need to begin using charts with Web Administration.

• Provide the following link to the chart administrators:

– Web Adminsitration URL – example:

http://servername/opweb/opadmin.htm – PublishedCharts URL – example:

http://servername/opweb/publishedcharts

• Chart administrators will need assistance downloading the Web

Adminsaitration pluginx if they are not administrators on their machines.

• A system DSN must be created if the chart administrator uses an ODBC connection to a database.

• If a chart administrator uses a text or csv file that is not in the standard OrgPublisher field order, and administrator on the server must must map the files through the OrgPublisher client.

• A network share to the SourceCharts folder is needed for chart

administrators to import and overwrite existing data files from their destops to the SourceCharts folder from the Web Administration interface. Your IT department makes the decision to approve network share access, and is not part of the standard OrgPublisher Web Adminsitration installation.

• A network share to the PublishedCharts folder is required for chart

administrators to copy formatting files (otm files) to use with new chart data files. Your IT department makes the decision to approve network share access, and is not part of the standard OrgPublisher Web Adminsitration installation.

Note: We recommend that a default chart file be created one time on the server, using the OrgPublisher client, if the server

administrator needs assistance with mapping text files in OrgPublisher.

Open the default file, select File, then Save as, and create a new chart name for the file.

The data connection remains the same, and can now be used to create new organizational charts.

(45)

Troubleshooting Tips

1. If you see an Internet Explorer window with a grey bar at the top but no chart, set a MIME type of .OCP on the PublishedCharts folder.

Figure 62.

2. If you receive the error, “Unable to contact the remote server .dll at this URL,”

the paths to the virtual directory and URL were, likely, not entered correctly during installation, or the permissions are not set.

Figure 63.

This may require a re-installation by following this guide.

3. If a chart administrator or end user sees a blank Internet Explorer screen with a red X in the upper-left corner, this is an indicates a problem with installing and registering the ActiveX control (pluginx).

Figure 64.

Installing ActiveX controls requires administrative rights in the workstation.

Your IT group can request MSI scripts to assist in pushing out the plugins by contacting Product Support. Include the full version number of OrgPublisher installed on the server. (Select Help>About OrgPublisher.)

(46)

Troubleshooting Tips

Figure 65.

4. If you receive the error, “Unable to instantiate OrgPub32 as an automation server”, there may be a permission or installation error.

Figure 66.

Verify the DCOM permissions (mmc-32) are correct. If the error still occurs, adjust settings to include the following DCOM permission.

In the OrgPublisher X Document dialog, Identity tab, select the Launching User. If the error persists, this may require a re-installation, following this guide.

5. Understanding HTTP error messages and their associated status codes is

important when you need to troubleshoot IIS. A few common errors on the client side (4xx error) and server side (5xx error) are listed here.

Error Code Definition

400 Bad Request: the server cannot service the request, usually because of an incorrect URL.

401 Unauthorized: the user’s credentials were not accepted by the authorization process.

M403 Forbidden: the request could not be serviced for a number of reasons, even though the user was authenticated.

404 Not Found: the server cannot locate the requested file.

405 Method Not Allowed: the client incorrectly issued an HTTP GET request when an HTTP POST request should have been issued.

406 Not Acceptable: the requested file is not supported by the client.

407 Proxy Authentication Required: the client has to

authenticate with the proxy server before its request can be serviced.

(47)

Troubleshooting Tips 410 Gone: the server no longer has the requested file.

500 Internal Server Error: indicates a typical server side error.

501 501 Not Implemented: the server does not support the HTTP method requested by the client.

502 Bad Gateway: an invalid response was received by the upstream server for which this server is a gateway.

503 Service Unavailable: the server does not support the service requested by the client.