Asset Manager Web installation detailed steps
Download 15.97 Kb.
|
- Navigate this page:
- Primary considerations
- Steps to deploy Webclient in TOMCAT JAVA install
- For a 64 bit AM Web client
- Install the Database server
- For Oracle database client must be installed locally if the database is remote. Depending on the application we need the client; win client uses 32 bit client and 64 bit web uses 64 bit Oracle client.
- Asset Manager Web service : Package.properties file: \websvc\ Parameters to edit and save
- Deploy the package.properties In the command prompt go to \deploy For 32 bit web client
| Asset Manager Web installation - detailed steps
Asset Manager Web can be installed in both the 32 or the 64 bit mode the steps are almost similar with slight variations in the path. If you need to access Asset Manager Web with several concurrent users 64 bit is the best option as it has a very huge addressable memory which improves the performance. Primary considerations :
Steps to deploy Webclient in TOMCAT
Eg: JAVA_HOME : C:\Program Files (x86)\Java\jdk1.7.0_40 PATH : C:\Program Files (x86)\Java\jdk1.7.0_40\bin Run java –version in the command prompt to confirm the install.
Java Classpath: C:\ProgramFiles\ Java\jdk1. Java Options: -Dsun.lang.ClassLoader.allowArraySyntax=true (This option is ONLY for Tomcat6) For a 64 bit AM Web client: -Djava.library.path=C:\Program Files (x86)\ HP\Asset Manager 9.3 For a 32 bit web client: -Djava.library.path=C:\Program Files (x86)\ HP\Asset Manager 9.3 -Djava.library.path=C:\Program Files\HP\ Asset Manager 9.3
MSSQL:
For a 64 bit Web client only the Web and API is 64 bit the Windows client still uses 32 bit DSN hence create both 64 bit System DSN and 32 bit DSN as well. ODBC connection: On a 64 bit Windows OS: 32 bit DSN is created under C:\Windows\SysWOW64\odbcad32.exe - System DSN or Start - Administrative Tools - Data Source ODBC.
Only 32 bit DSN can be created from C:\WINDOWS\system32 or Administrative Tools - Data Source ODBC) For Oracle database client must be installed locally if the database is remote. Depending on the application we need the client; win client uses 32 bit client and 64 bit web uses 64 bit Oracle client.
Asset Manager Web service : Package.properties file: Parameters to edit and save: AssetManager.UserLogin= Admin AssetManager.UserPwd= pidf5oqm+AI=
DB.datasource= DB.login= DB.password= Copy all the files from java.exe -jar am-pwd-crypt-93.jar Copy this encrypted password to the DB.password parameter.
DB.library.path=C:/Program Files (x86)/HP/Asset Manager 9.3 **If 32 bit AM Web client: DB.library.path=C:/Program Files (x86)/HP/Asset Manager 9.3 **In 32 bit OS: DB.library.path=C:/Program Files/HP/Asset Manager 9.3 arch = <32 or 64> encrypt=false Asset Manager Webtier : Package.properties file : Parameters to verify : AssetManager.UserLogin= Admin AssetManager.UserPwd= pidf5oqm+AI= Verify the tomcat port mentioned is correct.
In the command prompt go to For 32 bit web client: deploy.bat ..\websvc\package.properties deploy.bat ..\webtier\package.properties
deploy.bat /64 ..\websvc\package.properties deploy.bat /64 ..\webtier\package.properties
Stop Tomcat. Delete el-api.jar file from \webtier\AssetManager.war. It’s under WEB-INF\lib. (ONLY if you are using Tomcat 6.x) Copy the AssetManagerWebService.war and the Assetmanager.war to the Copy the Copy am-constants-9x.jar and am-jni-9x.jar from websvc\lib to Start Tomcat.
Directory: hpeb -> attachments -> hpeb hpeb -> Installing the Linux Client System hpeb -> Deploy Operating System toolbar button hpeb -> Hp service Manager Single Sign On Implementation Integration with Integrated Windows Authentication hpeb -> Pcm-04. 00. 00. 1609-x64. exe Download 15.97 Kb. Share with your friends:
|