Skip this Video
Download Presentation
KEPServer moving from 4.0 to 5.0

Loading in 2 Seconds...

play fullscreen
1 / 27

KEPServer moving from 4.0 to 5.0 - PowerPoint PPT Presentation

  • Uploaded on

KEPServer moving from 4.0 to 5.0. KEPServer 5.0 is the next generation of Kepware communications technology. Newer, sleeker, and stronger it represents 12 years of knowledge and know how.

I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
Download Presentation

PowerPoint Slideshow about ' KEPServer moving from 4.0 to 5.0' - dom

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

KEPServer 5.0 is the next generation of Kepware communications technology. Newer, sleeker, and stronger it represents 12 years of knowledge and know how.

The Server has been re-designed from the ground up to take advantage of new technology and position it to move onto new automation platforms while leveraging legacy functionality.


Key Features

  • New Licensing
  • Separate Runtime and Configuration
  • Remote Configuration (Phase II)
  • User Management
  • Processor Affinity and Process Priority Settings
  • Host Resolution Management

Where are the my options?

One of the things that has been done in 5.0 is the ability for the server project to carry project specific settings with it. Additional options for the server are divided between Runtime and Configuration Options.


What has changed when installing and launching the server?

  • By default the runtime runs as a service. The customer will have to change this after the installation if they want to run on the desktop
  • By default stricter DCOM Security requirements are set. In 4.0 Use DCOM security was off by default which meant the server would basically ignore security warnings for local desktop connections.
  • Runtime is managed via the Administrator which runs in the toolbar.

What Has Changed? Cont….

  • There is a new default SimDemo project.
  • You can edit projects offline while another project is running.
  • Plug-ins like Advanced Tags, Data Logger, and OPC Connectivity Suite are now embedded in the server GUI rather than having stand alone GUI’s. This reduces issues with UAC if it is enabled.

Installation and Licensing?

Please stop the KEPServerEx V4 service and any client applications (both local and remote) that may be connected before proceeding, run _install\KEPServerEx5.exe.  This will install the necessary dependencies and launch the KEPServerEx V5 install.  After accepting the Licensing Agreement, you will be presented with the following question.  Please select “Side by Side”.  This will leave V4 installed while also installing V5.


After the install the V5 server should be running in service mode.  If not, go to Programs->Kepware->KEPServerEX5->KEPServerEX 5 –> Administration.

Preparing the V5 Server

Please locate the Administrator icon ( ) in the system tray and you’ll see the following menu

2. In the event Start Runtime Service is enabled (server not running), right-click and select “Start Runtime Service”.  This will launch the server runtime component.

3. Now right-click and select “Configuration”.  This will launch the Configuration console with a GUI very similar to our V4 product. 

4. If the server doesn’t automatically load the V4 project you can do so manually by going to File | Open in the Configuration console and select the project file used in KEPServerEx V4 (i.e. M11_Kep_GCBD.opf).  You should get the following popup:


5. Select Yes, Update

  • 6. Your project will now be loaded into the Runtime.
  • 7. We suggest doing a File | Save As and calling it something like M11_Kep_GCBD_V5.opf, this way you can always distinguish between the V4 and V5 project.
  • Now that the server is configured, the next step is to redirect your clients so that they point at the V5 server rather than the V4 server.
  • Redirecting Client ProgIds
  • All clients will need to be configured so that the Server ProgId is changed from Kepware.KEPServerEX.V4 to Kepware.KEPServerEX.V5.  This operation will be done differently based on the client (i.e. FactoryTalk, VB app).  Once redirected, please verify connectivity with the server with all clients.


Once connectivity has been verified, you will want to license your drivers, otherwise you’ll be running in a 2 hour demo mode.  

Right-click on the Administrator utility in the system tray and select License Utility.  The following screen will come up.


In the drop down box select “Manage Software Licenses”.  You will see the following screen below.


Select the “Manage software license activation between this PC and Kepware (default)”.  You will see the following screen below.


In the Activation ID edit box, enter one of the activation ids.  Make sure to note which one you used as it can’t be used again on the other PCs.

  • Now press the “Save to File” button.  A file called activation_request.txt will be saved to your hard drive.  By default it will be saved in My Documents.
  • We suggest renaming it to something like activation_request_OmronFINSEthernet_GMS_2.txt to reflect the driver and PC the activation will apply to. 
  • Go to your account and login to the activate license utility on the website. Enter the entitlement ID and upload the ctivation_request.txt file. You will then be provided with a response.txt file and save to your hard drive.
  • If you had shut down the License Utility since step 6, please re-launch it and follow the above steps until you get to the Manage Software License Activation screen (shown above).
  • From this screen, press the “Load From File” button under the Process Activation Response File group.
  • Navigate to the response.txt file.
  • The licensing process is now complete.  You should see a screen similar to this