solution Contentsolution Content

HP Web Jetadmin - Deploy the Smart Client

HP Web Jetadmin uses the Microsoft ClickOnce Smart Client technology. This technology runs a Microsoft .NET Framework application by automatically downloading and starting the application through a web browser.

The Smart Client application runs as a local .NET Framework application on the host and uses .NET Remoting to communicate with the HP Web Jetadmin service. The following describes the interaction between the HP Web Jetadmin server and the Smart Client application:

  • The Smart Client application uses HTTP or HTTPS to initially contact the HP Web Jetadmin server. The default HTTP port is 8000. The default HTTPS port is 8443. You can change the default ports that the Smart Client application uses.

  • The HP Web Jetadmin server transfers approximately 2 MB of files for the Smart Client application to the client.

  • The Smart Client application runs on the client as the user who is logged in to the computer, executes commands that download approximately 50 MB of HP Web Jetadmin client files, and starts the graphical user interface for the HP Web Jetadmin client application. The web browser is now inactive.

    After the Smart Client application starts, the web browser is no longer required. Although HP Web Jetadmin also uses the web browser to deliver online Help and proactive Product Update notifications, the HP Web Jetadmin client application runs locally on the computer.

  • The HP Web Jetadmin server downloads all of the relevant information to the client. When new information is available, the HP Web Jetadmin server contacts the client and downloads the new information.

The HP Web Jetadmin installer builds a shortcut on the installation host to the following URL:

http://<ip_address>:8000/

The <ip_address> is the host where HP Web Jetadmin is installed. Use this URL to access HP Web Jetadmin remotely from anywhere on the company's intranet or WAN.

Only a web browser is required to start the Smart Client session. Administrator rights are not required to run Smart Client applications. However, .NET Framework must be installed. Local administrator rights might be required to install .NET Framework.

In most cases, the Smart Client session starts automatically. However, the local security settings on the workstation might prevent the application from starting automatically. For more information about changing the local security settings, see the Microsoft documentation.

Change the Default HTTP or HTTPS Port for the HP Web Jetadmin Smart Client Application

The HP Web Jetadmin Smart Client uses port 8000 for HTTP and port 8443 for HTTPS by default. You can change these default ports based on your company's requirements.

Use the following steps to change the default HTTP and HTTPS ports:

  1. Open Notepad or a similar text editor that has the appropriate create and edit permissions.

  2. From the File menu, select Open. The Open window opens.

  3. Navigate to the following directory:

    C:\Windows\ServiceProfiles\NetworkService\AppData\Local\HP Inc\HPWebJetadmin\WjaService\config

  4. Open the HP.Imaging.Wjp.Core.WebServer.config.xml file.

  5. Find the HttpsPort and HttpPort properties.

                      <property name="HttpsPort">
       <type>HP.Imaging.Wjp.Sdk.Core.Framework.ConfigurationItemString
       </type>
       <value>8443</value>
    </property>
    <property name="HttpPort">
       <type>HP.Imaging.Wjp.Sdk.Core.Framework.ConfigurationItemString
       </type>
       <value>8000</value>
    </property>
                    
  6. Change the <value> attributes to the HTTP and HTTPS ports to use for HTTP and HTTPS communication.

  7. From the File menu, select Save.

Run the Smart Client Application in a Workgroup

You can run the HP Web Jetadmin Smart Client application from a workgroup. You must first change the Microsoft security settings.

Tip:

For more information about the security policy settings, see the Microsoft documentation.

Use the following steps to change the Microsoft security settings:

  1. On the HP Web Jetadmin server, go to Start > Control Panel > System and Security > Administrative Tools.

  2. In the right pane, double-click Local Security Policy.

  3. In the left navigation pane, expand Local Policies, and then select Security Options.

  4. In the right pane, double-click Network access: Sharing and security model for local accounts.

  5. From the list, select the Classic - local users authenticate as themselves option.

  6. Click the OK button.

Start an HP Web Jetadmin Client Session

After the HP Web Jetadmin installation is complete, you can start an HP Web Jetadmin client session.

Choose one of the following methods to start a client session:

  • On the host where HP Web Jetadmin is installed, go to Start > HP Web Jetadmin 10, and then select HP Web Jetadmin.

  • From a supported web browser, access the following URL on the host where HP Web Jetadmin is installed:

    http://<ip_address>:8000

    In some cases, you might need to add the URL for HP Web Jetadmin to the trusted security zone in the web browser.

  • From the command line, issue the following command:

                      rundll32 dfshim.dll, ShOpenVerbApplication http://<ip_address>:8000/wja/wja.application?InternalErrorDetails=true
                    

    To start the HP Web Jetadmin client session in a specific language, use the following URLs. If the corresponding Windows language pack is installed, HP Web Jetadmin displays the content in that language. If the corresponding Windows language pack is not installed, HP Web Jetadmin displays the content in a mixture of English and the specified language.

    URLs to start HP Web Jetadmin in a specific language

    Language

    URL

    Chinese (Simplified)

    http://<ip_address>:8000/wja/wja.application?lang=zh-cn

    Chinese (Traditional)

    http://<ip_address>:8000/wja/wja.application?lang=zh-tw

    English (Worldwide)

    http://<ip_address>:8000/wja/wja.application?lang=en-us

    French (European)

    http://<ip_address>:8000/wja/wja.application?lang=fr-fr

    German

    http://<ip_address>:8000/wja/wja.application?lang=de-de

    Italian

    http://<ip_address>:8000/wja/wja.application?lang=it-it

    Japanese

    http://<ip_address>:8000/wja/wja.application?lang=ja-jp

    Korean

    http://<ip_address>:8000/wja/wja.application?lang=ko-kr

    Portuguese (Brazilian)

    http://<ip_address>:8000/wja/wja.application?lang=pt-pt

    Russian

    http://<ip_address>:8000/wja/wja.application?lang=ru-ru

    Spanish (Mid-Atlantic)

    http://<ip_address>:8000/wja/wja.application?lang=es-es

Configure the Port for Event Notifications

HP Web Jetadmin directs clients to a TCP connection to receive event notifications. After the client establishes the TCP connection, HP Web Jetadmin sends event notifications that prompt the client to update itself via the standard Microsoft .NET Remoting channel on port 4088.

The HP Web Jetadmin server communicates the port number that is established for event notifications to the client when the client first establishes a connection to the HP Web Jetadmin server. The port that HP Web Jetadmin uses to communicate with the client is somewhat random. A random port might cause a problem if a firewall is configured on the HP Web Jetadmin server.

If a firewall is configured on the HP Web Jetadmin server, you must configure a static port for event notifications and configure the firewall to accept connections through this port. If a firewall is configured on the client, you do not need to configure the firewall on the client to launch the client.

Use the following steps to configure a static port for event notifications:

  1. Open Notepad or a similar editor that has the appropriate create and edit permissions.

  2. Enter the following code:

                      <ipmc:configuration
    xmlns:ipmc="www.hp.com/schemas/imaging/ipmc/config/2004/02/24">
       <property name="ClientEventRouter.ServerPort">
          <type>HP.Imaging.Wjp.Sdk.Core.Framework.ConfigurationItemString
          </type>
          <value>8099</value>
       </property>
    </ipmc:configuration>
                    
    CAUTION:

    Make sure that the code is entered exactly as shown here. Observe all of the rules for XML editing. Use the quotes (") that the editor generates.

    Do not copy the code from this document, and then paste it into the editor. The characters copied into the editor, such as quotes ("), are not formatted correctly. Characters that are formatted incorrectly cause the HP Web Jetadmin XML parser to fail and the HPWJA service to fail during the startup process.

  3. Change the <value> attribute to any unused port.

  4. From the File menu, select Save. The Save As window opens.

  5. Navigate to the following directory on the HP Web Jetadmin server:

    C:\Windows\ServiceProfiles\NetworkService\AppData\Local\HP Inc\HPWebJetadmin\WjaService\config

  6. In the File name field, enter Global.config.xml.

  7. Click the Save button.

  8. Restart the HP Web Jetadmin service (HPWJAService).

    CAUTION:

    Be careful when you restart the HP Web Jetadmin service. Critical tasks might be running and clients might be logged in to HP Web Jetadmin. To view the tasks that are running, go to the Application Management > Overview > Application Management - Active Tasks task module. To view the clients that are logged in, go to the Application Management > Overview > Client Management - Active Clients task module.

  9. Use any firewall application or a similar application to open the port.

Configure the Firewall Software

You must configure the firewall on the HP Web Jetadmin server host to allow client traffic and other traffic to pass through the correct ports. The firewall monitors HP Web Jetadmin for the ports that it uses and allows traffic.

In some firewall applications, such as Microsoft Firewall, you can specify a program or executable file as a firewall exception. In these cases, you can define the following file as an exception:

C:\Program Files\HP Inc\Web Jetadmin 10\bin\HPWJAService.exe

The firewall on the client system does not require any special consideration because the client application does not listen to a specific port.