Highlighted
Absent Member.
Absent Member.
249 views

SM Tip: how to upgrade SM9.34PD to SM9.40codeless

There are two kinds of SM9.40. The SM9.40 classic which has no Proccess Designer and the SM9.40 codeless which has built-in PD. The following steps explain how to upgrade SM9.34PD to SM9.40codeless under SM OOB system.
Even by tailoring/cutomization, these steps can  be used

 

1. System
 - Windows 2008 x64 EE R2(en)
 - IP address: 10.10.10.10
 - FQDN: sm940.domain.com
 - Database: Oracle 11gR2

2. As-Is
 - sm9.34.0032 app
 - sm9.34.0032 rte
 - sm9.34.0032 eclipse
 - sm9.34.0032 web
 - sm9.34.0072 src
 - sm9.34.0032 km
 - sm9.34.0021 mobility
 - PD4-9.30.3
 
3. To-Be
 - sm9.40.0015 app(codeless)
 - sm9.40.0015 rte
 - sm9.40.0015 eclipse
 - sm9.40.0015 web
 - sm9.40.0015 src
 - sm9.40.0015 km
 - sm9.40.0015 mobility

4. references
 - HP Service Manager Application Upgrade Guide, SM930PD_SM940_upgrade.pdf, total 89 pages
   ( from SM940#GA-Media\Documentation\Install_Upgrade_Doc_Center\Content\PDF\SM930PD_SM940_upgrade.pdf )
 - HP Service Manager Process Designer Migration Guide, total 127 pages
   ( from 
https://hpln.hp.com/node/124/contentfiles )
  
5. pretask-1
 1) HP Service Manager Application Upgrade Guide, SM930PD_SM940_upgrade.pdf
   -> page 6, if lang pack is installed, upgrade utility shows error and ends.
      ==> "The Upgrade Utility does not support multi-languages."
          in this case, needs to use "Service Manager 9.40 Applications Upgrade Utility for Multi-Languages", 
 2) login to sm 9.34 server via sm9.34 win client
 3) purge existing upgrade files (manual page 18)
  - *aapm.upgrade.purge
  > check, "I'm done, and I want to remove the upgrade files completely"

6. install 9.40.0015 rte/win client
 1) mount 9.40 installation media
 2) ClickMe.html
 3) install, HP Service Manager Server for Windows
   -> launch configuration manager but don't click "upload data"
   - if db is not supported version, add this line in sm.ini
     allowunsupporteddbversion:1  
   - apply license on sm9.40
 4) install, HP Service Manager Windows Client

7. pretask-2 for apply application 9.40
 1) change configuration files(manual page 20)
  - modify sm.cfg
   # sm system.start  // stop bg process

   sm  // launch only one servlet
   sm -sync        
   // comment out all other parameter except for two ( one for a servlet, one for -sync )
 
  - modify sm.ini
   ir_disable:1
   sessiontimeout:1200
   shared_memory:150000000
   heartbeatinterval:120
 
  ## sm.ini (full) ###
  shared_memory:150000000
  log:../logs/sm.log
  system:13080
  httpPort:13080
  sslConnector:0
  httpsPort:13443
  sqldictionary:oracle10
  [oracle10]
  sqldb:ora11
  sqllogin:sm/sm
  sqllibrary:sqoracle.oci10.DLL
  plugin0:kmplugin.dll
 
  KMSearchEngineClass:com.hp.ov.sm.server.plugins.knowledgemanagement.solr.KMSolrSearch
 
  allowunsupporteddbversion:1
 
  sessiontimeout:1200
  ir_disable:1
  heartbeatinterval:120  
 
 2) start SM

8. apply sm9.40 application
 # running the upgrade utility(manual page 22)
 1) step1. load the application upgrade files
 ---------------------------------------------
   load preupg.bin , transfer.bin
   - make a folder,
     C:\Program Files (x86)\HP\Service Manager 9.40\Server\upgrade
   - copy file from 9.40 media to newly created folder(upgrade)
     from {9.40 media}\Utilities\Application_Upgrade_EN-9.40.zip
     to   C:\Program Files (x86)\HP\Service Manager 9.40\Server\upgrade
   - uncompress Application_Upgrade_EN-9.40.zip
   -> finally, this folder and files are created
   C:\Program Files (x86)\HP\Service Manager 9.40\Server\upgrade\Application_Upgrade_EN-9.40\AppUpgrade\application-9.40.0015-UP\English_app_upgrade\SM7.10-9.40.0015_EN

   - set sm win client : uncheck for 'Client side load/unload'
 
   - load preupg.bin using service manager database manager
    > db > Import/Load
      C:\Program Files (x86)\HP\Service Manager 9.40\Server\upgrade\Application_Upgrade_EN-9.40\AppUpgrade\application-9.40.0015-UP\English_app_upgrade\SM7.10-9.40.0015_EN\preupg.bin
     
   - load transfer.bin using upgrade utility
    > smupgrade  
    > goto  Upgrade Utility > Load Transfer
      . What is the fully qualified path to the transfer.bin file ? ( don't include filename, transfer.bin )
      C:\Program Files (x86)\HP\Service Manager 9.40\Server\upgrade\Application_Upgrade_EN-9.40\AppUpgrade\application-9.40.0015-UP\English_app_upgrade\SM7.10-9.40.0015_EN\
     >> click next
      Loading transfer.bin...
      ... 5 min later ...
      Transfer files loaded
 
   - logout and login again
  
 2) step2. run the SQL compare utility
 -------------------------------------
  - run SQL Compare utility,
   > smupgrade in command line
   > click Run SQL Compare Utility
    >> Enter the full path to the location of the upgdbdct.dta file:
    C:\Program Files (x86)\HP\Service Manager 9.40\Server\upgrade\Application_Upgrade_EN-9.40\AppUpgrade\application-9.40.0015-UP\English_app_upgrade\SM7.10-9.40.0015_EN\
    >> click load button
    No dbdict named "AutomationTaskUpdate" exists in this system.  Dbdict will be added by upgrade.
    ...
    Process Complete.  Please check for any additional messages.
   
  - view the SQL compare results
   > smupgrade
   > view SQL Field Compare Results
   > view SQL Unique Key Compare Results
   
  - add new fields if required // page 28 of SM930PD_SM940_upgrade.pdf
 
  - determine the correct structure if required // page 28 of SM930PD_SM940_upgrade.pdf

  - process the nvarchar SQL type if required // page 29 of SM930PD_SM940_upgrade.pdf
 
 
 3) step3. run the upgrade utility
 ----------------------------------
 phase 1. questions
   > smupgrade > upgrade utility > service pack
   >> Upgrade Processing > Apply an Upgrade
     . application version upgrading from: 9.34.0032 PDCP4
   >> click Next
     --> if langpack has installed then, stop with message "The Upgrade Utility does not support multi-languages."
        ( there is no upgrade pack for lang-pack installed system, at the moment, Mar 6th, 2015)
   >> Are you going to use this system to create a custom upgrade for another system ?  
     --> Yes
     --> click Next
   >> What is the fully qualified path to the Upgrade Utility files ?
     --> C:\Program Files (x86)\HP\Service Manager 9.40\Server\upgrade\Application_Upgrade_EN-9.40\AppUpgrade\application-9.40.0015-UP\English_app_upgrade\SM7.10-9.40.0015_EN\
     --> click Next
   >> When HP Service Manager Upgrade doesn't recognize an object it should:
     -(*) Install HP Service Manager's version of the object alongside your own. // choose
     -    Replace your version of the object with HP Service Manager's version of the object. // this option is for applying custom upgrade
   >> Do you want to enable automatic merge and which version will be used as the bsae version ?
     Your current installed version is     9.34.0032 PDCP4
     check : Enable
     Base Version: 9.3PD

     page 30 of SM930PD_SM940_upgrade.pdf
     "The Base Version you select here will be considered as a clean version on which all
      changes are based. The earlier the version is, the less the chance your tailoring will be
      discarded. However, the earlier the version is, the less likely the utility will successfully
      merge objects. Typically, it is safe to keep the default value, which is set to the earliest
      version that your applications were previously upgraded from."
      --> click Next
    >> Do you want to force the replacement of the objects ?
      check : Replace RAD   // because of no RAD tailoring
      --> click Next
    >> HP Service Manager Upgrade is now ready to begin the data upgrade.
      --> click Next
      "This Application will upgrade your system to Version : 9.40.0015 built on :
      12/08/14 09:53:11. Proceed?"
      --> click Yes
       21:18 -> ...
     
 phase 2. updates dbdicts
 phase 3. updates application data
 
      ... -> 21:45 , took about 30 min
        UPGRADE IS COMPLETE.
        Message Box,
        "APPLYING OUT-OF-BOX UPGRADE IS COMPLETE. You will be automatically
         logged out after clicking the OK buton.
         Next steps:
         1. Fix all errors in except.log, and verify your fixes.
         2. Resolve all of conflicts in upgraderesults table, and verify your resolution.
         3. Create custom upgrade package.
         4. Apply custom upgrade package to another copy of production system.
        "
     
      
     C:\Program Files (x86)\HP\Service Manager 9.40\Server\upgrade\Application_Upgrade_EN-9.40\AppUpgrade\application-9.40.0015-UP\English_app_upgrade\SM7.10-9.40.0015_EN
       upgrade.log
       detail.log
       except.log
             
   - upgrade.log  // filter ****
      2015-03-06 17:50:15 **** Start Phase [Load Transfer] ****
      2015-03-06 17:52:14 **** Finish Phase [Load Transfer] ****
      2015-03-06 18:02:32 **** Start Phase [Pre Upgrade Action Check] ****
      2015-03-06 18:02:32 **** Finish Phase [Pre Upgrade Action Check] ****
      2015-03-06 18:02:32 **** Start Phase [Pre Upgrade Action Update] ****
      2015-03-06 20:58:59 **** Finish Phase [Pre Upgrade Action Update] ****
      2015-03-06 20:59:02 **** Start Phase [Pre Upgrade Action Purge] ****
      2015-03-06 20:59:04 **** Finish Phase [Pre Upgrade Action Purge] ****
      2015-03-06 20:59:04 **** Start Phase [Pre Upgrade Action] ****
      2015-03-06 20:59:05 **** Finish Phase [Pre Upgrade Action] ****
      2015-03-06 20:59:05 **** Start Phase [Load Upgrade File] ****
      2015-03-06 21:00:40 **** Finish Phase [Load Upgrade File] ****
      2015-03-06 21:00:40 **** Start Phase [Upgrade Dbdicts] ****
      2015-03-06 21:03:13 **** Finish Phase [Upgrade Dbdicts] ****
      2015-03-06 21:03:13 **** Start Phase [Load Upgrading Data] ****
      2015-03-06 21:08:46 **** Finish Phase [Load Upgrading Data] ****
      2015-03-06 21:08:46 **** Start Phase [Upgrade Data] ****
      2015-03-06 21:20:49 **** Finish Phase [Upgrade Data] ****
      2015-03-06 21:20:49 **** Start Phase [Post Upgrade Action] ****
      2015-03-06 21:23:04 **** Finish Phase [Post Upgrade Action] ****
      2015-03-06 21:23:04 **** Start Phase [Post Upgrade Action Prior to SM940] ****
      2015-03-06 21:24:08 **** Finish Phase [Post Upgrade Action Prior to SM940] ****
      2015-03-06 21:24:08 **** Start Phase [Post Upgrade Action Auto Merge] ****
      2015-03-06 21:24:17 **** Finish Phase [Post Upgrade Action Auto Merge] ****
      2015-03-06 21:24:17 **** Start Phase [Post Upgrade Action Purge] ****
      2015-03-06 21:25:00 **** Finish Phase [Post Upgrade Action Purge] ****
      2015-03-06 21:25:00 **** Start Phase [Post Upgrade Action Update] ****
      2015-03-06 21:25:13 **** Finish Phase [Post Upgrade Action Update] ****
      2015-03-06 21:25:13 **** Start Phase [Post Upgrade Action Notification] ****
      2015-03-06 21:28:14 **** Finish Phase [Post Upgrade Action Notification] ****
      2015-03-06 21:28:14 **** Start Phase [Post Upgrade Action Restore] ****
      2015-03-06 21:28:14 **** Finish Phase [Post Upgrade Action Restore] ****
   
   - restart SM --> sm.log is not like common status
   - reboot SM's box -> now sm.log looks good and successfully logged in via eclipse client.
   
    
 4) fix issue after upgrading
  - verify application, db > scversion > search >
     Application version  9.40.0015
     RTE version          9.40.0015
     Application build date  12/08/14 05:00:00
     Content Releases Installed: Process_Designer


9. Resolving exceptions and conflicts
 0) view "Upgrade results"
 -------------------------
  > smupgrade > UPGRADE UTILITY > View/Merge Upgrade Results
  - result=Added,          --> 11,107 --> no further action required
  - result=Already Current --> 23,168 --> no further action required
  - result=Auto Merged     --> 0
  - result=Error           --> 0
  - result=Forced          --> 0
  - result=Kept Customer   --> 2
      Object Type(Object Name)
      kmknowledgebase(Incident_Library)
      kmknowledgebase(Interation_Library)
      --> no further action required
  - result=Kept Customer Non-OOB --> 6
      kmknowledgebase(KnwonError_Library_disabled_by_PDHD)
      Object(probsummary_disabled_by_PDHD)
      kmknowledgebase(Problem_Library_disabled_by_PDHD)
      Object(incident_disabled_by_PDHD)
      activityactions(Save Activities_disabled_by_PDHDincidents)
      Object(rootcause_disabled_by_PDHD)
      --> no further action required
  - result=Merged          --> 60
      --> Test these objects, and change their result to 'Reconciled' when satisfied.
      --> in this upgrade-testing, let it be,"Merged"
  - result=Previously Reconciled --> 1
      kmknowledgebase(Knowledge_Library)
      --> click "Merge" --> Copy all from Left to Right
      --> click "Mark as Reconciled"
  - result=Reconciled      --> 1
      kmknowledgebase(Knowledge_Library)
      --> no more action
  - result=Renamed         --> 11
    Process(kmquery.submitsearch)
    globallists(Resolution Code)
    globallists(Startup Lists)
    link(incidents)
    link(probsummary)
    link(rootcause)
    menu(ADMIN)
    menu(CC PD)
    menu(HOME)
    menu(IM GEN)
    menu(PM GEN)
   --> it should be one of three a. keep old version b. keep new version c. merge
       it is upgrade from SM OOB, so do "keep new version"
      --> click "Merge" --> Click "Three way compare"
      --> eye check     --> Click "Copy all from Left to Right"
      --> click "Save" -->  click "Mark as Reconciled"
  - result=Upgraded       --> 4,845
     --> no further action required
  - result=Replaced        --> 0

 
 Step 1. Resolve exceptions on page 38
 -------------------------------------
 - except.log and action
2015-03-06 17:55:30 dbdict:Workflow, field:description, SQL type is VARCHAR2(255) -- expected to be:BLOB
 --> change SQL type to BLOB by using dbdict utility
      SQL Type : VARCHAR2(255) -> BLOB
      SQL RC   : false -> true
 
2015-03-06 17:55:32 dbdict:cm3r, field:assets, type:array, SQL Table is EMPTY -- expected to be: a3
2015-03-06 17:55:32 dbdict:cm3r, field:assets, type:character, SQL type is CLOB -- expected to be: VARCHAR2(200), SQL Table is m1 -- expected to be: a3
 --> change mapping , assets(CLOB m1) --> assets(VARCHAR2, a3)
     a. add SQL Tables
      a3 CM3RA3 oracle10
     b. add Keys
      nulls & duplicates, assets
     c. change mapping
         assets array ,   sql table: null -> a3
         assets character,  SQL Type: CLOB -> VARCHAR2(200), SQL Table:m1 -> a3

2015-03-06 17:55:43 dbdict:operator, field:assignment.groups, SQL type is VARCHAR2(200) -- expected to be:CLOB
2015-03-06 17:55:43 dbdict:operator, field:secRole, SQL type is VARCHAR2(200) -- expected to be:CLOB
 --> ignore this. no further action is necessary.
 
2015-03-06 17:55:49 dbdict:svcItemCount, field:access.filter, SQL type is RAW(255) -- expected to be:CLOB
 --> change mapping, access.filter : RAW(255) -> CLOB
      SQL Type: RAW(255) -> CLOB
      SQL RC  : True -> False
     
2015-03-06 21:00:51 dbdict:Rule, field:tablename, SQL type is VARCHAR2(60) -- expected to be:CLOB
 --> ignore this. no further action is necessary.

2015-03-06 21:00:53 dbdict:Workflow, field:description, SQL type is VARCHAR2(255) -- expected to be:BLOB
 --> change SQL type to BLOB by using dbdict utility
      SQL Type : VARCHAR2(255) -> BLOB
      SQL RC   : false -> true
 
2015-03-06 21:01:04 dbdict:cm3r, field:assets, SQL type is CLOB -- expected to be:VARCHAR2(200)
 --> change mapping , assets(CLOB m1) --> assets(VARCHAR2, a3)
     a. add SQL Tables
      a3 CM3RA3 oracle10
     b. add Keys
      nulls & duplicates, assets
     c. change mapping
         assets array ,   sql table: null -> a3
         assets character,  SQL Type: CLOB -> VARCHAR2(200), SQL Table:m1 -> a3

2015-03-06 21:01:45 dbdict:operator, field:assignment.groups, SQL type is VARCHAR2(200) -- expected to be:CLOB
2015-03-06 21:01:45 dbdict:operator, field:secRole, SQL type is VARCHAR2(200) -- expected to be:CLOB
 --> ignore this. no further action is necessary.

2015-03-06 21:02:14 dbdict:svcItemCount, field:access.filter, SQL type is RAW(255) -- expected to be:CLOB
 --> change mapping, access.filter : RAW(255) -> CLOB
      SQL Type: RAW(255) -> CLOB
      SQL RC  : True -> False
 
  - Fixing the FolderRights delete field ( page 41 )
   -> no action required because my sm oob's FolderRights.delete is alerady varchar2(50)
 
  - Add new object record failure ( page 43 )
   -> no action required because of no error regarding in except.log and 'upgrade results, Result=Error'
  
  - Handle key change failure ( page 43 )
   -> no action required because of no error regarding in except.log and 'upgrade results, Result=Error'
 
  - Unexpected errors
   -> no action required because of no error regarding in except.log and 'upgrade results, Result=Error'
 
 
 Step 2. Resolve conflicts on page 45
 ------------------------------------
 - Standard conflict resolution process (page 45)
  > View/Merge Upgrade Results where status = "Renamed"
  option 1. use your customized object instead of the new object
  option 2. use the new object instead of your customized object
  option 3. merge the changes shipped with the new object into your customized object
  > After resolving each conflict, must mark the object as "Reconciled"

  - result=Renamed         --> 11
    Process(kmquery.submitsearch)
    globallists(Resolution Code)
    globallists(Startup Lists)
    link(incidents)
    link(probsummary)
    link(rootcause)
    menu(ADMIN)
    menu(CC PD)
    menu(HOME)
    menu(IM GEN)
    menu(PM GEN)
   --> it should be one of three a. keep old version b. keep new version c. merge
       it is upgrade from SM OOB, so do "keep new version"
      --> click "Merge" --> Click "Three way compare"
      --> eye check     --> Click "Copy all from Left to Right"
      --> click "Save" -->  click "Mark as Reconciled"
 
 - Display components ( page 48 )
  . Display RAD application ( RAD=display )
  . displayscreen
  . displayoption
  . displayevent
 
 - RAD applications ( page 49 )
 

 Step 3. Perform additional manual task on page 61
 -------------------------------------------------
  - *aapm.upgrade.purge
   > click "I'm done, and I want to remove the duplicate data prefixed by "NEW","PRE" and "OLD"
   -> Purge 12 duplicate upgrde records prefixed by NEW,PRE and OLD.
      "Finishe purging upgrade files"
 
 Step 4. Migrate Process Designer data on page 62
 ------------------------------------------------
   - reference : HP Service Manager Process Designer Migration Guide, 127 page
     SM940#GA\Documentation\Install_Upgrade_Doc_Center\Content\PDF"sm_pd_migration_guide.pdf"
  
   - do not execute PD Enablement. Instead, execute Migrate Data only.
    ( we are upgrading 9.34PD -> 9.40 codeless )
  
   - db > db> migrationSetting > Search >> 20 searched
    >> click "Migrate Data" button for all, 20 records
    
  # this time, I just did "Migrate Data", however,
   in actual system, customer needs to read whole PD migration document,
                     and then, list and follow up action plan.
                    
  
 Step 5. Return the sysetm to normal operation on page 62
 --------------------------------------------------------
  - sm.cfg
    sm system.start
  - restart SM
 
 Step 6. Test the system(functional testing) on page 63
 ------------------------------------------------------
 Step 7. Back up the system on page 63
 -------------------------------------
 
 - install sm9.40.0015 web
 - verify it with google chrome 41, ( IE 8 is not supported )


10. Creating and applying the custom upgrade
 - create folder for custom upgrade
   C:\Program Files (x86)\HP\Service Manager 9.40\Server\custom_upgrade
 - login to SM using eclipse client
  > smupgrade in command line
  >> UPGRADE UTILITY > SERVICE PACK
   --> click "Create an Upgrade
    -> click "Next"
    -> What is the name of this release ?
       sm940
       -> click "Next"
    -> Where do you want the upgrade files to be exported?
      C:\Program Files (x86)\HP\Service Manager 9.40\Server\custom_upgrade\
      -> click "Next"
    -> Which patch file should be used to build the upgrade ?
       SM94
       -> click "Next"
    -> Take which action ?
       Produce Signatures of Current System
       Build Upgrade Information
       Export this Release
       Build Transfer Set
   (*) Complete Upgrade Build (Recommended)
       -> click "Next"
    -> Filter out the objects which are not changed ?
       --> check for excluding unchanged object
       -> click "Next"
    -> HP Service Manager Upgrade Builder is now ready to build the upgrade.
       -> click "Next"
    -> Question, Warning, This process will destroy any existing upgrade definition on file. Proceed?
       -> click "Yes"
      12:04 -> 12:31 // took 27 min     
      
     C:\Program Files (x86)\HP\Service Manager 9.40\Server\custom_upgrade
     upgrade.log   
     detail.log
     transfer.log
    
     > upgrade.log // fileter ****
     2015-03-11 12:03:10 **** Start Phase [Pre Create Action Check] ****
     2015-03-11 12:03:10 **** Finish Phase [Pre Create Action Check] ****
     2015-03-11 12:04:01 **** Start Phase [Build Signatures] ****
     2015-03-11 12:09:50 **** Finish Phase [Build Signatures] ****
     2015-03-11 12:09:51 **** Start Phase [Build Distribution] ****
     2015-03-11 12:19:30 **** Finish Phase [Build Distribution] ****
     2015-03-11 12:19:30 **** Start Phase [Export Data] ****
     2015-03-11 12:31:05 **** Finish Phase [Export Data] ****
     2015-03-11 12:31:05 **** Start Phase [Transfer Data] ****
     2015-03-11 12:31:43 **** Finish Phase [Transfer Data] ****


11. install SRC 9.40.0015
 - reference : SRC interactive installation guide
 - configure tomcat
  . increase java initial/maximum memory pool : 1024M
  . add java options :
    -XX:MaxPermSize=128m
 - deploy src9.40 webtier
 - sm.ini
   webservices_sessiontimeout:1800
 - url:
  
http://localhost:8080/src-9.40   ( use google chrome which Adobe flash player is installed )


12. install sm9.40.0015 km
 - ClickMe.html
  > Installation > Knowledge Management > HP Service Manager Knowledge Management Search Engine for Windows
   -> kmsetup.exe
 - Choose Install set : Typical
 - installation folder : C:\Program Files\HP\Service Manager 9.40\SearchEngine
 - Tomcat port Selection
   > tomcat port          : 8081
   > tomcat shutdown port : 8006
   > modify server.xml
     --> change ajp port 8009 -> 8010
 - Configure KM search engine
  . set system variables
    JAVA_HOME: C:\Program Files\Java\jdk1.7.0_72
    JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF8
  . sm.ini
    KMSearchEngineClass:com.hp.ov.sm.server.plugins.knowledgemanagement.solr.KMSolrSearch
 - register/install Search engine as a windows service
   > firstly, remove existing sm9.34 KM search engine service **
   --> execute command,
      C:\Program Files\HP\Service Manager 9.30\Search_Engine\installasservice.cmd remove
   > secondly, install sm9.40 KM search engine service
   C:\Program Files\HP\Service Manager 9.40\SearchEngine\installasservice.cmd install master
 - start KMsearch engine
 - SM win client\System Navigator\Knowledge management\Configuration\Configure Search Servers
   add KM Search Servers: sm940.domain.com
   . hostname: sm940
   . port: 8081
   . server tyep: Master
 - SM win client\System Navigator\Knowledge management\Configuration\Knowledgebases
   for all knowledge library
   > Type information: uncheck index attachments
   > click 'Full Reindex'
 - restart SM
 - start KMUpdate background process
 - wait for 10 min or , manually start java script function
   system.library.KMCollection_Update.refreshIndexes();
 - verify KM
   System Navigator\Knowledge management\Search Knowledgebase

13. install sm9.40.0009 mobility
 - reference : sm9.40 mobile application user guide.
 - Tomcat configuration
   -XX:MaxPermSize=256m
   java initial/max=1500M
 - set system variables
   JAVA_HOME: C:\Program Files\Java\jdk1.7.0_72
 - load MOBILITY_ESS_SM940_SM932.unl
 - deploy webapp-9.40.0009.war on tomcat
 . verify on google chrome
   -> inspect element > show drawer > set emulation ( device=Apple iPhone 5 )
   ->
http://localhost:8080/webapp-9.40.0009

HP Support
If you find that this or any post resolved your issue, please be sure
to mark it as an accepted solution.
Please also give kudo if you find it interesting 🙂
Labels (1)
0 Replies
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.