SKF Install Manual

SKF @ptitude Analyst Download and
Installation
Documents the Download and Installation of @ptitude Software
and User Manuals
Supports Microlog Analyzer, Microlog Inspector, MARLIN, W V/T, WMx,
IMx and DMx
Part No. 32367100-EN

Revision A
Installation Manual
Copyright  2017 by SKF USA Inc.

All rights reserved.
Technical Support Email: tsg-americas@skf.com North and South America
Technical Support Email: tsg-emea@skf.com
SKF USA Inc.
® SKF is a registered trademark of the SKF Group.
All other trademarks are the property of their respective owners.
© SKF 2017
The contents of this publication are the copyright of the publisher and may not be reproduced (even
extracts) unless prior written permission is granted. Every care has been taken to ensure the accuracy of
the information contained in this publication but no liability can be accepted for any loss or damage whether
direct, indirect or consequential arising out of the use of the information contained herein. SKF reserves the
right to alter any part of this publication without prior notice.
Patents: US 4,768,380 • US 5,633,811 • US 5,679,900 • US 5,845,230 • US 5,852,351 •

US 5,854,553 • US 5,854,994 • US 5,870,699 • US 5,907,491 • US 5,992,237 • US 6,006,164 •
US 6,124,692 • US 6,138,078 • US 6,199,422 • US 6,202,491 • US 6,275,781 • US 6,301,514 •
US 6,437,692 • US 6,489,884 • US 6,513,386 • US 6,633,822 • US 6,789,025 • US 6,792,360 •
US 7,103,511 • US 7,697,492 • WO/2003/048714
Product Support – Contact Information
Product Support – To request a Return Authorization, Product Calibration or a Product Support Plan, use
the web page links for direct contact and support.
Product Sales - For information on purchasing condition monitoring products, services or customer
support, contact your local SKF sales office.
General Product Information
For general product information (i.e., product data sheet, accessories catalog, etc.), visit the Condition
Monitoring Products page on SKF.com and select the appropriate product link.
Technical Support Group
Discuss/review issues of specific interest with maintenance and reliability specialists from around the world
at the SKF Knowledge Centre.
For technical support on issues like troubleshooting product installation, troubleshooting product
performance, etc., use our technical support web page to contact one of our Technical Support Groups.
Product Registration
Please take a moment to register your product at www.skf.com/cm/register to receive exclusive benefits
offered only to our registered customers, including receiving technical support, tracking your proof of
ownership, and staying informed about upgrades and special offers. (Please visit our website for more
details on these benefits.)
Tell us how we’re doing!
It’s important that you’re satisfied with the quality of our product user manuals. We appreciate your
feedback; if you have comments or suggestions for improvement, please tell us how we’re doing!
031017dc
End-User License Agreement (d) Person. The term “Person” shall
mean an individual, a partnership, a
THIS END-USER LICENSE AGREEMENT (this company, a corporation, an
“Agreement”) is entered into by and between association, a joint stock company, a
SKF USA Inc. and/or SKF Condition Monitoring trust, a joint venture, an
Center AB (hereinafter referred to collectively as unincorporated organization, or a
the “Licensor”) and any person or business that governmental entity (or any
executes this Agreement by clicking the “I agree” department, agency, or political
icon at the end of this Agreement or by subdivision thereof).
accessing, using, or installing the Software
(“Licensee” or “You”). Licensor and Licensee (e) Software. The term “Software” shall
shall be referred to collectively in this mean the software application entitled
Agreement as the Parties. Software for Wireless Monitoring
System V/T, SKF @ptitude Analyst,
BY CLICKING THE ACCEPTANCE BUTTON OR SKF @ptitude Inspector, SKF @ptitude
ACCESSING, USING, OR INSTALLING THE Observer, SKF @ptitude Decision
SOFTWARE, OR ANY PART THEREOF, YOU Support or any other software within
EXPRESSLY AGREE TO BE BOUND BY ALL OF the SKF @ptitude family suite, which
THE TERMS OF THIS AGREEMENT. IF YOU is an application developed, owned,
DO NOT AGREE TO ALL OF THE TERMS OF marketed, and licensed by Licensor.
THIS AGREEMENT, THE BUTTON INDICATING The term Software shall include the
NON-ACCEPTANCE MUST BE SELECTED, object code of Software for Wireless
AND YOU MAY NOT ACCESS, USE, OR Monitoring System V/T, SKF @ptitude
INSTALL ANY PART OF THE SOFTWARE. Analyst, SKF @ptitude Inspector, SKF
@ptitude Observer, SKF @ptitude
1. DEFINITIONS Decision Support or any other object
code within the SKF @ptitude family
(a) Derivative Works. The Term suite and any and all user manuals, or
“Derivative Works” shall have the other technical documentation,
same meaning as set forth in the U.S. authored by Licensor in connection
Copyright Act, as amended from time with Software for Wireless Monitoring
to time, in title 17 of the United States System V/T, SKF @ptitude Analyst,
Code. SKF @ptitude Inspector, SKF @ptitude
Observer, SKF @ptitude Decision
(b) Effective Date. The term “Effective Support or any other software within
Date” shall mean the date on which the SKF @ptitude family. The term
Licensee assents to the terms of this “Software” includes any corrections,
Agreement by clicking the “I agree” bug fixes, enhancements, releases,
button at the bottom of this updates, upgrades, or other
Agreement. modifications, including custom
modifications, to Software for
(c) Intellectual Property Rights. The Wireless Monitoring System V/T, SKF
term Intellectual Property Rights shall @ptitude Analyst, SKF @ptitude
mean all rights arising or protectable Inspector, SKF @ptitude Observer,
under the copyright, trademark, SKF @ptitude Decision Support or any
patent, or trade secrets laws of the other software within the SKF
United States or any other nation, @ptitude family suite and any and all
including all rights associated with the user manuals. The term Software
protection of computer programs also includes any supplemental, add-
and/or source code. on, or plug-in software code provided
to Licensee in the course of receiving Software on as many
Product Support Plan services from networked clients
Licensor. The term Software shall not (workstations) as authorized
be construed to include the source by your network license, as set
code for Software for Wireless forth more particularly in the
Monitoring System V/T, SKF @ptitude applicable purchase order or
Analyst, SKF @ptitude Inspector, SKF other ordering documents
@ptitude Observer, SKF @ptitude memorializing your license
Decision Support or any other acquisition; provided, however,
software within the SKF @ptitude that all network clients
family suite. (workstations) are connected
to a single licensed database
2. LICENSE residing in your principal
business office.
(a) Grant of License. Licensor grants
Licensee, pursuant to the terms and (iii) If you obtained a network
conditions of this Agreement, a non- license of the Software, you
exclusive, non-transferable, and may connect to multiple
revocable license to use the Software licensed databases, you may
in strict accordance with the terms install the database-dedicated
and conditions of this Agreement, clients up to the total number
including any concurrent use, network of networked clients acquired
or other limitations set forth in by you under the applicable
subsection (b) below. All rights not purchase order or other
specifically granted by Licensor under ordering documents
this Agreement are retained by memorializing your license
Licensor and withheld from Licensee. acquisition.
(b) Installation and Use Rights. (c) Other Conditions of Use. Licensor
Licensee shall use the Software only understands and agrees that the
on its internal computer equipment, Software works in conjunction and is
whether such equipment is owned, compatible with database software
leased, or rented, at the Licensee’s licensed to you by Microsoft or
principal business office. The Oracle. Upon installation of the
following paragraphs govern your Software, the Software may detect
installation and use rights with regard an installed database software
to the Software, depending on the application from Oracle or Microsoft,
type of license you have obtained from and if so, the Software will be fully
Licensor. installed. If no installed database
software application from Oracle or
(i) If you obtained a stand-alone Microsoft is detected, the Software
license of the Software, you will not install until such time as
may install one (1) copy of the Licensee installs a valid and Software
Software on one (1) computer compatible copy of an Oracle
residing in your principal database or a Microsoft SQL Server
business office. database and consents to the license
terms of such database software
(ii) If you obtained a network application. If Licensee does not
license of the Software, you agree to the terms of the the Oracle
may install one (1) copy of the database license or the Microsoft
SQL Server license, or if the Licensee (vii) make the Software accessible
fails to install such database to any Person by any means,
software, the Software will not work. including posting on a web site
Licensee is responsible for or through other distribution
maintaining a valid database license mechanisms over the Internet;
in accordance with the Oracle or
Microsoft license agreement (which (viii) reverse assemble,
ever is applicable) at all times. disassemble, reverse engineer,
reverse compile, decompile, or
(d) Restrictions on Use. Licensee may otherwise translate the
use the Software only for its internal Software or prepare
business purposes and on the Derivative Works based on the
identified equipment on which the Software;
Software was first installed or for
which it is otherwise licensed; (ix) place, reproduce, or make
provided, however, that Licensee available the Software on
may temporarily use the Software on Licensee’s computer network
a back-up system in the event that if Licensee is only authorized
the primary licensed system is by this Agreement to operate
inoperative or test system not used the Software on a single
for production but solely for the workstation;
purposes of testing the Software.
Licensee may not use the Software (x) exceed at any given point in
for any other purpose. Licensee shall time the total number of
not: network clients authorized by
the applicable purchase order
(i) permit any parent, or ordering document to use
subsidiaries, affiliated entities or access the Software;
or third parties to use the
Software; (xi) edit or modify the Software
except as expressly authorized
(ii) use the Software in the by Licensor, including altering,
operation of a service bureau; deleting, or obscuring any
proprietary rights notices
(iii) allow access to the Software embedded in or affixed to the
through any workstations Software;
located outside of Licensee’s
principal business offices; (xii) use the Software in any
manner that disparages
(iv) rent, resell, lease, timeshare Licensor, Microsoft, or Oracle,
or lend the Software to any or use the Software in a way
Person; that infringes the Intellectual
Property Rights of the
(v) sublicense, assign, or transfer foregoing parties; or
the Software or this license for
the Software to any Person; (xiii) use the Software in a manner
that violates any federal, state,
(vi) reproduce, distribute, or or local law, rule or regulation,
publicly display the Software; or use the Software to violate
the rights of any third party, or
use the Software to promote valuable copyright and contains
pornography, hatred, or valuable trade secrets of Licensor.
racism. Licensee agrees not to discover or
attempt to discover, or assist or
(e) Copies. Licensee, solely to enable it permit any Person to discover or
to use the Software, may make one attempt to discover, by any means
archival copy of the Software’s whatsoever the source code of the
computer program, provided that the Software.
copy shall include Licensor’s copyright
and any other proprietary notices. (h) Licensor’s Audit Rights. Licensor
The Software delivered by Licensor to shall possess the right to audit
Licensee and the archival copy shall Licensee’s use of the Software to
be stored at Licensee’s principal determine compliance with this
business office. If you purchased a Agreement (hereinafter referred to as
network license of the Software, you “Licensor’s Audit Rights”). Licensor’s
may install one additional copy of the Audit Rights shall be exercised in
Software on your network for the accordance with the following
limited purpose of testing the paragraphs:
Software’s operation. Except for the
limited reproduction rights set forth in (i) Notice of Audit. Licensor
this paragraph, Licensee shall have no shall provide Licensee with at
other right to copy, in whole or in part, least five (5) calendar days
the Software. Any copy of the advance written notice of its
Software made by Licensee is the intent to exercise the
exclusive property of Licensor. Licensor’s Audit Rights.
(f) Modifications. Licensee agrees that (ii) Conduct of Audit. The audit
only Licensor shall have the right to conducted by Licensor shall
alter, maintain, enhance or otherwise consist of a physical review of
modify the Software. the computer hardware,
software, and middleware
(g) Protection of Software. Licensee operated by Licensee at its
agrees that it will take action by principal business office and
instruction, written agreement, or any other office for which
otherwise as appropriate with any Licensor, in its sole and
person permitted access to the arbitrary discretion, deems an
Software to enable Licensee to comply audit appropriate. Licensee
with its obligations hereunder. shall provide Licensor with
Licensee shall maintain records of the unrestricted access to its
number and location of all copies of computer hardware, software,
Software. Licensee shall not provide, and middleware in connection
permit access to or use of, or with any audit conducted by
otherwise make available any Licensor.
Software in any form without
Licensor’s prior written agreement, (iii) Costs of Audit. If Licensor’s
except to Licensee’s employees for audit uncovers a violation of
purposes specifically authorized by this Agreement by Licensee,
this Agreement. Licensee Licensee shall pay all costs
understands and agrees that the and expenses incurred by
source code for the Software is a Licensor in exercising the
Licensor Audit Rights, terminate this Agreement and the
including, without limitation, license granted hereunder
all attorneys’ fees and agent immediately and without an
fees incurred by Licensor. If opportunity to cure. This subsection
Licensor concludes that no 2(j) shall not be construed to preclude,
violation of this License or in any way effect, a finding of
Agreement has occurred, materiality with respect to any other
Licensor shall bear all costs provision of this Agreement.
and expenses incurred in
exercising the Licensor Audit 3. LICENSE FEE
Rights. If Licensee obstructs, The applicable licensee fees will be set forth
restricts, or otherwise in the quote issued to Licensee by Licensor
prevents Licensor from or otherwise established in the applicable
conducting a full and purchase order or other ordering
unrestricted audit, Licensee documents memorializing your license
shall bear all costs and acquisition.
expenses, including attorneys’
fees, incurred by Licensor in 4. OWNERSHIP
enforcing this Section 2(h)
before any court or judicial (a) Title. Licensee understands and
tribunal. agrees that Licensor owns all
Intellectual Property Rights related to
(iv) Frequency of Audits. the Software, including custom
Licensor’s Audit Rights shall be modifications to the Software,
exercised no more than two whether made by Licensor or any
(2) times in any one calendar third party. Licensee agrees that this
year. Agreement effects a license, not a
sale, of the Software and that the first
(i) Validity of Intellectual Property sale doctrine, as codified in 17 U.S.C.
Rights. In any action, dispute, § 109, does not apply to the
controversy, or lawsuit arising out of transaction effected by this
or related to this Agreement, Licensee Agreement.
shall not contest the validity of
Licensor’s Intellectual Property Rights (b) Transfers. Under no circumstances
related to the Software. Licensee shall Licensee sell, license, sublicense,
hereby agrees that it has had an publish, display, distribute, assign, or
opportunity to investigate the validity otherwise transfer (hereinafter
of Licensor’s Intellectual Property referred to collectively as a “Transfer”)
Rights, and acknowledges that to a third party the Software or any
Licensor’s Intellectual Property Rights copy thereof, in whole or in part,
related to the Software are valid and without Licensor’s prior written
enforceable. consent. Any Transfer effected in
violation of this Section 4(b) shall be
(j) Material Terms and Conditions. void ab initio and of no force or effect.
Licensee specifically agrees that each
of the terms and conditions of this 5. MAINTENANCE AND SUPPORT
Section 2 are material and that failure Licensor may provide you with support
of Licensee to comply with these services related to the Software called
terms and conditions shall constitute Product Support Plan (“PSP”) services. Use
sufficient cause for Licensor to of PSP is governed by the policies and
programs described in the PSP literature or Licensor aware of any defect with the
other material from Licensor’s Product Software within seven (7) days after
Support Department (hereinafter referred the occurrence of the defect; (ii)
to as the “PSP Policies”) that may be Licensee has paid all amounts due
updated by Licensor from time to time. If under this Agreement; and (iii)
you select and pay for PSP, the PSP Licensee has not breached any
Policies shall be specifically incorporated provision of this Agreement. The
into this Agreement by this reference. foregoing warranty does not apply in
Licensee acknowledges that Licensor may the event that: (i) the Software and
use any technical information provided by documentation have been subject to
Licensee in the course of receiving PSP misuse, neglect, alteration,
services for Licensor’s business purposes, modification, customization, improper
including for product support and installation, and/or unauthorized
development. Licensor will not utilize such repair; (ii) the Software or any
technical information in a manner that associated software or equipment
identifies Licensee. have not been properly maintained in
accordance with applicable
6. CONFIDENTIAL INFORMATION specifications and industry standards
Licensee agrees that the Software contains or have been maintained in unsuitable
proprietary information, including trade environmental conditions; or (iii)
secrets, know-how and confidential Licensee has used the Software in
information (hereinafter referred to conjunction with other equipment,
collectively as the “Confidential hardware, software, or other
Information”), that is the exclusive property technology that created an adverse
of Licensor. During the period this impact on the operation, functioning,
Agreement is in effect and at all times after or performance of the Software.
its termination, Licensee and its employees
and agents shall maintain the confidentiality (b) EXCEPT AS SET FORTH IN THIS
of the Confidential Information and shall not SECTION 7 AND TO THE EXTENT
sell, license, publish, display, distribute, PERMITTED BY APPLICABLE LAW,
disclose or otherwise make available the ALL EXPRESS AND/OR IMPLIED
Confidential Information to any Person nor WARRANTIES OR CONDITIONS,
use the Confidential Information except as INCLUDING BUT NOT LIMITED TO
authorized by this Agreement. Licensee IMPLIED WARRANTIES OR
shall not disclose the Confidential CONDITIONS OF MERCHANTABILITY,
Information concerning the Software, MERCHANTABILITY OF A COMPUTER
including any flow charts, logic diagrams, PROGRAM, INFORMATIONAL
user manuals and screens, to persons not CONTENT, SYSTEM INTEGRATION,
an employee of Licensee without the prior FITNESS FOR A PARTICULAR
written consent of Licensor. PURPOSE, AND NON-
INFRINGEMENT, ARE HEREBY
7. LIMITED WARRANTIES DISCLAIMED AND EXCLUDED BY
LICENSOR.
(a) Licensor warrants that the Software
will perform substantially in (c) The remedies set forth in this Section
accordance with its documentation for 7 are the exclusive remedies available
a period of 180 days from the date of to Licensee for any problem in the
shipment of the Software; provided, performance of the Software.
however, that the foregoing warranty
only applies if: (i) Licensee makes
8. LIMITATIONS ON LIABILITY 9. TERM AND TERMINATION
(a) Limitations and Exclusions. IN NO (a) Term. This Agreement shall

EVENT WILL LICENSOR BE LIABLE commence on the Effective Date and
TO LICENSEE FOR ANY DIRECT, shall continue in existence until it is
INDIRECT, INCIDENTAL, terminated in accordance with Section
CONSEQUENTIAL, PUNITIVE OR 9(b) below.
OTHER SPECIAL DAMAGES, LOST
PROFITS, OR LOSS OF INFORMATION (b) Termination. Licensor may
SUFFERED BY LICENSEE ARISING terminate this Agreement and the
OUT OF OR RELATED TO THIS license conveyed hereunder in the
AGREEMENT OR THE USE OF THE event that Licensee breaches any
SOFTWARE, FOR ALL CAUSES OF provision, term, condition, or
ACTION OF ANY KIND (INCLUDING limitation set forth in this Agreement,
TORT, CONTRACT, NEGLIGENCE, including but not limited to the license
STRICT LIABILITY, BREACH OF restrictions set forth in Section 2(d) of
WARRANTY OR CONDITION, AND this Agreement.
STATUTORY) EVEN IF LICENSOR HAS
BEEN ADVISED OF THE POSSIBILITY (c) Effect of Termination. Within ten
OF SUCH DAMAGES. THE (10) days after termination of this
PRECEDING EXCLUSION AND Agreement and the license granted
DISCLAIMER OF DAMAGES SHALL hereunder, Licensee shall return to
APPLY TO ALL CLAIMS MADE BY Licensor, at Licensee’s expense, the
LICENSEE RELATED TO OR ARISING Software and all copies thereof, and
OUT OF LICENSEE’s USE OF THE deliver to Licensor a certification, in
SOFTWARE, INCLUDING, BUT NOT writing signed by an officer of
LIMITED TO, CLAIMS ALLEGING THAT Licensee, that all copies of the
THE SOFTWARE, OR ANY Software have been returned to
COMPONENT THEREOF, FAILED OF Licensor and that Licensee has
ITS ESSENTIAL PURPOSE OR FAILED discontinued its use of the Software.
IN SOME OTHER RESPECT.
10. ASSIGNMENT
(b) Acknowledgment. Licensee agrees Licensee shall not assign or otherwise
that the limitations of liability and transfer the Software or this Agreement to
disclaimers of warranty set forth in anyone, including any parent, subsidiaries,
this Agreement will apply regardless affiliated entities or third Parties, or as
of whether Licensor has tendered part of the sale of any portion of its
delivery of the Software or Licensee business, or pursuant to any merger,
has accepted the Software. Licensee consolidation or reorganization, without
acknowledges that Licensor has set its Licensor’s prior written consent. Any
prices and entered into this assignment or transfer effected in violation
Agreement in reliance on the of this Section 10 shall be void ab initio
disclaimers of warranty and the and of no force or effect.
limitations and exclusions of liability
set forth in this Agreement and that 11. FORCE MAJEURE
the same form an essential basis of Neither party shall be in default or
the bargain between the Parties. otherwise liable for any delay in or failure
of its performance under this Agreement if
such delay or failure arises by any reason
beyond its reasonable control, including
any act of God, any acts of the common such Party’s respective address shall be
enemy, the elements, earthquakes, floods, effective service of process for any Legal
fires, epidemics, riots, failures or delay in Proceeding. Licensor and Licensee
transportation or communications; irrevocably and unconditionally waive any
provided, however, that lack of funds shall objection to personal jurisdiction and/or
not be deemed to be a reason beyond a the laying of venue of any Legal
party’s reasonable control. The Parties Proceeding in the state or federal court in
will promptly inform and consult with each or for Philadelphia, Pennsylvania, and
other as to any of the above causes that in hereby further irrevocably and
their judgment may or could be the cause unconditionally agree not to plead, argue,
of a delay in the performance of this or claim in any such court that any Legal
Agreement. Proceeding brought in any such court has
been brought in an inconvenient forum
12. NOTICES and otherwise waive any and all objections
All notices under this Agreement are to be to the forum.
delivered by depositing the notice in the
mail, using registered mail, return receipt 15. EXPORT CONTROLS
requested, to the party’s last known Licensee shall not export or reexport,
principal business address or to any other directly or indirectly, the Software without
address as the party may designate by complying with the export controls
providing notice. The notice shall be imposed by the United States Export
deemed delivered four (4) days after the Administration Act of 1979, as amended
notice’s deposit in the mail, if such notice (or any future U.S. export control
has been sent by registered mail. legislation) and the regulations
promulgated thereunder.
13. CHOICE OF LAW
This Agreement (including all Exhibits), 16. GOVERNMENT END USERS
including its formation, execution, If Licensee is acquiring the Software for or
interpretation, and performance, and the on behalf of a subdivision of the U.S.
rights and obligations of the Parties federal government, this Section 16 shall
hereunder, shall be governed by and apply. The Software was developed
construed in accordance with the laws of completely at private expense, is existing
the Commonwealth of Pennsylvania, computer software, is a trade secret for all
without regard to any conflicts of law (or purposes of the Freedom of Information
choice of law) principles thereof. Act, is “restricted computer software” and
in all respects proprietary data belonging
14. CONSENT TO JURISDICTION solely to Licensor, and all rights are
In the event that either party initiates reserved under the copyright laws of the
litigation relating to or arising out of this United States. Use, duplication, or
Agreement, Licensor and Licensee disclosure by the Government is subject to
irrevocably submit to the exclusive restricted rights as set forth in
jurisdiction of the state or federal court in subparagraphs (a) through (d) of the
or for Philadelphia, Pennsylvania for the Commercial Computer Software Restricted
purposes of any suit, action or other Rights clause at FAR 52.227-19, or for
proceeding relating to arising out of this DoD units, the restrictions as set forth in
Agreement or any transaction subparagraph (c)(1)(ii) of the Rights in
contemplated hereby or thereby (“Legal Technical Data and Computer Software
Proceedings”). Licensee further agree that clause at DFARS 252.227-7013.
service of any process, summons, notice,
or document by U.S. registered mail to
17. TRADEMARKS (c) Waiver. The waiver or failure of
Licensee agrees that SKF @ptitude either party to exercise in any
Analyst, SKF @ptitude Inspector, SKF respect any right provided for in this
@ptitude Observer, SKF @ptitude Decision Agreement shall not be deemed a
Support or any other software within the waiver of any further right under this
SKF @ptitude family suite and the trade Agreement.
dress, logos and other designations of
source used by Licensor to identify the (d) Severability. If any provision of this
Software are trademarks or registered Agreement is invalid, illegal or
trademarks of Licensor. Licensee shall not unenforceable under any applicable
use Licensor’s trademarks or service statute or rule of law, it is to that
marks without the prior written consent of extent to be deemed omitted. The
Licensor. If the Software contains any remainder of the Agreement shall be
active links to web sites, you agree to valid and enforceable to the
maintain such active links and not redirect maximum extent possible.
or modify them.
(e) Read and Understood. Each party
18. GENERAL PROVISIONS acknowledges that it has read and
understands this Agreement and
(a) Complete Agreement. The Parties agrees to be bound by its terms.
agree that this Agreement is the
complete and exclusive statement of (f) Limitations Period. No action
the agreement between the Parties, arising under, or related to, this
which supersedes and merges all Agreement, may be brought by
prior proposals, understandings and either party against the other more
all other agreements, oral or written, than two (2) years after the cause of
between the Parties relating to the action accrues, unless the cause of
use of the Software. action involves death or personal
injury.
(b) Amendment. This Agreement may
not be modified, altered or amended (g) Attorneys’ Fees. In the event any
except by written instrument duly litigation is brought by either party in
executed by both Parties. Any connection with this Agreement, the
purchase orders or other ordering prevailing party in such litigation will
documents issued to Licensee by be entitled to recover from the other
Licensor shall not have the effect of party all the costs, reasonable
amending or modifying this attorneys’ fees, and other expenses
Agreement, and shall only serve to incurred by such prevailing party in
memorialize the number of licenses the litigation.
or products ordered by Licensee. In
the event of a conflict between the (h) Authorized Representative. The
PSP Policies and this Agreement, the person installing or using the
terms of this Agreement shall Software on behalf of Licensee
control. represents and warrants that he or
she is legally authorized to bind
Licensee and commit Licensee to the
terms of this Agreement.
(i) Injunctive Relief. Licensee agrees
that Licensor may suffer irreparable
harm as a result of a violation of
Sections 2, 4, 6, 10, 15, and 17 of
this Agreement and that monetary
damages in such event would be
substantial and inadequate to
compensate Licensor. Consequently,
Licensor shall be entitled to seek and
obtain, in addition to such other
monetary relief as may be
recoverable at law or in equity, such
injunctive other equitable relief as
may be necessary to restrain any
threatened, continuing, or further
breach by Licensee without showing
or proving actual damages sustained
by Licensor and without posting a
bond.
CM-F0176 (Revision F, January 2011)

Table of Contents
Installation 1
Important - How to Facilitate a Quick, Easy
Product Installation! ............................................... 1-1
Hardware Requirements .......................................... 1-3
Technical Support ...................................................... 1-6
Planning the Installation ........................................... 1-6
Upgrading an Existing Version of the Software .. 1-12
The Download and Installation Process ............... 1-16
Download and Install Prerequisite Applications . 1-16
Download and Install the Database Manager
Application.............................................................. 1-17
Download and Install the SKF @ptitude Analyst
Applications ............................................................ 1-20
User Manuals ............................................................ 1-26
Setting Up License Keys .......................................... 1-26
What’s the Next Step?............................................. 1-26
SKF @ptitude Analyst Configuration Tool 2

Database Configuration Options .............................. 2-1
Database Type ............................................................ 2-4
Change Database ..................................................... 2-10
Update Database ...................................................... 2-12
Run SQL Script ......................................................... 2-13
SKF @ptitude Analyst Configuration Tool ........... 2-14
General Configuration ............................................. 2-14
SKF @ptitude HMI Connection .............................. 2-15
SKF @ptitude Transaction Service ....................... 2-16
SKF @ptitude Monitor Recovery ........................... 2-21
SKF @ptitude Thin Client Transfer ....................... 2-22
SKF @ptitude Analyst License Key Manager....... 2-23
SKF @ptitude IMx Service ...................................... 2-24
SKF @ptitude Microlog Service ............................. 2-30
SKF @ptitude WMx Service .................................... 2-35
SMTP Settings .......................................................... 2-38
SKF @ptitude Analyst TOC - 1

Installation Manual
Installing SKF @ptitude Analyst Thin Client
Transfer 3
A Note About Thin Client Transfer Licenses ......... 3-1
Installing Thin Client Transfer ................................. 3-2
Installation Maintenance 4
Removing your Installation....................................... 4-2
SKF @ptitude Analyst License Key Manager 5

Overview ...................................................................... 5-1
SKF @ptitude Analyst System Connection

Diagram A
Index
TOC - 2 SKF @ptitude Analyst

Installation Manual
1
Installation
Important - How to Facilitate a Quick, Easy Product Installation!
The information in this section is provided to point you in the right direction to help
guarantee the easiest possible installation.
Varying Procedures for First Time Installations, Application

Upgrades, and Product Maintenance Releases
Note that there are various types of software installations; for example, first time
installations vs. product upgrades vs. product maintenance releases. The SKF @ptitude
Analyst Installation and Upgrade Matrix below overviews specific installation steps you
will take depending on your situation. Review this matrix and proceed as described for
your type of installation.
 With SKF @ptitude Analyst 9, it is no longer necessary to remove
(uninstall) an existing previous version of the application to install
an upgrade or a maintenance release.
Application Maintenance
Upgrade Release
SKF @ptitude Analyst Installation and First Time
(e.g., from (installed from
Upgrade Matrix Installation
version 7 to downloaded
version 8) file)
Run Prerequisites (described in Chapter 1,
Installation / Installing Prerequisite X X
Applications)
Install Database Manager (described in
Chapter 1, Installation / Database X
Installation)
Install Application (described in Chapter 1, X - run the
Installation / Installing the SKF @ptitude X X downloaded
Analyst Applications) file
From the Configuration Tool – Acquire the
Demo database, specify the database type,
and connect the database to @ptitude
Analyst (described in Chapter 2, SKF X
@ptitude Analyst Configuration Tool /
Database Configuration Options /
Database Type)
From the Configuration Tool, Update
Database (described in Chapter 2, SKF
@ptitude Analyst Configuration Tool / X X X
Database Configuration Options / Update
DB)
SKF @ptitude Analyst 1-1

Installation Manual
Installation
Important - How to Facilitate a Quick, Easy Product Installation!
A Note about the Download Installation Image

This download and installation manual documents the installation procedure for the
SKF @ptitude Analyst downloadable installer, which installs SKF’s SKF @ptitude Analyst
software that supports SKF’s Microlog Analyzer, Microlog Inspector, MARLIN, IMx, TMU,
CMU, LMU, MIM, WMx, IMx, and DMx data acquisition devices. After the installation,
please use the license keys provided to you to activate portions of the application
specific to your purchase.
In addition to SKF @ptitude Analyst, end users may obtain license keys for one or more
add-on applications, which extend the features of SKF @ptitude Analyst. The following
add-on applications are automatically installed during the SKF @ptitude Analyst
installation procedure and activated based on license keys:
 HMI (SKF @ptitude Analyst Human Machine Interface)
 Trend Oil
 Work Notifications
 IT Security
 NT Authentication
Additional applications are available as separate installs that can be run once the SKF
@ptitude Analyst installation procedure is complete. These include:
 SKF @ptitude Decision Support
 SKF @ptitude Analyst Thin Client Transfer
The SKF @ptitude Analyst software download website provides links that install Thin
Client Transfer and @ptitude Decision Support.
Refer to What to Install First, later in this section, for help with the installation order.
A Note about License Keys

License keys will be provided by SKF customer service for the specific product(s) you
have purchased. License keys are used to enable the product(s). Make sure you have
them on hand before starting the installation so that you are prepared to complete the
installation.
What to Install First

Use the following check list when installing SKF @ptitude Analyst and any add-on
applications:
 Ensure you have your license keys available.
 Review the Planning the Installation section of this manual for important pre-
installation instructions and guidelines. During this step you will be requested to
install important prerequisite programs and a supported database manager. You
will need to restart your computer before continuing with the installation.
 Install SKF @ptitude Analyst.
 Refer to the What’s the Next Step section following SKF @ptitude Analyst
installation to determine how you should proceed.
1-2 SKF @ptitude Analyst

Installation Manual
Installation
Hardware Requirements
 Please take a moment to register your product at www.skf.com/cm/register to

receive exclusive benefits offered only to our registered customers, including
receiving technical support, tracking your proof of ownership, and staying informed
about upgrades and special offers. (Please visit our website for more details on
these benefits.)
 Print and read the appropriate SKF @ptitude Analyst User Manuals for instructions
on getting started.
For maximum SKF @ptitude Analyst performance, refer to the hardware configuration
requirements detailed below. The numbered Notes are provided after the configuration
tables.
Stand alone configuration
 Running SKF @ptitude Analyst / SKF @ptitude Inspector
 Running Oracle or Microsoft SQL Server database management system
 Storing data
Configuration Minimum requirements Recommended requirements
Operating System (Note 1) Windows 7 Windows 7,

Windows 8.1 Enterprise or Pro,
Windows 10 Enterprise or Pro
Processor (Note 2) Intel 2.0 GHz, 32 or 64-bit, Intel Quad-Core processor 64-
or better bit
RAM 6 GB 8 GB or more
Disk space available for 10 GB 30 GB or more

standalone computer (Note
3)
Database Oracle Version 11g Version 12c

support
Microsoft SQL Server 2008 R2 SP1 SQL Server 2014 SP1 (SQL
(Note 5)
SQL Server Server recommends NTFS file
format)
USB port for SKF Microlog / SKF Microlog Inspector transfer and serial port for SKF
Multilog IMx configuration.

Installation Manual
Installation
Network configuration – Database server

 Running Oracle or Microsoft SQL Server database management system
 Storing data
Network configuration for up to 35 Clients and one database. Installations of 50 Clients or
greater will require an on-site assessment by our Field Service Engineers.
Operating System (Note 1) Windows Server 2008 Windows Server 2008

Windows Server 2012 R2
Processor (Note 2) Intel 2.0 GHz, 32 or 64-bit, Intel Quad-Core I7 processor

or better 64-bit
Quantity of hard drives 3 5

(Note 4)
Disk space available (Note 10 GB 30 GB or more

3)

support
(Note 5)
format)
Network configuration – Network Client

 Running database client software

Operating System (Note 1) Windows 7 Windows 7,
Processor (Note 2) Intel 2.0 GHz, 32 or 64-bit, Intel Quad-Core processor 64-bit
or better
Disk space available for 10 GB 30 GB or more

each network client

support (Note
5)
format)
USB port for SKF Microlog / SKF Microlog Inspector transfer and serial port for SKF
Multilog IMx configuration.

Installation Manual
Installation
Network configuration – Application server


Operating System (Note 1) Windows 7 OR Windows 7,
Windows Server 2008
OR
Windows Server 2008,
Windows Server 2012 R2
Processor Intel 2.0 GHz, 32 or 64-bit, Intel Quad-Core I7 processor

or better 64-bit
Disk space available 10 GB 30 GB or more
Note 1: Windows 7 (32 or 64-bit) Professional or Ultimate Editions, (please see

Windows Operating System Compatibility for the Windows 7 and UAC compatibility
matrix in this Installation Manual), Microsoft.NET Framework 3.5, 4.0, Windows 4.5
Installer and Windows Mobile Device Center 6.1.
Note 2: These requirements apply to SKF @ptitude Analyst complete with database
management system. Other applications running simultaneously may degrade
performance. Hyper-threading should be disabled in some systems.
Note 3: These requirements ONLY apply to SKF @ptitude Analyst complete with
database management system. Additional storage disk space is required for data.
Note 4: The major benefits of spreading Oracle across three or more hard disks at the
server is the improved speed, and improved recoverability of a previously archived
database. The recommended five disk configuration provides the optimal protection for
backup, recovery, indexing, and speed. Disk / file configuration should ONLY be handled
by a SKF Field Service Technician certified on SKF @ptitude Analyst. If using RAID, the
combination of RAID 0 and RAID 1 is recommended over RAID 5.
Note 5: In a Network Client configuration you must install Oracle 32-bit Client
Software. If using Windows 7 (32 or 64-bit), then Oracle 11g must be installed.
Note 6: Running SKF Multilog On-line System devices to monitor transient events
requires full database support. Express versions will not support performance
requirements for the system.
Notice: If running other system configurations, please contact your local SKF
Representative to inquire about compatibility.

Installation Manual
Installation
Technical Support
Technical Support
If you have questions regarding the installation or operation of SKF @ptitude Analyst,
please visit the self-help portal before contacting the help desk to see if the answer is
already published:
Technical Support Self-help Portal: www.skf.com/cm/tsg
If further assistance is needed, please submit a support request by clicking on the
SUPPORT tab and one of our support engineers will contact you shortly.
The technical support team can be reached during normal business hours (7:00 a.m. to
4:00 p.m. local time) by phone, e-mail, or live chat:
 Customers in Europe, Middle East and Africa:
Phone: +46 31 337 6500
E-Mail: TSG-EMEA@skf.com
Chat: www.skf.com/cm/tsg
 Customers in all other locations:
Phone: 1-858-496-3627 or toll-free (USA) 1-800-523-7514
E-Mail: TSG-Americas@skf.com
Chat: www.skf.com/cm/tsg
Note: Standard technical support will be provided at no cost on products or software
covered under an SKF Product Support Plan (PSP), whenever applicable. Many SKF
Machine Health products include limited technical support for the first 180 days after
purchase. Support obtained after 180 days or without PSP coverage will be Support
obtained after 180 days or without PSP coverage will be subject to a per-incident fee.
Contact the technical support team for more information.
Planning the Installation
Prior to installing SKF @ptitude Analyst, take a moment to complete the necessary
installation requirements. The following programs must be installed before you can run
the SKF @ptitude Analyst installation:
Windows Installer
.Net Framework (V3.5 and V4.0)
Refer to Download and Install Prerequisite Applications later in this manual.
Database Consideration
Prior to installing SKF @ptitude Analyst, you must install a supported database. The
application supports:
 Oracle database version 12c, Standard or Express Edition
 Oracle database version 11g, Standard or Express Edition
 Oracle database version 10g, Standard or Express Edition
 Microsoft SQL Server 2014, Standard Edition or Express Edition

Installation Manual
Installation
 Microsoft SQL Server 2012 Service Pack 1, Standard Edition or Express Edition
 Microsoft SQL Server 2008 (and 2008 R2), Standard Edition or Express Edition
If one of these database tools already exists on your network, the installation process
connects to the existing database.
 Consult with your database administrator or IT personnel to
obtain connection information.
If you connect to an existing Oracle database, you will need to know the
Instance Name, the SYS password, and the SYSTEM password.
If you connect to an existing Microsoft SQL Server database, you will need
to know the SQL Database Instance Name and the SA Password.
 If you are installing a client and are not updating the host
database, you only need the database instance name.
 Refer to the Upgrading an Existing Version of the Software
section for more information on database upgrade options.
 If a supported database tool is not already installed, you can download one from
skf.com / SKF @ptitude Analyst software downloads, Database engine downloads.
(Refer to Download and Install the Database Manager Application later in this
chapter). You must install either Oracle 11g Express or SQL Server Express
before installing the SKF @ptitude Analyst application.
 If your system is running Windows 7 operating system (32 or 64-bit) and you wish
to install Oracle, you must obtain Oracle 11g R2 (32-bit) from the manufacturer.
Important
Oracle 11g Express offers up to 11 GB of database storage capacity and a limit of
one named instance, and SQL Server 2014 offers up to 10 GB of database storage
capacity and a limit of one named instance. If you require more storage capacity,
or more than one named instance, you must upgrade to a production version of the
database from Oracle or Microsoft. Your Database Administrator needs to install
the database prior to running the SKF @ptitude Analyst installation. Only Oracle
32-bit is supported when the SKF @ptitude Analyst software and its utilities are
installed on the same computer.
Important
When installing the Microsoft SQL Server database manager, make sure you
configure a Mixed Mode authentication.

Installation Manual
Installation
Network Considerations
There are two possible installation scenarios:
 Multi-user Installation – Provides multi-user capability. The database is installed
on a server computer. The applications that interact with the data are installed on
additional client computers and access data over the network.
 Single-user installation – Installs both the database and the applications on a
single computer. All data access is performed locally.
If you are performing a single-user installation, you need only ensure the computer on
which you are installing meets the minimum system requirements.
If you are performing a multi-user installation, you must choose a computer to host and
serve the data. When selecting the database computer, keep the following in mind:
 The computer where the data resides must have sufficient hard drive space for the
initial installation files, plus any data that is added. At least 20 gigabytes of free
disk space is recommended.
 The computer where the data resides needs to be accessible on your network to all
of the computers that will be using the applications.
 The computer where the data resides needs to be turned on when other people
want to use the software.
Once you’ve decided where to install the database server, you can perform the client
installation on any other computers that need to access the data.
Important
The 32-bit Oracle database client must be installed and configured on the local
client workstation prior to installing SKF @ptitude Analyst. Contact your database
administrator or IT department for assistance.
Transaction Server Service Considerations

If you are performing a multi-user installation, in addition to the database server, you
also need to select a computer to host the SKF @ptitude Transaction Server service.
The Transaction Server acts as a communication layer between the applications and the
database, streamlining database access for faster processing in a wide area network
environment. The Transaction Server can be installed on the database server computer
or on one of the client computers (on the same local area network as the database
server). During installation, you must either configure the Transaction Server locally, or
enter the machine name or IP address where a previously configured Transaction
Server is located.
When selecting the Transaction Server host, keep the following in mind:
 If you are operating on a wide area network, the Transaction Server host should be
on the same local area network as the database host.
 The computer where the Transaction Server is installed needs to be accessible on
your network to all of the computers that will be using the applications. Make note
of the connection information (machine name or IP address and the TCP port

Installation Manual
Installation
number) for the Transaction Server host as it is needed when configuring

Transaction Server clients.
 The computer where the Transaction Server is installed needs to be always turned
on, so it is recommended that you install it on a server class machine that is either
the database server, or on the same local area network as the database server.
 Transaction Server uses a TCP port that is defined during the installation (default is
8088). Make sure to allow this port by your firewall software installed on the host
computer.
Important
Only Oracle 32-bit is supported when the SKF @ptitude Analyst software and its
utilities are installed on the same computer.
Windows Operating System Compatibility

Windows Vista Issues
Windows Vista is no longer supported by any SKF software.
Windows 7, 8.1 or 10 User Account Control (UAC) and Windows 7, 8.1 or 10 64-bit
Compatibility
Some SKF @ptitude Analyst applications and add-ons, and some SKF data acquisition
devices (DADs) that communicate with @ptitude Analyst have Windows 7, 8.1 or 10
UAC restrictions and/or Windows 7, 8.1 or 10 64-bit restrictions. The following two
tables specify these restrictions.
Note 1 - Core Modules = SKF @ptitude Inspector [CMSW 7200], SKF @ptitude Analyst
for Microlog Analyzer [CMSW 7300] and SKF @ptitude Analyst [CMSW 7400].
Note 2 - Add-Ons = Trend Oil [CMSW 7308] and Work Notification [CMSW 7302].
Note 3 - UAC level must be set to "low."
Note 4 - Decision Support is supported on Windows Server 2008 R2 and Windows
2012 R2.
Note 5 – If you are using Oracle for your database, then Oracle 32-bit or Oracle 32-bit
Client is required when installing these utilities on the same server or client PC.
Note 6 – Download the 64-bit driver from the SKF Microlog Analyzer series download
page. For proper driver installation, you must connect and power on a Microlog
Analyzer device before proceeding with the installation package. If the device is not
available at the time of installation, you must reinstall the device drivers when you first
connect and power on the Microlog Analyzer device.

Installation Manual
Installation
Application / Utility Win 7, 8.1 Win 7, 8.1 or

or 10 10
32 bit 64 bit
SKF @ptitude Analyst 9 (Core modules 1 and Add-ons2)
Including the following utilities:
Transaction Service5
IMx Service5
WMx Service5
Microlog Service5 Yes Yes
License Key Manager (Requires OS Admin level)
ConfigTool (Requires OS Admin level) 5
IMx Serial Configurator
SKF @ptitude Analyst Monitor5
Installers for all applications (Requires OS Admin level)
Supporting Applications
SKF @ptitude Decision Support version 3.3 [CMSW 7450] (add-ons + utilities) Yes No4
SKF @ptitude Analyst HMI version 1.x [CMSW 7203] No No
SKF @ptitude Analyst Thin Client Transfer 2013 [CMSW 7320 & 7321] Yes Yes
Interfaces and Miscellaneous
SAP 4.7 & 7.1 interface for SKF @ptitude Decision Support and core modules 1 Yes3 Yes3
3
SKF @ptitude Analyst OPC client version x.x [CMSW 7473] Yes No
SKF @ptitude Software Developers Kit version x.x (@SDK) Yes Yes
3
SoundByte Yes Yes
3
PRISM Conversion Yes No
Ivy, CMU Configurator Yes3 No
3
DMx Manager Yes No
1 - 10 SKF @ptitude Analyst

Installation Manual
Installation
Data Acquisition Devices (DADs) Minimum Win 7, 8.1 Comment

F/W or 10
Version 64 bit
SKF Multilog DMx 7.2 No

SKF Multilog IMx 5.0 Yes Unit types –S, -M, -T, -P, -B, -C
SKF Multilog WMx [CMWA 7830, CMWA 2.05.03 Yes
7820]
SKF Wireless Machine Condition Sensor Win 7 Via CMWA 8800 manager software / XML
[CMWA 8800]
SKF Microlog Analyzer GX [CMXA 70] 2.0.3 Yes
SKF Microlog Analyzer GX [CMXA 75] 4.03 Yes6 Requires 64-bit driver
6
SKF Microlog Analyzer AX [CMXA 80] 4.03 Yes Requires 64 bit driver
SKF Microlog Analyzer IS [CMXA 51-IS] 1.12 Yes6 Requires a third party USB to Serial cable
and 64-bit driver
SKF Microlog Analyzer CMVA 65 3.81 Yes6 Requires a third party USB to Serial cable
and 64-bit driver
SKF Microlog Inspector [CMDM 6600] 1.4.5.4 Yes
SKF Microlog Inspector [CMDM 6700] 1.4.5.4 Yes
SKF MARLIN [CMDM 5460] 4.23 Yes Operating under Windows Mobile 2005
SKF MARLIN [CMDM 6200] 4.5 Yes
Legacy On-Line Systems

SKF Multilog W/VT No
SKF Multilog LMU 3.32 No
SKF Multilog CMU and TMU 5.1 No Recommended to operate under
Windows7 32-bit3
Installation Order
Use the following order when installing on multiple computers:
1. Perform the installation on the database server computer, installing or
connecting to the appropriate database;
2. Perform the installation on the computer that will act as the Transaction Server;
3. Perform the remaining client installations, connecting to the database server
and Transaction Server host.
 Install additional applications (that is, SKF @ptitude Decision
Support and SKF @ptitude Analyst Thin Client Transfer) on each
computer after the SKF @ptitude Analyst software has been
installed.
SKF @ptitude Analyst 1 - 11

Installation Manual
Installation
Upgrading an Existing Version of the Software
 This information applies to prior versions of SKF @ptitude

Analyst, @ptitude Inspector, Machine Suite, Machine Analyst,
Machine Inspector, and Machine Observer.
Important
Ensure you have a full backup of the database before proceeding with the upgrade.
If you are upgrading from a prior version of the software, you have two options
regarding your existing data:
1. You can leave the older version of the database manager installed and simply
upgrade the structure of the database to be compatible with the new software
version.
If you choose to continue to use the older version of the database manager, the
database upgrade is performed using the SKF @ptitude Analyst Configuration
Tool.
2. If you would like to upgrade your database manager, you can install a new
version of the database manager and migrate the older data. For your
convenience, the SKF @ptitude Analyst software downloads web page contains
Database engine downloads options. Choose either Microsoft SQL Server or
Oracle. The links take you to Microsoft or Oracle so you can download the latest
versions of the Express editions. Select the corresponding supporting database
to download.
If you choose to install a new version of the database manager, the new
database must be in place prior to installing SKF @ptitude Analyst. Work with
your Database Administrator or IT Personnel to upgrade the database and
create a data migration plan.
The procedure to migrate existing data varies depending on the database type
that is selected.
WARNING
Oracle 11g Express offers up to 11 GB of database storage capacity and SQL
Server 2014 offers up to 10 GB of database storage capacity. If you would like to
upgrade your database manager, but your existing database is larger than 11 GB /
10 GB, or could become larger over time, do not install the express edition of the
database manager. (To determine the size of your current Oracle database, add up
the file sizes of all .dbf files associated with your database name.) Instead,
purchase an upgraded database manager from Oracle or Microsoft.

Installation Manual
Installation
Migrating to Oracle 11g or 11g XE

Use the following steps to migrate prior version data to Oracle 11g or 11g XE.
1. Prior to running the SKF @ptitude Analyst installation, open the older version
of the Oracle Database Manager and create a dump file of your Oracle
database. (Refer to your Oracle Database user manuals for instructions.)
2. Obtain Oracle 11g from Oracle and work with your database administrator to
install the new database manager. (Oracle web site is accessible through
skf.com > SKF @ptitude Analyst software downloads > Database engine
downloads.
3. Configure the new database instance with the required table spaces. Use the
provided skfuserts.sql script to identify the sub steps required for this step.
Work with your database administrator to complete this step.
4. Access the newly installed Oracle Database Manager and import the dump file
created in step 1.
5. Run the SKF @ptitude Analyst installation and connect to the existing database.
The structure of the imported database will be upgraded to the current
version.
Migrating to SQL Server Standard Edition or Express Edition from

Oracle (recommended)
Use the following steps to migrate prior version data to Microsoft SQL Server Express
Edition or Standard Edition, from an Oracle database.
1. Prior to installing SKF @ptitude Analyst, open your SKF software application
(Machine Suite, Machine Analyst, Machine Observer, or Machine Inspector) and
select the File menu’s Export / Analyst Data option.
Use the Export Analyst Data wizard to create a .MAB file that contains your
Analyst data.
WARNING!
This option only exports hierarchy setup and historical data. Report settings,
filters, and user preferences will need to be recreated in the new installation.
WARNING!
You must export your data from the previous version of the software prior to
running the SKF @ptitude Analyst installation. Although the prior version data will
still exist in your Oracle database (assuming you do not uninstall Oracle), you will
not be able to access the older database from within SKF @ptitude Analyst to
perform the export after upgrade. (If this should occur, contact Technical Support
for assistance.)

Installation Manual
Installation
2. During SKF @ptitude Analyst installation, select the option to install the
Microsoft SQL Express Database Manager.
OR
Purchase Microsoft SQL Server Standard Edition from Microsoft and work with
your database administrator to install the database manager prior to running
the SKF @ptitude Analyst installation. During the SKF @ptitude Analyst
installation, connect to the newly installed database manager.
 If you install the Microsoft SQL Server database manager prior to
the SKF @ptitude Analyst installation, make sure you select the
Mixed Mode Authentication during the Microsoft SQL Server
installation.
3. Use the SKF @ptitude Analyst Configuration Tool to attach the provided demo
database (SKFUSER.mdf). Reference Chapter 2, SKF @ptitude Analyst
Configuration Tool for details.
4. Once the installation is complete, open SKF @ptitude Analyst and select the
File menu’s Import / Analyst Data option to import the prior version’s data.
Migrating from prior version to a later SQL Server version

Use the following steps to migrate a prior version data to a newer Microsoft SQL Server
version.
 It is recommended that you close all SKF @ptitude Analyst
connections before proceeding with the migration process.
1. Before running the SKF @ptitude Analyst installation, open the prior version of
Microsoft SQL Server Management Studio and connect using your SA
Password.
2. Detach the SKFUSER.mdf and .ldf database files from your prior version of
Microsoft SQL Server database.
To detach the SKFUSER.mdf / .ldf database files:
 In SQL Server Management Studio, on the Object Explorer pane,
expand the Databases folder and locate the SKFUSER folder.
 Right click the SKFUSER folder and select Tasks / Detach. The
Detach Database dialog displays.
 Enable the drop connections check box and click OK. The .mdf /
.ldf files are removed from your prior SQL Server database.
3. Exit SQL Server Management Studio.
4. Disable or uninstall your prior version of Microsoft SQL Server.
 Only one service can run at a time. If you no longer need the
prior version of Microsoft SQL Server, it is recommended that you
uninstall it. If you do not uninstall the prior version of Microsoft
SQL Server, you must disable the service to run a newer version
of Microsoft SQL Server.

Installation Manual
Installation
To disable the services:

 Open the Computer Management screen on your computer
(Start / Control Panel / Administrative Tools / Computer
Management) and expand the Services and Applications node in
the left pane and click Services.
 In the right pane, scroll to the SQL Server services and right click
each service and select Properties. The Service Properties
screen displays.
 On the Service Properties screen’s General tab, change the
Startup Type to Disabled, and press Stop to stop the service.
Click OK.
5. Install the newer version of Microsoft SQL Server (administrative rights
required).
 Purchase the newer version of Microsoft SQL Server Standard
Edition from Microsoft and work with your database administrator
to install the database manager prior to running the SKF
@ptitude Analyst installation. During the SKF @ptitude Analyst
installation, connect to the newly installed database manager.
6. Attach the SKFUSER database to the newer version of SQL Server.
To attach the SKFUSER database to the newer version of SQL
Server database:
 Locate the .mdf file you detached from the prior version of SQL
Server. These files are typically located at C:\Program
Files\Microsoft SQL Server\MSSQL\Data.
 Move the SKFUSER.mdf database file to your newer version of
SQL Server Data folder, or another accessible location.
 Open newer version of Microsoft SQL Server Management Studio
and connect using your SA Password.
 In Management Studio, on the Object Explorer pane, right click
the Databases folder and click Attach. The Attach Databases
dialog displays.
 In the Databases to Attach area, click Add. The Locate
Database Files dialog displays.
 Browse to the SKFUSER.mdf file and select it. Click OK. On the
Attach Databases dialog, the SKFUSER.mdf / .ldf files display in
the “skf user” database details area.
 Click OK. The Database folder on the Object Explorer pane
updates to show the listing for the SKFUSER database.
Once the database is attached, the newer version of SQL Server
database will migrate the prior version of SQL Server SKFUSER
database system files to the newer version of SQL Server.

Installation Manual
Installation
The Download and Installation Process
7. Rebuild the SKFUSER database’s users.

To rebuild the SKFUSER database’s users:
 Use the SKF @ptitude Analyst Configuration Tool to run the
following sql script:
Rebuild_loginname_username_links.sql (typically located in the
dbassist/scripts-sql server installation folder)
 Reference the Run SQL Script section in Chapter
2, SKF @ptitude Analyst Configuration Tool for
details on running SQL scripts.
 When prompted for an SQL Server Password, select the Use SA
user option and enter your SA Password.
The Download and Installation Process
Reference the SKF @ptitude Analyst Installation and Upgrade Matrix at the beginning of
this chapter. Depending on your type of installation, you may or may not be required
to:
 Download and install Prerequisite applications.
 Download and install the Database Manager.
 Download and install the SKF @ptitude Applications.
 Configure the installed database.
 Update the database.
Important
If you are upgrading from a prior version, create a full backup of your database
before proceeding. Refer to the previous Upgrading an Existing Machine Suite
Installation section for details.
Download and Install Prerequisite Applications
The following programs must be installed before you can run the SKF @ptitude Analyst
installation:
Windows Installer (Required for Windows Server 2008/2008 SP1 only)
.Net Framework (V3.5 and V4.0) (Required for Windows 7 and Windows
Server 2008 only)
 If you do not install these programs, you will not be able to run
the SKF @ptitude Analyst installation.
 These programs may already be installed on your system.
 Go to skf.com > SKF @ptitude Analyst software downloads > Prerequisites for SKF
@ptitude Analyst to download each prerequisite program you are missing.

Installation Manual
Installation
Download and Install the Database Manager Application
 Double-click WindowsInstaller.exe to initiate installing Windows Installer.

 Follow the installation instructions to completion.
 If a prerequisite is already installed, a message displays indicating
that the prerequisite is already installed on your system.
 You may be prompted to restart your computer after running the
Windows Installer and .Net Framework.
 Double-click dotNetFx40_Full_setup.exe to initiate installing .Net Framework. See
the note below if you have Windows 10 Operating System.
 Follow the installation instructions to completion.
 Enter the following command line:
Dism /online /enable-feature /featurename:NetFX3 /All /Source:D:\sources\sxs
/LimitAccess .
Important: When installing Windows 10 Operating System, if your computer is

connected to the Internet, the Windows 10 installation will automatically download
.Net 3.5. If your computer is NOT connected to the Internet, you must install .Net
3.5 from the Windows 10 installation media (CD or USB).
A Note about Microlog Analyzers and Windows Mobile Device

Center
If you intend to use Microlog Analyzers, you must also install Microsoft’s Windows
Mobile Device Center. Windows Mobile Device Center offers device management and
data synchronization between a Windows Mobile-based device and a computer
software for synchronizing devices. Windows Mobile Device Center is compatible with
Windows 7, Windows 8.1 and Windows 10. You can download Windows Mobile Device
Center from the Microsoft website. Go to https://support.microsoft.com/en-
us/kb/931937 for detailed information about Windows Mobile Device Center and which
version you should download.
 You may find that this program has already been installed on your
system as part of the Windows 7 or Windows 8 installation.
Downloading the Database Manager

Prior to installing SKF @ptitude Analyst, you must have SQL Server or Oracle installed
as your @ptitude Analyst database manager.
 Go to skf.com > SKF @ptitude Analyst software downloads > Database engine
downloads.
 Click the link for the database manager application you want to use: SQL Server
2014 ExpressAndTools or Oracle 11g XE.
 Download the product from the manufacturer’s website.

Installation Manual
Installation
 Next, download the corresponding SQL Server or Oracle demo database executable
file.
 If you downloaded the SQL Server demo database, double-click
AptitudeAnalystSQLDemoDatabase.exe. to extract the demo database files.
 If you downloaded the Oracle demo database import .DMP file, double-click
p4demodb.dmp to extract the demo database files.
The installation procedures for both SQL Server 2014 and Oracle 11g are described
below.
Important: The following database manager installation procedures apply only to

“standard, first time installations.” Non-standard installations and product
upgrades may, or may not, use existing databases. Reference the SKF @ptitude
Analyst Installation and Upgrade Matrix at the beginning of this chapter for more
information.
Installing the Database Manager

To install the SQL Server 2014 Express database tool (software):
 Double-click Setup.exe.
 You should simply click OK, Next, or Install (as applicable) for each dialog as you
progress through the installation. The installation dialog progression is listed below
(of course, this does not apply for those wishing to customize their database
installation).
Setup Support Rules (click OK)
Product Key (click Next)
License Terms (click Next)
Support Setup Files (click Install)
Setup Support Rules (click Next)
Setup Role (click Next)
Feature Selection (click Next)
Installation Rules (click Next)
Instance Configuration (click Next)
Disk Space Requirements (click Next)
Server Configuration (click Next)
Database Engine Configuration (Next) (Note - on this dialog, the default
password for the Sql Server “sa” is specified as “skf_admin1”. Please make a
note of this.)
Error Reporting (click Next)
Installation Configuration Rules (click Next)
Ready to Install (Install)
Complete (Close)

Installation Manual
Installation
With the SQL Server database manager software successfully installed, you are ready to
download and install Analyst.
To install the Oracle 11g Express database:
 If installing a full version Oracle database, your IT / database
administrator may contact SKF Technical Support Group for
assistance.
 You should simply click OK, Next, or Install (as applicable) for each dialog as you
progress through the installation. The installation dialog progression is listed below
(of course, this does not apply for those wishing to customize their database
installation).
Install Wizard Welcome dialog (click Next)
License Agreement (click Next)
Choose Destination Location (click Next)
Specify Database Passwords (enter and confirm the SYS and SYSTEM
database account password and click Next – make a note of this password for
future reference).
Summary (click Install)
InstallShield Wizard Complete (click Finish)
With the database manager software successfully installed, you are ready to download
and install Analyst.

Installation Manual
Installation
Download and Install the SKF @ptitude Analyst Applications
To download the Analyst software:

 Verify that your computer meets the minimum system requirements (presented
previously in this manual).
 Download the appropriate @ptitude Analyst EXE file.
 There is a 64-bit and a 32-bit version of the EXE, so make sure
you download the correct one (AptitudeAnalystV9_64Bit.exe or
AptitudeAnalystV9_32Bit.exe) for your computer.
Figure 1 - 1.
Example of the Analyst Software Downloads Matrix.
Installing the Analyst Software

SKF offers the option to purchase a version of SKF @ptitude Analyst that supports a
specific data acquisition device (i.e., SKF @ptitude Analyst for SKF Microlog Analyzer,
SKF @ptitude Analyst for SKF Multilog On-Line Systems TMU, SKF @ptitude Inspector
for MARLIN and Microlog Inspector), or to purchase the full SKF @ptitude Analyst
product, which supports all Analyst data acquisition devices. All of these products, as
well as the HMI, Trend Oil, Work Notifications, IT Security, and NT Authentication add-
on applications, are installed using the same installation procedure. (The product that is
enabled during installation is determined by the license key you enter. Refer to Chapter
5, SKF @ptitude Analyst License Key Manager for details.)
 Double click the Setup.exe file (AptitudeAnalystV9_64Bit.exe or
AptitudeAnalystV9_32Bit.exe) to initiate the installation.
 You are prompted to select your desired language from a drop down list.
 Select the appropriate language from the list displayed, or select Other Languages
to view additional language options.
Then, the installation files are extracted and the Welcome to the InstallShield Wizard
for SKF @ptitude Analyst 9 screen appears.

Installation Manual
Installation
Figure 1 - 2.
The Welcome to the InstallShield Wizard Screen.
 Click Next to proceed to the Important Information screen.
The Important Information Screen
Figure 1 - 3.
The Important Information Screen.
 Prior to proceeding with the installation, carefully review the information on this
screen:
SKF @ptitude Analyst requires Microsoft .NET Framework versions 3.5
and 4.0. If not already installed, refer to the Installing Prerequisite

Installation Manual
Installation
Applications section for details on installing .Net Framework. Each version

installs separately.
 Depending on your operating system, the .NET framework
requires anywhere from 280 MB to 610 MB of disk space when
installed.
The SKF @ptitude Analyst installation program requires the Windows 4.5
installer. If it is not already installed, refer to the Planning the Installation
section for details on installing the Windows Installer.
You must be an administrator on the computer to proceed with the
installation.
If you are upgrading from a prior version of the software, ensure you have
a full backup before proceeding.
If you are only installing an application client, make sure you have the host
database location and log on name and password available.
You must have Adobe Reader version 7.0 or higher to view the user
manuals.
 If you have satisfied all of the stated requirements, click Next to proceed with the
installation. If you have not satisfied the requirements, click Cancel to cancel the
installation.
When you click Next, the installer checks to ensure that all required components
are installed. If any components are missing, a message displays informing you
that you need to install the missing components and then retry installing SKF
@ptitude Analyst.
If all required components are installed, the License Agreement screen displays.
The License Agreement Screen
Figure 1 - 4.
The License Agreement Screen.

Installation Manual
Installation
 Carefully read the license agreement. If you do not agree with the terms of the
license agreement, click Cancel to abort the installation. If you agree with the
terms, select I accept the terms in the license agreement, and then click Next to
proceed to the Destination Folder screen.
The Destination Folder Screen
Figure 1 - 5.
The Destination Folder Screen.
The default destination location displays.

 If Thin Client Transfer is already installed on this computer, the
previously selected destination location is automatically used and
this screen does not appear.
 Accept the default location (recommended), or use the Change button to select a
new location.
 Click the Next button to proceed to the Ready to Install the Program screen.

Installation Manual
Installation
The Ready to Install the Program Screen
Figure 1 - 6.
The Ready to Install the Program Screen.
 Click the Install button to begin installing SKF @ptitude Analyst. If you wish to
review or edit settings, click the Back button to return to the previous screen(s).
The installation program proceeds to create the specified installation directory on the
specified drive, and additional subdirectories branching from the specified directory.
Program files are then copied into their appropriate directories. The Setup Status
screen displays progress.
Figure 1 - 7.
The Installing Status Bar.

Installation Manual
Installation
Depending on your installation selections, additional command windows may appear as

settings are configured. When the installation is complete, the InstallShield Wizard
Completed screen displays.
The InstallShield Wizard Completed Screen

The InstallShield Wizard Completed screen allows you to view the Readme file and
launch the SKF @ptitude Analyst Configuration Tool when you click Finish.
Figure 1 - 8.
The InstallShield Wizard Completed Screen.
 If you wish to open the readme file, which contains important information related to
your installation, leave the View the Readme file check box enabled.
 If you wish to launch the Configuration Tool, which allows you to configure a new
@ptitude Analyst database or update an existing @ptitude Analyst database, enable
(select) the Launch the Analyst Configuration Tool check box.
 Reference Chapter 2, SKF @ptitude Analyst Configuration Tool
for more information.
 Click Finish to close the wizard and return to the main installation menu.
If you selected to read the readme file, a window opens where you can read and/or print
the installation notes.
If you selected to launch the Configuration Tool the SKF @ptitude Analyst Configuration
Tool window displays.
 After installation is complete, you must first launch the SKF
@ptitude Analyst Configuration tool and configure or update your
@ptitude Analyst database before launching the SKF @ptitude
Analyst application. Refer to What’s the Next Step? below for
details.

Installation Manual
Installation
User Manuals
 Refer to SKF @ptitude Decision Support Installation instructions,

which are available from the product web page.
 Thin Client Transfer installation is detailed in the Installing SKF
@ptitude Analyst Thin Client Transfer section, later in this manual.
User Manuals
It is recommended that you refer to the SKF @ptitude Analyst Introduction and Global
Features user manual’s Starting SKF @ptitude Analyst section for instructions and initial
login details.
Product user manuals (in Adobe Acrobat PDF format) are available from the SKF
@ptitude Analyst software download web page. Scroll to SKF @ptitude Analyst user
manual installers.
 Select the language you desire. Each of the language links downloads a Microsoft
Installer (.msi) file.
 After downloading, double click the .msi file to open the wizard.
 Follow the instructions in the wizard to extract the @ptitude Analyst user manuals.
After the files are extracted, the user manuals may be accessed from the Windows
Start menu.
 Adobe Reader version 7.0 or newer is required to view and print
the .pdf version manuals. Download and install Adobe Reader
from the Adobe website if needed.
Setting Up License Keys
At some point after you have completed the basic installation, you must set up license
keys using the SKF @Aptitude Analyst License Key Manager, accessed via the Windows
Start menu’s All Programs / SKF @ptitude Monitoring Suite / Admin Tools / License
Key Manager option.
Reference Chapter 5, SKF @ptitude Analyst License Key Manager for details on setting
up your license keys, or click the Help button to use the help file.
What’s the Next Step?
After installing SKF @ptitude Analyst, the next step you take depends on if you need to
install additional applications and what devices you will be using (reference the SKF
@ptitude Installation and Upgrade Matrix at the beginning of this chapter).
The SKF @ptitude Transaction Server is used as a communication layer between the
applications and the database. This is desirable in a network environment where
multiple clients may try to access the database at the same time. The Transaction
Server processes some of the database requests, reducing the load on the database
itself, thereby increasing performance.

Installation Manual
Installation
What’s the Next Step?
 You will need to install one Transaction Server per database

installation for proper operation of the software system. Each
instance of the Transaction Server must be installed on a
different computer. You cannot have multiple instances of the
Transaction Server running on the same machine.
Follow the steps below:
 (Required for all users) Launch the SKF @ptitude Analyst Configuration Tool, which
is automatically installed during the SKF @ptitude Analyst installation, to configure
your database to work with SKF @ptitude Analyst. If running a WMx / IMx system
and / or Microlog Inspector, this is also where you will set up WMx / IMx / Microlog
Inspector devices in SKF @ptitude Analyst. Reference the SKF @ptitude Analyst
Configuration Tool chapter for detailed instructions on how to configure your
database.
o If you are a new user, you must first acquire the demo database file(s), then
configure your database by first selecting your database type on the Database
Type dialog, and then either Attach to an SQL database or Import an Oracle
database’s dump file on the Change Database dialog. Reference the Chapter
2, Database Configuration/Change Database section for details.
o If you are an existing user, you must update your database on the Update
Database screen.
 Run the Transaction Server for each standalone and server database installation.
Client installations must be configured to point to the transaction server location.
Reference the SKF @ptitude Analyst Configuration Tool chapter for detailed
instructions on how to run and configure the Transaction Server.
 If you will be running an IMx system, launch the Multilog IMx Configurator to set the
network configuration and identification for the IMx devices. Reference the SKF
Multilog IMx Configurator User Manual for details.
 Install any additional applications (e.g., Thin Client Transfer) you have purchased
that were not already installed with SKF @ptitude Analyst. (Refer to A Note about
the Download Installation Image above for details on what is and is not installed
with SKF @ptitude Analyst.) Reference the installation instructions, either in this
manual or in the product’s documentation to complete their installation.
Run the database configuration if:
 A database administrator configures a new database after SKF @ptitude Analyst
has been installed.
 A user has multiple database instances (for example, a service engineer).
 Upgrading an existing database.

Installation Manual
2
SKF @ptitude Analyst Configuration Tool
Database Configuration Options
After completing installation of your SKF @ptitude Analyst application(s), your next step
is to configure your database to work with SKF @ptitude Analyst.
 From the Windows Start / SKF @ptitude Monitoring Suite / Admin Tools menu,
select the SKF @ptitude Analyst Configuration Tool option. A warning message
displays, advising caution, then Configuration Tool help automatically displays and
you are prompted whether to show help on startup again (answer appropriately),
then the SKF @ptitude Analyst Configuration Tool window displays.
If you are a new user, you must first acquire the demo database file(s), then configure
your database by first selecting your database type on the Database Type dialog, and
then either Attach to an SQL database or Import an Oracle database’s .dmp file using
the Change Database dialog.
If you are an existing user, you must update your database on the Update Database
screen.
Figure 2 - 1.
The SKF @ptitude Analyst Configuration Tool Main Window.

Installation Manual
The window’s left pane displays two main configuration options:

Database configuration options – provide options for specifying a database
type, changing to a different database, adding users for existing databases,
updating the database, and running an SQL script.
SKF @ptitude Analyst Configuration Tool options – allow you to configure
various supporting SKF @ptitude Analyst applications.
You first use the Database options to configure your database, then you proceed to use
the lower section to configure other installed applications.
Specify the Database Configuration Tool

Before applying database configuration options, you may need to use the File menu’s
Setting option to specify which database tool to use to execute all database relevant
functions (i.e., Run SQL script, etc.), if the database tool is not found in the default
location on the computer.
To specify the database configuration tool:
 Select the File menu’s Settings option. The Settings dialog displays.
Figure 2 - 2.
The File Menu’s Settings Dialog.
 Use the options buttons to select either:

Automatically find suitable database tool for databases – The application
will search for the proper database tool for the installed database.
Specify a database tool for Configuration Tool – If necessary, use the
Browse button to specify the correct database tool (i.e., if working with
multiple databases).

Installation Manual
Multi-database Mode of Operation

On the Analyst Configuration Tool’s Settings dialog, you can select the checkbox Multi-
database mode to enable the system to operate in multi database mode. This may
mean that two or more databases can operate in sync OR that two or more instances of
the same database can operate.
Multi-database mode is supported by the following services:
 Transaction Service
 IMx Service
 Microlog Service
To enable the Multi-database mode of operation:
 Select the checkbox Multi-database mode.
 Click OK. A warning message about changing multi-database mode displays.
Figure 2 - 3.
Multi-database Mode Change Warning.
Enabling this mode will require you to delete the existing services and then recreate
them. Enabling this mode will change some of the available options in the services. For
example, in multi-database mode the Stand Alone System becomes unavailable as a
Transaction Server Type.
 Click Yes to continue and apply the change.
If you have a Transaction, IMx or Microlog service dialog open when you enable or
disable multi-database mode, you will have to navigate to another page and then return
in order to see the changed settings. Multi-database mode will stay in effect until you
disable it.
For details about the specific changes in the Transaction, IMx or Microlog services, refer
to the appropriate section below about the service.

Installation Manual
Database Type
To disable multi-database mode:

 Deselect the Multi-database mode checkbox.
 Click OK.
 In the warning, click Yes to continue.
Just as with enabling the multi-database mode, you will need you to delete the existing
services and then recreate them. You will also have to navigate away from an open
service dialog and then return in order to see the changed settings.
For more information about the configuration of services in multi-database mode, see
the applicable multi-database mode information under the SKF @ptitude Transaction
Service, SKF @ptitude IMx Service and SKF @ptitude Microlog Service sections later in
this chapter.
Database Type
Sections below describe database installation procedures for both a standard single
client database installation and a custom database installation. Reference the section
appropriate for your type of installation.
Standard, Single Client Database Installation
Procedures below detail how to set up both SQL Server and Oracle Demo databases.
Follow the procedure that is appropriate for your type of installation.
SQL Server Demo Database
 Extract the Demo database files from the AptitudeAnalystSQLDemoDatabase.exe
file that was downloaded from the Database engine downloads link.
To set the type of database to SQL Server:
 Launch the SKF @ptitude Analyst Configuration Tool.
 Under Database, select the Database Type option. The Database Type
Configuration screen displays.

Installation Manual
Database Type
Figure 2 - 4.
The SQL Server Database Type Configuration Screen.
For default installations, the Connections and Connection Title fields display
sql_skfuser.
 Press the Set active button to set the sql_skfuser database type. A confirmation
prompt appears.
To attach the SQL Server Demo database:
 In the Configuration Tool’s left pane, under Database, select the Change Database
option. The Database Import/Attach Configuration dialog displays.
 Press the Attach/Switch button to attach the SQL Server Demo database. A file
Open dialog displays.
 Browse to select the skfuser.mdf file previously stored in the SQL Server default
location.
 Press the Open button. A dialog then prompts you for the SA password.
 Enter the default password “skf_admin1” (lower case). You are prompted to wait,
and then an “attach database success” prompt appears. Press OK. You must now
perform the Update DB option (reference the Update Database section later in
this chapter).
Oracle Demo Database 11g

The general steps for acquiring and using the Oracle Demo database are:
 Set the database type to Oracle.
 Import the file.

Installation Manual
Database Type
To set the database type to Oracle:

 Launch the SKF @ptitude Analyst Configuration Tool.
 Under Database, select the Database Type option. The Database Type
Configuration screen displays.
Figure 2 - 5.
The Oracle Database Type Configuration Screen.
For default installations, the Connections and Connection Title fields display
ora_skfuser.
 Press the Set active button to set the ora_skfuser database type. A confirmation
prompt appears.
To import the Oracle Demo database:
 In the Configuration Tool’s left pane, under Database, select the Change Database
option. The Database Import/Attach Configuration dialog displays.
 Press the Import button to import the Oracle Demo database. A file Open dialog
appears.
 Browse to the p4demodb.dmp file, which was downloaded from skf.com > SKF
@ptitude Analyst software downloads > Database engine downloads section. Click
the Open button. A dialog then prompts you for the SYS password.
 Enter the password you selected during the Oracle 11g Express installation and
press OK. You are then prompted for the SYSTEM password. Enter the same
password and press OK. You must now perform the Update DB option (reference
the Update Database section later in this chapter)

Installation Manual
Database Type
Custom Database Installation

Specify the type of database to use with SKF @ptitude Analyst.
Figure 2 - 6.
The Custom Database Type Configuration Screen.
Options Include:
Connections - Specify the selected database’s name.
Database connections identify a specific SKF @ptitude Analyst database by its Db
connect name and type. Database connections are configured and given a Connection
title for identification purposes when configuring your Services. You must configure a
database connection for each SKF @ptitude Analyst database with which you wish to
communicate.
To manage SKF @ptitude Analyst database connections:
 Press the Manage button on the Database Type, Transaction Service, IMx
Service, Microlog Service, or WMx Service dialog. The Manage Connections
window appears.

Installation Manual
Database Type
Figure 2 - 7.
The Manage Connections Window.
In the Manage Connections window, the Connections drop down list displays existing
SKF @ptitude Analyst database connections.
 Use your mouse to select a database connection from the list, its setup parameters
display in following fields.
 Use the window’s buttons to manage your database connections:
Add – Add a new database connection. Press the Add button, the
configuration fields become available. Specify the new database connection’s:
Connection title – Enter a unique name to identify the database
connection (alphanumeric and underscore characters only).
Db connect name - Input the database connection name of the
specific SKF @ptitude Analyst database.
Database type – Use option buttons to specify the SKF @ptitude
Analyst database as either an Oracle or SQL Server database type.
If you installed the Oracle 11g XE database, the connection name is XE. If you
are connecting to an existing database, enter the appropriate connection name.
If you installed the MS SQL Server Express database, enter
computer_name\SQLExpress (where computer_name is the name of the
computer on which the instance is installed). If you are connecting to an
existing database, enter the appropriate instance name.
 In some circumstances, you will not need the instance name.
Contact your database administrator or IT department for
assistance.

Installation Manual
Database Type
When finished, press the Save button to save the new database connection, or
the Undo button to cancel.
 After pressing Save, the Db Connection Test dialog appears,
allowing you to test the database connection.
Edit – Edit an existing database connection’s configuration. Select the
database connection to edit from the Connections drop down list and press the
Edit button, then edit the connection’s configuration as described above. When
finished, press the Save button to save any changes, or the Undo button to
cancel any changes.
Remove – Remove an existing database connection (available only for
database connections not being used by any IMx / Microlog Service). Select the
database connection to remove from the Connections drop down list and press
the Remove button. You are prompted to confirm the removal.
Close – Close the Manage Connections window.
To continue configuring the database type, specify database type information on the
Database Type dialog as follows:
Oracle 10g, 11g, 12c – Select this option if you have configured an Oracle database on
your database server computer.
MS SQL 2008, 2012, 2014 – Select this option if you have configured a Microsoft SQL
database on your host computer.
Oracle Database Passwords
SYS Password - If you installed a new database, enter the password that was
entered at the Specify Database Passwords screen during the Oracle
installation process. If you are connecting to an existing database, enter the
appropriate SYS password.
OR
SYSTEM Password - If you selected to install a new database, enter the
password that was entered at the Specify Database Passwords screen during
the Oracle installation process. If you are connecting to an existing database,
enter the appropriate SYSTEM password.
OR
Custom User Name and Password – To connect as a “specific” user, enter
your user name and password.
Microsoft SQL Server Database Password
SA Password - If you installed a new database, enter the password that was
entered in the Specify the sa logon password field on the Authentication
Mode screen of the SQL Server Express installation wizard. If you are
connecting to an existing database, enter the appropriate SA Password.
OR
Custom User Name and Password – To connect as a “specific” user, enter
your user name and password.

Installation Manual
Change Database
 Enter your password and press OK. Database connection is tested and
resulting success is indicated in the window’s lower right, and in a Success
dialog.
 In the Success dialog, press OK to complete Database Type configuration.
 If you use Database Type options to change to a
different type of database, use the Save button to save
the new database type settings.
Change Database
Figure 2 - 8.
The Change Database Configuration Screen.
If you are utilizing multiple databases, the Change Database option allows you to
Attach to a different SQL Server database, or Import a different Oracle database’s .dmp
file.
WARNING: You should backup your existing database before applying this feature.
To change to a different database or use the demo database:

 In the Data file location field, use the browse button to specify the SQL database’s
.mdf file or the Oracle database’s .dmp file respectively.
 If you are a new user, you can Attach to the Demo database
(p4demodb.dmp) downloaded from skf.com > SKF @ptitude
Analyst software downloads > Database engine downloads.
 When the correct database file is identified, click the Attach button (for SQL Server
databases) or the Import button (for Oracle databases). The process will take
several minutes to complete

Installation Manual
Change Database
User Management
Figure 2 - 9.
The User Management Configuration Screen.
The User Management screen allows you to easily Create new SKF @ptitude Analyst
database users or Delete existing database users.
Creating New Database Users
To create new database users:
 In the New User Name field, type the name of the new user and press the Create
User button. You are prompted for your password, enter your password and press
OK. You are prompted to wait while the new user is created. Success is indicated in
the screen’s lower right, and in a Success dialog.
 In the Success dialog, press OK to complete
 Press the Refresh button to add the new user to the Existing Users list. You are
prompted for your password, enter your password and press OK. Success is
indicated in the screen’s lower right, and in a Success dialog.
Deleting Database Users
To delete an existing database user:
 In the Existing Users list, highlight the user to delete.
 Press the Delete User button. You are prompted for your password, enter your
password and press OK. You are prompted to wait while the user is deleted.
Success is indicated in the screen’s lower right, and in a Success dialog.
 The user is disabled from using the database.

Installation Manual
Update Database
 Press the Refresh button to delete the user from the Existing Users list. You are
prompted for your password, enter your password and press OK. Success is
indicated in the screen’s lower right, and in a Success dialog.
Update Database
Use the Configuration Tool’s Update Database option to update your database.
Figure 2 - 10.
The Update Database Configuration Screen.
To update your database:

In the window’s Update Database area, the Current DB Version field prompts you to
press the Get Version button to display your current database version.
 Press the Get Version button. You are prompted to enter your skfuser1 password.
 Enter your password (default is cm) and press OK. The current database version
displays in the Current DB Version field. Feedback displays in the information
area.
 Compare the Current DB Version with the Available DB Version shown. If the
two versions match, your database is up to date and you may exit the Configuration
Tool. If the Available DB Version is newer than the current database version,
press the Update DB button to update to the available version. You are again
prompted for your password.
 Enter your password and press OK. The database is updated. Results display in
the information area.
 If you are using an Oracle database, and if you have not updated
with previous @ptitude Analyst updates as they were made

Installation Manual
Run SQL Script
available, or if you have previously performed a “custom”

database configuration, a prompt indicates that required INDX
tablespace is missing from your database. In this case, press
OK, then enter your SYS password to create the INDX tablespace
and update the database. If you do not know your SYS password,
press Cancel at the SYS password prompt and ask your Database
Administrator for assistance.
Run SQL Script
The SKF @ptitude Analyst Configuration Tool provides an easy method to run SQL
scripts that help configure or repair your SKF @ptitude Analyst database.
Figure 2 - 11.
The Run SQL Script Configuration Screen.
To run an SQL script:

 In the Script Directory field, specify the folder containing the script you wish to
run.
 In the Script Location field, use the browse button to locate the script to run.
 If you would like to Save the script output as a file, enable the checkbox.
 Press the Execute button. You are prompted to enter your password. Enter your
password and press OK. The script executes and the results display in the Script
Output area.
 If Save script output is enabled, a Save As dialog prompts for file
name, type, and location information. Enter appropriate
information and press OK. The script output file is saved and you
are returned to the Run SQL script screen.

Installation Manual
If necessary, use SKF @ptitude Analyst Configuration Tool options to configure other
applications working with SKF @ptitude Analyst.
General Configuration
This option allows you to modify the settings for SKF @ptitude Analyst applications.
 We do not recommended modifying these settings without the
guidance of SKF service personnel or technical support.
Figure 2 - 12.
The General Configuration Configuration Screen.
On the right side of the screen, the SKF @ptitude Master Settings list displays
configuration settings you are able to modify.
To modify SKF @ptitude Analyst settings:
 In the SKF @ptitude Master Settings list, single-click to select the item you wish
to modify. The selected item displays in the Value name field (read only), and the
selected item’s current value displays in the Value data field.
 Edit the Value data field as necessary and click Save.
You may need to restart SKF @ptitude Analyst and any services for your changes to
take affect.

Installation Manual
SKF @ptitude HMI Connection
SKF @ptitude HMI Connection
This option allows HMI (if installed on the computer) to use the connection service, to
support HMI’s “live data” feature.
 HMI must be activated with a license key prior to setting the
connection service.
Figure 2 - 13.
The SKF @ptitude HMI Connection Configuration Screen.
The Register HMI Connection Service area displays the HMI Connection Service’s
current registration status. Status is either registered or not registered.
 Use the Register or Unregister buttons to change the current HMI Connection
Service registration status.
The HMI Connection Service status area displays the current HMI connection status.
Status is either running or not running.
 Use the Start and Stop buttons to change the HMI Connection Service status.

Installation Manual
SKF @ptitude Transaction Service
Figure 2 - 14.
The SKF @ptitude Transaction Service Configuration Screen.
The SKF @ptitude Transaction Server is used as a communication layer between the
applications and the database. This is desirable in a network environment where
multiple clients may try to access the database at the same time. The Transaction
Server processes some of the database requests, reducing the load on the database
itself, thereby increasing performance.
 You will need to install one Transaction Server per database
installation for proper operation of the software system. Each
instance of the Transaction Server must be installed on a
different computer. You cannot have multiple instances of the
Transaction Server running on the same machine.
Transaction Server Type options are:
Server Host – Select this option to install the Transaction Server on this computer. It is
highly recommended to make the database host (server) the Transaction Server host,
when possible.
 Server Name – always local host
 Server Port - Enter the TCP port used for communication with the Transaction
Server Host. Make sure your firewall software does not block this port.
Client – Select this option if this computer will use a Transaction Server previously
installed on another workstation.
 This option should not be confused with the database client. It is
possible for a database client to be a Transaction Server Host,

Installation Manual
and vice versa (although it is recommended to make the database

host the Transaction server host).
 Server Name – Enter the machine name or IP address of the computer where the
Transaction Server is installed.
 Server Port – Enter the TCP Port used for the communication with the Transaction
Server host. This must match the same port configured on the Transaction Server
host. Make sure your firewall software does not block this port.
Stand Alone System – If this is a stand alone system (i.e., single user), the Transaction
Server is not required for client access, however, it streamlines local database access
and some SKF @ptitude Analyst features (such as DMx integration) may require a
Transaction Server. To accommodate this functionality, the Transaction Server host is
installed on stand alone systems.
 Server Name – always local host
 Server Port - Enter the TCP port used for communication with the Transaction
Server Host. Make sure your firewall software does not block this port.
The Name, TCP port, and Connection Title for existing transaction services display in
the screen’s window.
 Use the Add, Modify, or Delete buttons with the Transaction Service Settings
fields beneath the window to add new services, modify existing services, and delete
existing services.
 If desired, press the Test button to test your transaction service configuration. A
dialog indicates test results.
 Press the Save button to save your configuration.
 Press the Start button to start the selected transaction server.
 Press the Stop button to stop the selected transaction server.
 Press the Manage button to select a database connection. The Manage
Connections dialog displays (reference the previous chapter’s Database Type /
Custom Database Installation section).
Transaction Service Configuration in Multi-database Mode

When Multi database mode is enabled (under File > Settings), two or more databases
can operate in sync OR two or more instances of the same database can operate.
Therefore, you must configure each transaction service and its database connection. In
multi-database mode, you can edit the default Transaction Service database and service
name (this is not allowed in single database mode).
 The Stand Alone System transaction server type is unavailable.
You may choose Server Host or Client.
When you open the Transaction Service page for the first time in multi-database mode,
a prompt tells you the service needs a database connection.
 Recall that when multi-database mode is first enabled, you must
delete the existing services and then recreate them.

Installation Manual
Figure 2 - 15.
Transaction Service Empty Database Warning.
 Click Edit to select a database connection.
Figure 2 - 16.
Transaction Service Type Screen.
The Service name, Server port and Connection title become available for editing.
Also, the Configure… button becomes active.

Installation Manual
Figure 2 - 17.
Ready for Edits; the Configure Button Becomes Active.
 Enter the unique transaction Service name (alphanumeric and underscore

characters only).
 Enter the Server port. Enter the TCP port used for communication with the
Transaction Server Host. Make sure your firewall software does not block this port.
 Select a Connection title.
With the transaction service uniquely identified, it is ready now to be configured.
To configure a transaction service:
 Click the Configure… button to open the Transaction Service Configuration
dialog.

Installation Manual
Figure 2 - 18.
Transaction Service Configuration Dialog.
 In Credentials, enter the Analyst user name and Analyst user password. Contact
the system administrator if you do not know these entries.
 Enter the Database user name and Database user password.
 Contact the system administrator if you do not know these
entries. They would have been created in SQL Server
Management Studio or Oracle.
 Select the Enabled checkbox to enable the Adjust Measurement Date function.
Independent of this function, the system will check the Microlog or other device’s
internal clock as soon as communications with the device is established. If the
device’s clock does not match the system clock, the system will reset the device’s
clock. For example, if the device's battery is completely run down, the internal
device clock resets to 1/1/1980 and any measurements taken after that event, but
before the device's clock is corrected, are 'invalid'. The Adjust Measurement Date
feature is designed to put a meaningful date to such measurements.
If Enabled is selected, the system adjusts the date of measurements downloaded
from the device while it is connected if the measurement date is outside the
number of Tolerance Days (by default, 60 days). The following options apply.
 If disabled, the system will not adjust the measurement dates of
data downloaded from the device while it is connected.
 Note - Select the checkbox to have the system create POINT Notes entries that
reflect any measurement adjustments.
 Event - Select the checkbox to have the system create a new Event Log record that
reflects the measurement adjustments.
 Tolerance Days - Select a numbers of days to establish a tolerance range. Any
measurements taken on or after the start of the specified date range, working

Installation Manual
SKF @ptitude Monitor Recovery
backward from today, are excluded from the measurement date adjustment. The
default is 60; you may enter between 1 and 999.
 Click OK to accept these settings and close the dialog.
 Click Save to create and save the transaction service.
SKF @ptitude Monitor Recovery
Figure 2 - 19.
The SKF @ptitude Monitor Recovery Configuration Screen.
 SKF @ptitude Monitor Recovery must be configured on every

computer on which you are running the SKF @ptitude Analyst
Monitor application.
SKF @ptitude Monitor Recovery is a service that runs in the background to facilitate
recovery (re-launch) of the SKF @ptitude Analyst Monitor application in the event of a
SKF Analyst Monitor failure.
To activate/deactivate SKF @ptitude Monitor Recovery on a computer running SKF
@ptitude Analyst Monitor:
 In the screen’s Status area, information is provided as to the recovery service’s
current state, and buttons are provided that allow you to manually start and stop
the recovery service. If the Service Status indicates the service is not running,
press the Start button to start the recovery service. Then use the Start Mode
Action options to specify how you wish the recovery service to perform after the
computer has restarted.
 In the Start Mode Action area, use the Startup Type drop down list to specify how
you would like the recovery service to start when the computer restarts, either:

Installation Manual
SKF @ptitude Thin Client Transfer
Automatic – (recommended) To direct the recovery service to automatically

restart upon machine restart.
Manual – To specify that the recovery service is to be manually started using
the Status area’s Start button, or manually stopped with the Stop button (in
the event you are not running Monitor on the computer).
Disabled – To disable the recovery service from restarting after the computer
is restarted. The recovery service will not restart unless either Automatic or
Manual are selected and applied.
 After specifying the recovery service’s Startup Type, press the Apply button to save
the new Startup Type, or the Cancel button to cancel the change.
 Use the Register button to re-register the recovery service if it
has been unregistered.
SKF @ptitude Thin Client Transfer
Figure 2 - 20.
The SKF @ptitude Analyst Thin Client Transfer Configuration Screen.
Thin Client Transfer is a small application that deploys very easily and facilitates data
transfer to and from Microlog and MARLIN Data Acquisition Devices (DADs), without
using the SKF @ptitude Analyst interface (via a connection through the SKF @ptitude
Analyst Transaction Server).
After installation of Thin Client Transfer use this screen to specify:
Transaction Server Host – Enter the machine name or IP address of the computer
where the Transaction Server is installed.

Installation Manual
SKF @ptitude Analyst License Key Manager
Transaction Server Port – Enter the TCP Port used for communication with the
Transaction Server host. This must match the same port configured on the Transaction
Server host. Make sure your firewall software does not block this port.
 If desired, press the Test Connection button to test your transaction service
configuration. A dialog indicates test results.
 Press the Save button to save your configuration.
Figure 2 - 21.
The SKF @ptitude Analyst License Key Manager Configuration Screen.
This screen is added as a convenience to allow you to quickly launch the SKF @ptitude
Analyst License Key Manager (detailed in Chapter 5 of this Installation Manual).
To launch the License Key Manager:
 Press the License Key button. The SKF @ptitude Analyst License Key Manager
window appears.

Installation Manual
SKF @ptitude IMx Service
Figure 2 - 22.
The SKF @ptitude IMx Service Configuration Screen.
This screen allows you to add one or more “IMx Services” to the SKF @ptitude Analyst
system (each IMx Service appears on a row in the screen’s table). An IMx Service is
necessary to enable communication between SKF Multilog IMx on-line monitoring
devices and an SKF @ptitude Analyst database storing IMx data.
 To establish communications between the IMx Service and the
IMx devices, you must first set each IMx device’s network
configuration and identification using the SKF Multilog IMx
Configurator.
For communication speed purposes, it is preferable to add the IMx Service to the
computer storing the SKF @ptitude Analyst database. Each IMx Service is able to
facilitate communication between one SKF @ptitude Analyst database and up to 255
IMx devices. Therefore, if you utilize more than one SKF @ptitude Analyst database or
more than 255 IMx devices, you must configure multiple IMx Services. You may add
multiple IMx Services on the same computer, and also on multiple computers on an SKF
@ptitude Analyst network, depending on your needs.
 If you utilize less than 255 IMx devices and only one SKF @ptitude
Analyst database, you may still prefer to configure multiple IMx
Services to facilitate faster communications.
To add a new IMx Service:
 On the computer on which you wish to add the new IMx Service, select the
Configuration Tool’s SKF @ptitude IMx Service option. The IMx Service
Configuration screen appears.

Installation Manual
 Select the screen’s Add button, then use fields in the screen’s Properties area to
configure the new IMx Service.
 If no database connections yet exist, the Manage Connections
dialog automatically appears, allowing you to add a database
connection. Reference the Database Type section earlier in this
manual for more detail.
Name – Enter a unique name to identify the IMx Service (alphanumeric and
underscore characters only).
Port – Enter the computer’s TCP Port used for the communication with the
IMx devices. Each IMx Service must have a unique Port number. Make sure
your firewall software does not block this port.
IMx hostname – Read only, displays the computer’s host name.
Connection title – Database connections identify specific SKF @ptitude Analyst
databases. Select an existing database connection to be used by the IMx
Service from the drop down list.
 If you do not have existing database connections, reference the
Database Type section earlier in this manual for more detail.
Email List – If the service loses connection to the database, and you wish to
automatically receive an email notification about the loss of connection, enable
the Send emails when service loses database connection check box. Click
the Email list button to enter email addresses to which the IMx Service will
send notifications.
Figure 2 - 23.
The Email List Dialog.
 Each email address must be separated by either a comma or

semicolon.
 Before the email recipients can receive these notifications, you
must first configure the SMTP settings. Reference the SMTP
Settings section later in this chapter.
 When finished, press the Save button to save the new IMx Service configuration,
the new IMx Service appears in the table and the new IMx Service initiates, or press
the Undo button to cancel the changes.

Installation Manual
To edit an existing IMx Service:

 Select the IMx Service to edit from the table and press the Edit button, then edit
the IMx Service properties as described above. When finished, press the Save
button to save any changes (confirmation prompts appear), or the Undo button to
cancel any changes.
To deactivate / activate an existing IMx Service:
At times you may wish to deactivate an IMx Service (stop communication between the
IMx devices and its database), then reactivate it at a later time. This operation is needed
if you decide to move the IMx Service to another computer.
 In the table, select the IMx Service to deactivate and press the Deactivate button.
The selected IMx Service is deactivated (but not removed from the IMx Services
table).
 Any IMx devices that were configured to communicate with this
IMx Service will no longer have their data saved in the SKF
@ptitude Analyst database.
The deactivated IMx Service still appears in the table, but when selected, the Deactivate
button changes to an Activate button indicating the IMx Service is not currently
operating. Press the Activate button to resume the IMx Service’s communication
operations.
To remove an IMx Service:
 In the table, select the IMx Service to remove and press the Remove button. The
selected IMx Service is deactivated and removed from the IMx Services table.
 Any IMx devices that were configured to communicate with this
IMx Service will no longer have their data saved in the SKF
IMx Service Configuration in Multi-database Mode

When operating in multi-database mode, more than one database, or more than one
instance of a database, can run on the same computer. Therefore, you must configure
each IMx service and its database connection.
For communication speed purposes, it is preferable to add the IMx Service to the same
computer that stores the SKF @ptitude Analyst database. You may add multiple IMx
Services on the same computer, and also on multiple computers on an SKF @ptitude
Analyst network.
 It is recommended to have approximately one dozen or so devices
per IMx Service to facilitate faster communications.
When Multi database mode is enabled (under File > Settings), the IMx Service
Configuration screen opens as shown below.
 Recall that when multi-database mode is first enabled, you must
delete the existing services and then recreate them.

Installation Manual
Figure 2 - 24.
IMx Service Configuration in Multi-database Mode.
 Click Add.
Figure 2 - 25.
IMx Service Configuration, Add a Service.
The Name, Port and Connection title become editable. Also, the Configure… button is
active.

Installation Manual
 Enter a unique Name for the IMx Service Service (alphanumeric and underscore
characters only). The service name cannot be empty, and cannot be a duplicate of
another DAD service name.
 Enter the computer’s TCP Port used for to communication with the IMx devices.
Each IMx Service must have a unique Port number (an integer in the range of 1 to
32767) that is not in use by another service or application. Make sure your firewall
software does not block this port.
 Host – Read only, displays the host computer’s name.
 Select a Connection title. Database connections identify specific SKF @ptitude
Analyst databases. Select an existing database connection to be used by the IMx
Service.
You must configure the IMx service to set the Analyst username and password and the
Database username and password. Additional configuration options are provided.
To configure the IMx Service:
 Click Configure… to open the Dad Service Configuration dialog.
Figure 2 - 26.
DAD Service Configuration Dialog.

Installation Manual
 Under Credentials, enter the Analyst username and Analyst user password.
 Enter the Database username (current default is skfuserts1) and Database user
password (default is cm).
 Select the Write communication log file checkbox to enable the logging of
communication events.
 Select the Comms log file details level to specify the level (None, Minimal, Debug
or Full) of details to store in the log file.
 Select the BOV check minutes to specify the number of minutes between checks of
the bias output voltage. The default is 5; from 1 to 1440 minutes is allowed.
IMPORTANT: The following parameters (Export of IMx Data in MAULF Format) are
only applicable to specific application needs. Please contact your local SKF technical
services group (TSG) before enabling this functionality.
 Select the Enabled checkbox to enable the Export of IMx Data in MAULF Format.
 Select the Log enabled checkbox to enable log entries during commission.
 Select the Export interval minutes to set the time period between data exports.
The default is default 60; from 1 to 1440 minutes is allowed.
 Enter the Export data path or click Browse to select a path.
 Click OK. The Dad Service Configuration dialog will close.
 Click Save.
The newly configured IMx service will display in the list on the IMx Service
Configuration screen.

Installation Manual
SKF @ptitude Microlog Service
Figure 2 - 27.
The SKF @ptitude Microlog Service Configuration Screen.
This screen allows you to add one or more “Microlog Services” to the SKF @ptitude
Analyst system (each Microlog Service appears on a row in the screen’s table). A
Microlog Service is necessary to enable communication between SKF Microlog Inspector
devices and an SKF @ptitude Analyst database storing Microlog Inspector data.
For communication speed purposes, it is preferable to add the Microlog Service to the
computer storing the SKF @ptitude Analyst database. You may add multiple Microlog
Services on the same computer, and also on multiple computers on an SKF @ptitude
Analyst network, depending on your needs.
To add a new Microlog Service:
 On the computer on which you wish to add the new Microlog Service, select the
Configuration Tool’s SKF @ptitude Microlog Service option. The Microlog
Service Configuration screen appears.
configure the new Microlog Service.
Name – Enter a unique name to identify the Microlog Service (alphanumeric
and underscore characters only).

Installation Manual
Port – Enter the computer’s TCP Port used for the communication with the
Microlog Inspector devices. Each Microlog Service must have a unique Port
number. Make sure your firewall software does not block this port.
Hostname – Read only, displays the computer’s host name.
databases. Select an existing database connection to be used by the Microlog
the Email list button to enter email addresses to which the Microlog Service
will send notifications.
Figure 2 - 28.

semicolon.
 When finished, press the Save button to save the new Microlog Service
configuration, the new Microlog Service appears in the table and the new Microlog
Service initiates, or press the Undo button to cancel the changes.
To edit an existing Microlog Service:
 Select the Microlog Service to edit from the table and press the Edit button, then
edit the Microlog Service properties as described above. When finished, press the
Save button to save any changes (confirmation prompts appear), or the Undo
button to cancel any changes.
To deactivate / activate an existing Microlog Service:
At times you may wish to deactivate a Microlog Service (stop communication between
the Microlog devices and its database), then reactivate it at a later time. This operation
is needed if you decide to move the Microlog Service to another computer.

Installation Manual
 In the table, select the Microlog Service to deactivate and press the Deactivate
button. The selected Microlog Service is deactivated (but not removed from the
Microlog Services table).
 Any Microlog Inspector devices that were configured to
communicate with this Microlog Service will no longer have their
data saved in the SKF @ptitude Analyst database.
The deactivated Microlog Service still appears in the table, but when selected, the
Deactivate button changes to an Activate button indicating the Microlog Service is not
currently operating. Press the Activate button to resume the Microlog Service’s
communication operations.
To remove a Microlog Service:
 In the table, select the Microlog Service to remove and press the Remove button.
The selected Microlog Service is deactivated and removed from the Microlog
Services table.
 Any Microlog Inspector devices that were configured to
communicate with this Microlog Service will no longer have their
data saved in the SKF @ptitude Analyst database.
Microlog Service Configuration in Multi-database Mode

When Multi database mode is enabled (under File > Settings), two or more databases
can operate in sync OR two or more instances of the same database can operate.
Therefore, you must configure each Microlog service and its database connection.
 Due to the switch to multi-database mode, any existing Microlog
Inspector services must be deleted and recreated.
The Microlog Service Configuration screen opens as shown below.
Figure 2 - 29.
Microlog Service Configuration in Multi-database Mode.

Installation Manual
 Click Add.
Figure 2 - 30.
Microlog Service Configuration, Add a Service.
Fields in the Properties section become available. Also, the Configure… button becomes
available.
Name – Enter a unique name to identify the Microlog Inspector Service (alphanumeric
and underscore characters only). The service name cannot be empty, and cannot be a
duplicate of another DAD service name.
Port – Enter the computer’s TCP Port used for the communication with the Microlog
Inspector devices. Each Microlog Service must have a unique Port number. Make sure
your firewall software does not block this port.
Host – Read only, displays the host computer’s name.
databases. Select an existing database connection to be used by the Microlog Service.
 XML file transport is used to download data from the Microlog
Inspector and place it on the computer. The data typically resides
in directory C:\ProgramData\SKF\@ptitude
Analyst\Microlog\Inspector\SERVICE_NAME\Downloaded XML
and Uploaded XML. The Microlog Service transfers the data from
the computer to the Analyst database.

Installation Manual
You must configure the Microlog service to set the Analyst username and password and
the Database username and password. Additional configuration options are provided.
To configure the Microlog Service:
 Click the Configure... button to open the Dad Service Configuration dialog.
Figure 2 - 31.
Microlog Dad Service Configuration Dialog.
 In Credentials, enter the Analyst username and Analyst user password. Contact
the system administrator if you do not know these entries.
 Enter the Database username and Database user password.
 Contact the system administrator if you do not know these
entries. They would have been created in SQL Server
Management Studio or Oracle.
 Check the box to enable Write communication log file.
 Comms log file categories – 0=None, 1=Minimal, 2=Debug, 3=Full.
 Report on devices – Enter the common names, separated by commas, of all
devices you want to log against.
Configure the Microlog service’s file management:
 Keep Downloads Weeks – enter the number of weeks to keep archived download
files on the hard drive before they are deleted.
 Keep Uploads Weeks – enter the number of weeks to keep archived upload files on
the hard drive before they are deleted.

Installation Manual
SKF @ptitude WMx Service
 Max connections – enter the maximum number of Microlog Inspectors that can be
connected to the Service at any one time.
 Status timer (mins) – Enter the number of minutes for the period of time when
the Service writes a message to the log that it is still active and connected. The
minimum value is 1.
 Min interval db emails (mins) – Specify the minimum number of minutes before
the Service sends out an email notice that the connection was lost between the
Service and the Analyst database.
 Db connection check (mins) – Specify number of minutes before the Service
checks the connection to the Analyst database.
 Click OK. The Dad Service Configuration dialog closes.
 Click Save to create the Microlog Service.
Figure 2 - 32.
The SKF @ptitude WMx Service Configuration Screen.
This screen allows you to add one or more “WMx Services” to the SKF @ptitude Analyst
system (each WMx Service appears on a row in the screen’s table). A WMx Service is
necessary to enable communication between SKF Multilog WMx on-line monitoring
devices and an SKF @ptitude Analyst database storing WMx data.
 To establish communications between the WMx Service and the
WMx devices, you must first set each WMx device’s network
configuration and identification using the SKF Wireless
Configuration Utility. Reference the SKF Multilog On-Line System
WMx User Manual for details.

Installation Manual
For communication speed purposes, it is preferable to add the WMx Service to the
computer storing the SKF @ptitude Analyst database. Each WMx Service is able to
facilitate communication between one SKF @ptitude Analyst database and up to one or
more WMx devices. You may add multiple WMx Services on multiple computers on an
SKF @ptitude Analyst network, depending on your needs.
 You can configure multiple WMx Services to facilitate faster
communications.
To add a new WMx Service:
 On the computer on which you wish to add the new WMx Service, select the
Configuration Tool’s SKF @ptitude WMx Service option. The WMx Service
Configuration screen appears.
 When you first open the SKF WMx Service Configuration screen,
a message displays prompting existing WMx users to import their
Wireless DB Builder database into @ptitude Analyst using the
WMx Conversion Utility. To launch the conversion utility, locate
filename skfWMxConversionUtility.exe in C://Program Files/SKF-
RS/@ptitude Analyst and double-click it.
configure the new WMx Service.
Name – Enter a unique name to identify the WMx Service (alphanumeric and
underscore characters only).
Service Port – Enter the computer’s TCP Port used for the communication
with the WMx devices. Each WMx Service must have a unique Port number.
Make sure your firewall software does not block this port.
Internal Port – Enter the internal port number that the WMx Service requires
for internal communications. Typically, this is one digit higher than the Service
Port number. For example, if the Service Port number is 8000, then the
Internal Port number should be 8001.
Host – Read only, displays the computer’s host name.
databases. Select an existing database connection to be used by the WMx
the Email list button to enter email addresses to which the WMx Service will
send notifications.

Installation Manual
Figure 2 - 33.

semicolon.
 When finished, press the Save button to save the new WMx Service configuration,
the new WMx Service appears in the table and the new WMx Service initiates, or
press the Undo button to cancel the changes.
To edit an existing WMx Service:
 Select the WMx Service to edit from the table and press the Edit button, then edit
the WMx Service properties as described above. When finished, press the Save
button to save any changes (confirmation prompts appear), or the Undo button to
cancel any changes.
To deactivate / activate an existing WMx Service:
At times you may wish to deactivate an WMx Service (stop communication between the
WMx devices and its database), then reactivate it at a later time. This operation is
needed if you decide to move the WMx Service to another computer.
 In the table, select the WMx Service to deactivate and press the Deactivate button.
The selected WMx Service is deactivated (but not removed from the WMx Services
table).
 Any WMx devices that were configured to communicate with this
WMx Service will no longer have their data saved in the SKF
The deactivated WMx Service still appears in the table, but when selected, the
Deactivate button changes to an Activate button indicating the WMx Service is not
currently operating. Press the Activate button to resume the WMx Service’s
communication operations.
To remove a WMx Service:
 In the table, select the WMx Service to remove and press the Remove button. The
selected WMx Service is deactivated and removed from the WMx Services table.
 Any WMx devices that were configured to communicate with this
WMx Service will no longer have their data saved in the SKF

Installation Manual
SMTP Settings
SMTP Settings
Figure 2 - 34.
The SMTP Settings Configuration Screen.
This screen allows you to configure the e-mail notification system.

Name – Enter the name of the SMTP server.
Server address – Enter the address of your outgoing SMTP mail server.
Port – Enter the SMTP port used by your mail client.
From – Enter the email address you wish for SKF @ptitude Analyst to use to send an
email.
User name – Enter the user name used to connect to the SMTP server.
User password – Enter the password associated with the selected user name.
Requires authentication - When enabled, you are required to log on to the SMTP
server.
User secure connection - When enabled, the Secure Sockets Layer (SSL) security
protocol is used when connecting to the SMTP server. When finished, press the Save
button to save the SMTP configuration.
 Click the Test button to verify that the specified SMTP settings are valid. If
successful, the Email List dialog displays, allowing you to enter one or more email
addresses to which to send a test email. If an error message displays, check your
settings and make any necessary changes, then click the Test button again.

Installation Manual
3
Installing SKF @ptitude Analyst Thin Client Transfer
SKF @ptitude Analyst Thin Client Transfer is a small application that deploys very easily
and facilitates data transfer to and from Microlog and MARLIN Data Acquisition Devices
(DADs), without using the SKF @ptitude Analyst interface.
 Thin Client Transfer is not for use with Microlog Inspector devices.
Thin Client Transfer has two modes of communication:
Direct communicate with an SKF @ptitude Analyst database – This method provides
database communication that allows data to be uploaded to and downloaded from a
Microlog or MARLIN DAD from a remote client computer, bypassing the SKF @ptitude
Analyst application interface. This is done by directly connecting with the SKF @ptitude
Analyst database via an optimized connection through the SKF @ptitude Analyst
Transaction Server.
This method requires a connection to the Transaction Server at all locations where Thin
Client Transfer is installed.
File Transfer – This method allows users to transfer data via a file, without requiring a
direct connection between the Microlog or MARLIN DAD and the computer hosting SKF
@ptitude Analyst. This is primarily used when data collection occurs at a remote
location without an SKF @ptitude Analyst installation.
This method requires a connection to the Transaction Server to upload / download to
the SKF @ptitude Analyst installation, but does not require a Transaction Server
connection to communicate with the DADs.
A Note About Thin Client Transfer Licenses
Thin Client Transfer File CMSW7320 (file transfer mode) and Thin Client Transfer
Direct CMSW7321 (direct database communication mode) products are licensed
separately. Each license specifies the number of remote computers that may upload
data to @ptitude Analyst. With file based transfer mode, once you upload data from
your DAD, one of the licenses for that upload method is permanently tied to the
computer that was used to generate the upload file. With Direct connect, a license is
used for each concurrent user logged into TCT. When one user logs off, the license
becomes available for the next user.
Licenses are validated during connection to the Transaction Server (in the case of TCT
Direct) or processing of the upload file (in the case of TCT File). You do not need to enter
license keys at each location where Thin Client Transfer is installed; rather, licenses are
entered using the License Key Manager on the computer hosting the Transaction
Server.
If you have one license key file on your network that is shared by multiple installations
of SKF @ptitude Analyst, you may enter the Thin Client Transfer licenses in the License
Key Manager at any SKF @ptitude Analyst installation. If each installation uses its own
license file, you must enter the keys on the computer hosting the Transaction Server

Installation Manual
Installing Thin Client Transfer
referenced by Thin Client Transfer, as specified during the Thin Client Transfer
installation procedure.
 By default, license key files are stored on the local computer. If
you would like to place a copy of the license key file on the
network where it can be shared by multiple installations, use the
File / Use File… menu option in the License Key Manager at each
SKF @ptitude Analyst installation.
 If the Thin Client Transfer license key was entered during
installation of the Transaction Server host, no further action is
required. If it was not already entered, you may enter the key at
any time using the License Key Manager.
Important: Before installing Thin Client Transfer, verify that your computer meets
the minimum system requirements. Refer to the SKF @ptitude Analyst Installation
Manual (P/N 32312400).
Download Thin Client Transfer from the SKF website and then install it, as described
below.
 You must be logged in as an administrator on the computer to be
able to install Thin Client Transfer.
To launch the Thin Client Transfer install program:
 From skf.com, click the link to SKF @ptitude Analyst Thin Client Transfer
downloads.
 Download the Thin Client Transfer program.
 Double-click the ThinClientV9.exe file.
 The installer prompts you to select the language for the installation. From the drop
down menu, choose English (United States), French (Standard), German,
Portuguese (Brazilian), Russian, Spanish, Swedish or Thai. Then, click OK.
 The Welcome page displays.
 Click Next to continue to the License Agreement screen.
 Carefully read the license agreement. If you do not agree with the terms of the
license agreement, click Cancel to abort the installation. If you agree with the
terms, select I accept the terms of the license agreement and click Next to
proceed to the Choose Destination Location screen.
 If SKF @ptitude Analyst is already installed on this computer, the
previously selected destination location is automatically used and
this screen does not appear.
The default destination location displays.

Installation Manual
 Accept the default location (recommended), or use the Browse button to select a
new location, and click the Next command button. The Transaction Server Name
screen displays.
You must specify whether this computer requires a connection to the transaction
server, and if so, the Transaction Server to use with this Thin Client Transfer
installation.
This computer will connect to the Transaction Server – Communication between
SKF @ptitude Analyst and SKF @ptitude Thin Client Transfer is handled through the
Transaction Server. If this Thin Client Transfer installation will be used to communicate
with an SKF @ptitude Analyst database (i.e., upload to and download from the Analyst
hierarchy), you must specify the Transaction Server to use. Leave this check box
enabled and enter the Transaction Server information in the following fields. If this
Thin Client Transfer installation will only be used to communicate with the Microlog or
MARLIN at a remote location via file transfer (CMSW7320) and does not require a
connection to the SKF @ptitude Analyst database, unmark this check box and click Next.
Name – Enter the machine name or IP address of the computer where the Transaction
Server is installed.
Port – Enter the TCP Port used for communication with the Transaction Server host.
This must match the same port configured on the Transaction Server host.
 Make sure to allow this port by your firewall software installed on
the host computer.
 Click Next. The Ready to Install the Program screen displays.
 Click Install to begin the installation.
The Installing Thin Client Transfer screen displays progress. When the installation is
complete, the Stop and Read screen displays. This screen provides important
information concerning licensing your SKF @ptitude Thin Client Transfer installation.
 Read the information on the screen and click Next.
 For more information on licensing, refer to the A Note About Thin
Client Transfer Licenses heading, earlier in this section.
InstallShield Wizard Complete screen displays. This screen provides an option to
Show the readme file. The Readme file contains important information related to
your installation. It is recommended that you leave this option button selected.
 Click Finish to close the wizard and return to the main installation menu.
 Click the back arrow twice to return to the Select Language menu.
 Click exit to close the menu.

Installation Manual
4
Installation Maintenance
Once initial setup has been completed, you can re-launch the installation at any time to
modify, repair or remove SKF @ptitude Analyst from your computer.
To launch the maintenance program:
 Return to the SKF website, Analyst download page and download the appropriate
(32/64 bit) Setup.exe. (Or, run the Setup.exe originally downloaded if you know its
location on the computer.)
 You are prompted to select the desired language from the drop down list.
 The InstallShield Wizard opens, allowing you to modify, repair or remove SKF
@Analyst 9.
Figure 4 - 1.
The InstallShield Wizard Welcome Screen for Maintenance.
 Click Next to continue to the Program Maintenance screen.

Installation Manual
Removing your Installation
Figure 4 - 2.
The Program Maintenance Screen.
You can select Modify to change the way program features are installed. Select Repair
to fix installation errors in the program. Or, select Remove to remove SKF @ptitude
Analyst 9. See below for more details on removing your installation.
 Select Remove on the Program Maintenance screen.

 Click Next. The Remove the Program screen displays.
In some cases, a message displays that an older version of the software was detected
and the setup aborts. If this occurs, access Add or Remove Programs from the
Windows Control Panel.

Installation Manual
Figure 4 - 3.
The Remove the Program Screen.
 Click Remove to uninstall SKF @ptitude Analyst, including all installed add-on
applications. Note: The action begins immediately; there is no additional message
asking for confirmation.
 You must first stop and deactivate all SKF @ptitude IMx / WMx /
Microlog Inspector services associated with this installation before
you can remove SKF @ptitude Analyst. Reference the appropriate
SKF @ptitude service sections in Chapter 2, SKF @ptitude
Analyst Configuration Tool for details.
 Remove does not remove the @ptitude Analyst License Key
Manager, the @ptitude Home application, the Microsoft .NET 3.5 /
4.0 framework, or the database.

Installation Manual
When the uninstall is complete, the Uninstall Complete screen displays.

 Depending on your configuration, you may be asked to reboot
after uninstalling.
 Click Finish to close the wizard.

Installation Manual
5
Overview
The SKF @Aptitude Analyst License Key Manager is accessed via the Windows Start
menu’s All Programs / SKF @ptitude Monitoring Suite / Admin Tools / License Key
Manager option. Enter each of the license keys provided by SKF customer service with
your purchase.
Figure 5 - 1.
The SKF @ptitude Analyst License Key Manager Program.
SKF @ptitude Analyst uses license keys to:

 scale the application’s features scope;
 enable concurrent use of the total number of licenses acquired by the end user;
 store the application instance serial number;
 view the application’s expiration time, where applicable.

Installation Manual
Overview
Upon startup, the SKF @ptitude Analyst core application determines the specific
functionality to which it is licensed based on the configured license key and presents
itself as one of the following four core applications:
 SKF @ptitude Analyst for SKF Microlog Analyzer (supports Microlog Analyzer only)
 SKF @ptitude Inspector (supports MARLIN and Microlog Inspector only)
 SKF @ptitude Analyst for Multilog On-line Systems (supports CMU and TMU only)
 SKF @ptitude Analyst (supports Microlog Analyzer, Microlog Inspector, MARLIN,
CMU, TMU, LMU, MIM, IMx, and DMx)
In addition to the core functionality, end users may obtain licenses for one or more add-
ons, which further extend the features of the installed software. Licenses are provided
to activate the individual add-ons that have been purchased.
Licenses are also used to grant concurrent use of the software in a network
environment.
Options on this screen include:
New License Key – Used to add a new key. (Refer to Operation of the License Key
Manager, later in this section, for details.)
Key Summary list - Displays information about configured license keys:
Product Number – The SKF model number that identifies the product
associated with the license key.
Key – The unique license key number that enables the associated product.
Valid – Indicates whether the license key is valid. (This column is only used
when importing a license key file. You will not be able to directly add an invalid
key. Refer to Operation of the License Key Manager below for details.)
Version – The software version covered by the license key.
Licenses – The number of users covered by the license key.
Expiration - Some features can be activated on a trial basis to allow you the
opportunity to use the feature before making the decision to purchase. In this
situation, the feature is activated for a specified time period. The expiration
date displays here. Upon making a purchase, a new license is provided without
the time restriction.
Serial - The serial number that uniquely identifies your purchase summary. (If
you ever require technical or sales support, having your serial number will
greatly speed the process.)
Comment – Allows the user to enter a comment about each license key in the license
manager file. Click the Set button to save your comment.
Description - Provides information about the application associated with the key
highlighted in the Key Summary list.
Delete – Deletes the key currently highlighted in the Key Summary list.
Messages - Shows the output of activities, including error messages.

Installation Manual
Overview
Copy - Copy the license keys and messages to the clipboard, which can then easily be
pasted into other applications, such as Microsoft Word or an e-mail.
Commonly Asked Questions

The following section lists a number of commonly asked questions related to license
keys in SKF @ptitude Analyst. Operation and use of the License Key Manager (LKM) is
described after this section.
Q. Where are the product license keys stored?
A. All product license keys are maintained in a license key file. License key files are
indicated by the filename extension “.alf” This file may be located on the end
user’s PC or on a shared network drive. It is possible to make backup copies of
a license key file. Only one license key file is active at any given time.
 If license key file is on a shared network drive, this location must
be accessible by all clients.
Q. How do I obtain a license key?
A. Product license keys may be distributed as part of an email. When an SKF
@ptitude Analyst product is purchased, SKF sends a support package to the
end user. As part of the support package, a license key letter is included which
lists all applicable license keys. If, by accident, the support package did not
include this license key letter, or the letter was misplaced, one may obtain a
copy of this from the designated Customer Service representative.
Q. How do I manage license keys?
A. During first time installation, as well as additional purchases of other software
modules later on, one must update the license key file to enable the purchased
items. The SKF @ptitude Analyst License Key Manager is the primary method
for maintaining the license key file. With it, you can add and remove license
keys, either one at the time or by importing an entire block of license keys from
a file. Through the LKM, one can quickly get an overview of the active license
keys and the entitlements for which they allow.
Q. How is the application’s serial number used?
A. Every purchase of SKF @ptitude Analyst is assigned a serial number. If a
purchase involves a multi client license, all individual installations within that
multi client license have the same serial number. The serial number allows SKF
to properly manage your service and upgrade entitlements, such as Product
Support Plans and maintenance releases. End users can view their
application’s serial number using the LKM.
Add-Ons that are enabled as part of a purchase acquire the same serial
number as the core application.
Customers may purchase more than one core application, or purchase
different core applications, each with its own serial number. For example, SKF
@ptitude Analyst for SKF Microlog Analyzer only may be purchased for two
different plants. Both will have their own individual serial number.
Alternatively, a single site may have purchased SKF @ptitude Analyst 10 multi

Installation Manual
Overview
client licenses and SKF @ptitude Inspector 5 multi client licenses. Again, each
will have a separate serial number, and will be placed in separate .alf files.
Q. How does the product license key expiration date affect my installation?
A. Product license keys may have an embedded expiration date. The expiration
date gives a user the ability to operate an SKF @ptitude Analyst application for
a limited period of time. It is, in essence, a temporary license. Using the LKM,
one may determine the specific expiration date for a given license key. SKF
@ptitude Analyst applications that are enabled under a temporary license may
show a warning message upon startup, or show the expiration date in the main
window’s title. The expiration of the application is enforced at the point of
startup.
Temporarily licensed applications operate identically to permanently licensed
applications; however, all functionality is lost after the expiration date. To
restore functionality, please contact your sales or customer representative. Any
acquired and stored data will be restored when the expired license key is
replaced by either a new temporary or permanent license.
SKF @ptitude Analyst products may be separated into a) the core application,
b) add-ons, and c) supporting applications. Add-ons extend the functionality of
the main application and entirely integrate into the main application’s menu
and help system. Both core application and Add-on functions require an
appropriate product license key. Both may have an expiration date, although
the most common situation will be for the core application to be licensed
permanently and the Add-On to have a temporary license. When the Add-On’s
temporary license expires, its functionality and features are removed from the
main menus. Data acquired with and/or associated with the Add-On remains
part of the database and is not lost. Supporting applications provide added
functionality, but reside outside the core application; they require their own key
and serial number.
Q. Do I need a new product license key when updating to a newer major
version of the application I currently use?
A. Yes. Product license keys enable a specific application functionality and
maintenance version. Please contact your sales representative with any
questions.
Q. I received a new product license key. How do I validate that it entitles me
to the functionality I purchased?
A. The simplest way to verify the entitlements of a product license key is to add
the key to the current license file using the LKM. The LKM shows the specific
entitlements, such as number of application clients, serial number, expiration
date, etc.
Q. How do I upgrade the number of users for my SKF @ptitude Analyst
installation?
A. You will need to purchase the upgrade for the desired number of users. After
purchase, SKF will extend a new product license key to you, which replaces
your existing product license key for the application you upgraded. For
example, assume that you are currently licensed to run five concurrent users

Installation Manual
Overview
for SKF @ptitude Analyst. The existing license key file holds a product license
key, which enables SKF @ptitude Analyst for these five application clients. Upon
receipt of the new product license key, you should remove the current license
key and add the new license key with the upgraded number of users.
Q. Where is the reference to the product license key file?
A. To make sure that all appropriate @ptitude applications operate on and can
refer to the same license key file, the path to this license key file is stored in the
client PC’s LicenseMngr.exe.config file.
Q. How do I share the product license key file with two or more users?
A. Follow these steps:
1. Ensure that all applicable users have read access to a common drive.
2. Start LKM on one of the client PCs that is appropriately licensed.
3. Select File / Save As… to store the product license key file on the common
drive in a location accessible by all other client PCs.
4. For each subsequent client PC, start the LKM and select File / Use File…
to select the product license key file created in step 3.
As an alternative to step 4, you may also modify the registry to have the
LicenseFile entry point to the commonly located file directly. Note that this
works only if all client PCs access the common network drive by the exact same
path, including drive letter.
Q. How do I limit end user access to the product license key file to minimize
tampering?
A. SKF @ptitude Analyst applications always require read access to the product
license key file. Therefore, setting the access rights to read only and
additionally removing the LKM from the end user’s PC should be sufficient to
avoid tampering.
Operation of the License Key Manager

The License Key Manager provides the ability to enter license keys manually, or to use
an existing license key file.
To manually enter a key:
 Enter the license key in the License Key field and click Add. If the license key is
valid, it appears in the Key Summary list. (If the key is not valid, you are informed
in the Messages area of this screen.)
 The LKM reviews new license keys against its list of already
entered license keys. If a license key is entered with greater
capabilities than the already entered license key, the latter will be
replaced. For example, if a license key exists that licenses SKF
@ptitude Analyst V4.1 for 5 users and a new license key is
entered that licenses that same SKF @ptitude Analyst V4.1 but
now for 10 users, the existing license key on file is replaced with
the license key having greater capabilities.

Installation Manual
Overview
To import a license key file:

 If you have been provided with a license key file, select File / Import from the
menu. A Windows Open dialog displays.
 Locate the license file and click Open. Any license keys in the file that have not
already been entered are appended to the Key Summary list.
 By default, license files are named LicFile.alf.
To switch between product license key files:
By default license key files are stored on the local computer. If you would like to place a
copy of the license key file on the network where it can be shared by multiple
installations, you can switch to the network license key file. Additionally, there may be
circumstances that require you to keep two license key files for use at different times.
 The LKM operates only one license key file at the time.
 To switch between two files, select File / Use File…
Important
Carefully review the end user license agreement before proceeding. It is a violation
of your agreement to share a license key file with more installations than you
purchased.
 A message appears warning you that the selected license file will be used by all SKF
@ptitude Analyst applications and asking you whether you would like to proceed.
Select Yes to continue to a Windows Open dialog where you can select the license
file.
 If you have manually entered license keys at this screen prior to
selecting a license key file, keys that are not in the selected license
key file will be overwritten and the associated features will cease
functioning.
To change the location of the product license key file:
 Select File / Save As from the menu. A Windows Save As dialog appears.
 Select a new location and enter a name for the file.
 Click Save to save the license key file to the specified location.
 This feature can also be used to save the configured license keys
to a file to facilitate installation on other computers
.

Installation Manual
Appendix A
SKF @ptitude Analyst System Connection Diagram
SKF @ptitude Analyst A-1

Installation Manual
Transaction Server 2-16
Index
I
A IMx service 2-24
Analyst software download 1-20 adding 2-25
Analyst software install 1-20 deactivate 2-26
editing 2-26
remove 2-26
B
install database manager, Oracle 1-19
backup 1-22 install database manager, SQL Server 1-18
installation
C maintenance 4-2
modify, repair or remove 4-1
client readme 1-25
Transaction Server 2-16
L
D
license key
database expiration 5-4
change 2-10 obtaining 5-3
configuration 2-1 sharing 5-5
connect name 2-7 upgrade 5-4
connection information 1-6, 1-17 License Key Manager 2-23
considerations 1-6 import key file 5-6
demo 2-1 switch key file 5-6
run SQL script 2-13
save 2-10
M
specifying database tool 2-2
supported 1-6, 1-17 maintenance 4-2
type 2-7 Microlog Inspector service 2-30
update 2-12 Microlog service 2-30
user management 2-11 adding 2-30
database manager 1-6, 1-17 deactivate 2-31
demo database 2-1 editing 2-31
download remove 2-32
database manager 1-17 Microsoft .NET Framework 1-21
download prerequisite applications 1-16 Microsoft SQL Server: See SQL Server
monitor recovery configuration 2-21
E
N
email list 2-25, 2-31, 2-36
network considerations 1-8
G
O
general configuration 2-14
Oracle
H migrating data 1-13
password 2-9
HMI configuration 2-15 supported versions 1-6, 1-17
host upgrade 1-13
SKF @ptitude Analyst Index - 1

Installation Manual
P
prerequisite applications 1-16
R
readme 1-25
remove installation 4-2
run SQL script 2-13
S
SMTP settings 2-25, 2-31, 2-37, 2-38
SQL Server
migrating data 1-13
password 2-9
supported versions 1-6, 1-17
upgrade 1-13
support, technical 1-6
supported databases 1-6
T
technical support 1-6
Thin Client Transfer
configuration 2-22
Thin Client Transfer installation 3-2
Transaction Server
considerations 1-8
transaction service configuration 2-16
U
uninstall 4-2
upgrade 1-12
user manual 1-26
W
Windows 4.5 installer 1-22
Windows 7, 8.1 or 10 1-9
WMx Conversion Utility 2-36
WMx database conversion 2-36
WMx service
deactivate 2-37
editing 2-37
remove 2-37
WMx service 2-35
adding 2-36
Index - 2 SKF @ptitude Analyst

Installation Manual

SKF Install Manual

Uploaded by

Document Informationclick to expand document informationSKF install manual

Document Informationclick to expand document information

Copyright:

Available Formats

SKF Install Manual

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SKF Install Manual

Uploaded by

Copyright:

Available Formats

SKF @ptitude Analyst Download and

Part No. 32367100-EN

Copyright  2017 by SKF USA Inc.

Patents: US 4,768,380 • US 5,633,811 • US 5,679,900 • US 5,845,230 • US 5,852,351 •

Product Support – Contact Information

General Product Information

Technical Support Group

Tell us how we’re doing!

(a) Limitations and Exclusions. IN NO (a) Term. This Agreement shall

CM-F0176 (Revision F, January 2011)

SKF @ptitude Analyst Configuration Tool 2

SKF @ptitude Analyst TOC - 1

SKF @ptitude Analyst License Key Manager 5

SKF @ptitude Analyst System Connection

TOC - 2 SKF @ptitude Analyst

Important - How to Facilitate a Quick, Easy Product Installation!

Varying Procedures for First Time Installations, Application

SKF @ptitude Analyst 1-1

A Note about the Download Installation Image

A Note about License Keys

What to Install First

1-2 SKF @ptitude Analyst

 Please take a moment to register your product at www.skf.com/cm/register to

Configuration Minimum requirements Recommended requirements

Operating System (Note 1) Windows 7 Windows 7,

Disk space available for 10 GB 30 GB or more

Database Oracle Version 11g Version 12c

SKF @ptitude Analyst 1-3

Network configuration – Database server

Configuration Minimum requirements Recommended requirements

Operating System (Note 1) Windows Server 2008 Windows Server 2008

Processor (Note 2) Intel 2.0 GHz, 32 or 64-bit, Intel Quad-Core I7 processor

Quantity of hard drives 3 5

Disk space available (Note 10 GB 30 GB or more

Database Oracle Version 11g Version 12c

Network configuration – Network Client

Configuration Minimum requirements Recommended requirements

Disk space available for 10 GB 30 GB or more

Database Oracle Version 11g Version 12c

1-4 SKF @ptitude Analyst

Network configuration – Application server

Configuration Minimum requirements Recommended requirements

Processor Intel 2.0 GHz, 32 or 64-bit, Intel Quad-Core I7 processor

Disk space available 10 GB 30 GB or more

Note 1: Windows 7 (32 or 64-bit) Professional or Ultimate Editions, (please see

SKF @ptitude Analyst 1-5

Planning the Installation

1-6 SKF @ptitude Analyst

SKF @ptitude Analyst 1-7

Transaction Server Service Considerations

1-8 SKF @ptitude Analyst

number) for the Transaction Server host as it is needed when configuring

Windows Operating System Compatibility

SKF @ptitude Analyst 1-9

Application / Utility Win 7, 8.1 Win 7, 8.1 or

1 - 10 SKF @ptitude Analyst

Data Acquisition Devices (DADs) Minimum Win 7, 8.1 Comment

SKF Multilog DMx 7.2 No