HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- How to start CI and SCS with SGeSAP?
Operating System - HP-UX
1836357
Members
2362
Online
110100
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-20-2008 07:18 AM
02-20-2008 07:18 AM
How to start CI and SCS with SGeSAP?
If I do a su - sidadm -c "startsap" then everything starts on the CI node.
How do I get SCS and CI up and running with SGeSAP (version 4.50)?
And yes - I have read the 316 page doc:
http://docs.hp.com/en/T2803-90011/T2803-90011.pdf
What I need to know is what to put in the sap.config file...
So far I have:
# grep -v "#" sap.config |sort -rn
WAIT_OWN_AS=2
USER_DEFINED=128
TRANSRELOC=192.1.162.55
STOP_WITH_PKG=2
STOP_IF_LOCAL_AFTER_FAILOVER=8
STOP_DEPENDENT_INSTANCES=16
START_WITH_PKG=1
SAPOSCOL_STOP=1
SAPOSCOL_START=1
RESTART_DURING_FAILOVER=4
REM_COMM=ssh
NFSRELOC=192.1.10.169
LISTENER_NAME="LISTENERIQA"
DELAY_INTERVALS=10
DB_PKG=dbIQA
DBRELOC=192.1.10.167
DBHOME="/oracle/IQA/102_64"
DB=ORACLE
CTEXEDIR=${CTEXEDIR:-/usr/sap/${SAPSYSTEMNAME}/SYS/exe/run}
CLEANUP_POLICY=normal
CI_PKG=ciIQA
CIRELOC=192.1.10.169
CINR=00
CINAME=DVEBMGS
AS_PSTART=1
ASSID[1]=IQA; ASHOST[1]=svr042; ASNAME[1]=D; ASNR[1]=00; ASTREAT[1]=7; ASPLATFORM[1]="HP-UX"
ASSID[0]=IQA; ASHOST[0]=svrvp1104; ASNAME[0]=D; ASNR[0]=00; ASTREAT[0]=7; ASPLATFORM[0]="HP-UX"
svr042 is an App server.
svrvp1104 is the CI Node (DB is on another node).
Rgds...Geoff
How do I get SCS and CI up and running with SGeSAP (version 4.50)?
And yes - I have read the 316 page doc:
http://docs.hp.com/en/T2803-90011/T2803-90011.pdf
What I need to know is what to put in the sap.config file...
So far I have:
# grep -v "#" sap.config |sort -rn
WAIT_OWN_AS=2
USER_DEFINED=128
TRANSRELOC=192.1.162.55
STOP_WITH_PKG=2
STOP_IF_LOCAL_AFTER_FAILOVER=8
STOP_DEPENDENT_INSTANCES=16
START_WITH_PKG=1
SAPOSCOL_STOP=1
SAPOSCOL_START=1
RESTART_DURING_FAILOVER=4
REM_COMM=ssh
NFSRELOC=192.1.10.169
LISTENER_NAME="LISTENERIQA"
DELAY_INTERVALS=10
DB_PKG=dbIQA
DBRELOC=192.1.10.167
DBHOME="/oracle/IQA/102_64"
DB=ORACLE
CTEXEDIR=${CTEXEDIR:-/usr/sap/${SAPSYSTEMNAME}/SYS/exe/run}
CLEANUP_POLICY=normal
CI_PKG=ciIQA
CIRELOC=192.1.10.169
CINR=00
CINAME=DVEBMGS
AS_PSTART=1
ASSID[1]=IQA; ASHOST[1]=svr042; ASNAME[1]=D; ASNR[1]=00; ASTREAT[1]=7; ASPLATFORM[1]="HP-UX"
ASSID[0]=IQA; ASHOST[0]=svrvp1104; ASNAME[0]=D; ASNR[0]=00; ASTREAT[0]=7; ASPLATFORM[0]="HP-UX"
svr042 is an App server.
svrvp1104 is the CI Node (DB is on another node).
Rgds...Geoff
Proverbs 3:5,6 Trust in the Lord with all your heart and lean not on your own understanding; in all your ways acknowledge him, and he will make all your paths straight.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-20-2008 11:22 PM
02-20-2008 11:22 PM
Re: How to start CI and SCS with SGeSAP?
You would set
JCINAME=SCS
JCINR=00
JCIRELOC=
and no JDB.
Carsten
JCINAME=SCS
JCINR=00
JCIRELOC=
and no JDB.
Carsten
-------------------------------------------------------------------------------------------------
In the beginning the Universe was created. This has made a lot of people very angry and been widely regarded as a bad move. -- HhGttG
In the beginning the Universe was created. This has made a lot of people very angry and been widely regarded as a bad move. -- HhGttG
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-21-2008 07:06 AM
02-21-2008 07:06 AM
Re: How to start CI and SCS with SGeSAP?
I had a couple of issues.
First, the libsapu16.so library is needed for SCS, but from SGeSAP - it wasn't found.
It is in: /usr/sap/IQA/SCS05/exe
This was due to the way it starts:
su - sidadm -c "csh -c \"/usr/sap/IQA/SCS05/exe/sapstart pf=/usr/sap/IQA/SYS/profile/START_SCS05_iqacip\""
Traced it to the .sapenv.csh and .sapenv_svrvp1104.csh had to add the following:
setenv DIR_LIBRARY /usr/sap/IQA/SYS/exe/run:/usr/sap/IQA/SCS05/exe
And
setenv SHLIB_PATH /usr/sap/IQA/SYS/exe/run:/usr/sap/IQA/SCS05/exe
foreach d ( /usr/sap/IQA/SYS/exe/run /usr/sap/IQA/SCS05/exe )
Second issue I had was with the resolver. I am build 2 copies of an existing Landscape. I use files then dns in nsswitch.conf. However, certain commands bypass the nsswitch.conf and go straight to DNS. (like the host command for example). So I had the floating ip set as iqaci pointing to an ip only on this host - but when SGeSAP started up - it resolved to my real iqaci through DNS.
Anyways, to get CI running was easy after that.
In sap.config:
CIRELOC=192.168.10.169
CINR=00
CINAME=DVEBMGS
For SCS:
JCIRELOC=192.168.10.169
JCINR=05
JCINAME=SCS
For the App server (with 3 instances):
ASSID[2]=IQA; ASHOST[2]=svr0042; ASNAME[2]=D; ASNR[2]=05; ASTREAT[2]=7; ASPLATFORM[2]="HP-UX"
ASSID[1]=IQA; ASHOST[1]=svr0042; ASNAME[1]=D; ASNR[1]=01; ASTREAT[1]=7; ASPLATFORM[1]="HP-UX"
ASSID[0]=IQA; ASHOST[0]=svr0042; ASNAME[0]=D; ASNR[0]=00; ASTREAT[0]=7; ASPLATFORM[0]="HP-UX"
Rgds...Geoff
First, the libsapu16.so library is needed for SCS, but from SGeSAP - it wasn't found.
It is in: /usr/sap/IQA/SCS05/exe
This was due to the way it starts:
su - sidadm -c "csh -c \"/usr/sap/IQA/SCS05/exe/sapstart pf=/usr/sap/IQA/SYS/profile/START_SCS05_iqacip\""
Traced it to the .sapenv.csh and .sapenv_svrvp1104.csh had to add the following:
setenv DIR_LIBRARY /usr/sap/IQA/SYS/exe/run:/usr/sap/IQA/SCS05/exe
And
setenv SHLIB_PATH /usr/sap/IQA/SYS/exe/run:/usr/sap/IQA/SCS05/exe
foreach d ( /usr/sap/IQA/SYS/exe/run /usr/sap/IQA/SCS05/exe )
Second issue I had was with the resolver. I am build 2 copies of an existing Landscape. I use files then dns in nsswitch.conf. However, certain commands bypass the nsswitch.conf and go straight to DNS. (like the host command for example). So I had the floating ip set as iqaci pointing to an ip only on this host - but when SGeSAP started up - it resolved to my real iqaci through DNS.
Anyways, to get CI running was easy after that.
In sap.config:
CIRELOC=192.168.10.169
CINR=00
CINAME=DVEBMGS
For SCS:
JCIRELOC=192.168.10.169
JCINR=05
JCINAME=SCS
For the App server (with 3 instances):
ASSID[2]=IQA; ASHOST[2]=svr0042; ASNAME[2]=D; ASNR[2]=05; ASTREAT[2]=7; ASPLATFORM[2]="HP-UX"
ASSID[1]=IQA; ASHOST[1]=svr0042; ASNAME[1]=D; ASNR[1]=01; ASTREAT[1]=7; ASPLATFORM[1]="HP-UX"
ASSID[0]=IQA; ASHOST[0]=svr0042; ASNAME[0]=D; ASNR[0]=00; ASTREAT[0]=7; ASPLATFORM[0]="HP-UX"
Rgds...Geoff
Proverbs 3:5,6 Trust in the Lord with all your heart and lean not on your own understanding; in all your ways acknowledge him, and he will make all your paths straight.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP