SAP hosted PI 7.1

I remember seeing an SAP hosted PI 7.1 earlier. Is this still around?
I dont find the link now...can anyone send me the same?
reg

Hi Naveen,
Are looking for SAP ES workspace?
if yes then here are some details which will help you :
1. You need to register to create a Login for you ([link|http://esworkplace.sap.com/socoview(bD1lbiZjPTAwMSZkPW1pbg==)/render.asp?sap-unique=162713&sap-params=aWQ9RjZDRkMwRUEzRUYxNEJDOTg0MUM1MjgyNzJFRTg1ODMmcGFja2FnZWlkPURFRTk4RDA3REY5RkE5RjFCM0M3MDAxQTY0RDNGNDYyJm1vZGU9] for registration page:{red letters on the right side}) I am not sure if only S user can have access or all users.
2. Once you get your ID created , you will get access to following:
ABAP Systems: HU2 (ERP), HU4 (CRM), HU5 (SRM), HU8 (SCM).You can access the system via WebGUI directly from here:
HU2 SAP ERP 6.0 (ECC 6.00 EhP4 SP03)
HU4 SAP CRM 7.0
HU5 SAP SRM 7.0
HU6 SAP PI 7.1
HU8 SAP SCM 7.0
few days back i came across this , but its kind of dummy stuff with little functionalityMight not be that useful to do hands on etc.
Regards,
Srinvas

Similar Messages

How to change SAP host IP?

Hi, All
I want to change SAP host 's IP, the SAP system are installed as a Central System, Usage Type:
application server abap
enterprise portal
business intelligence
application server java
ep core
windows server 2003 x64, oracle 10g
Which configurations must be changed? such as database, ep, etc.
Best regards
Jiande Ding

If u r using java stack then u have to change in host file and in visual administrator u have to change fully host name .
Regards,
Gurprit Bhatia

Diagnostics Agent 711 - SAP Host Agent - Installation on a cluster environm

Dear all,
We have the following architecture in our productive environment :
1. Cluster 01 is composed of 2 nodes.
   On Cluster 01, only "Database" and "Central Services" are running
   for 5 productive SAP systems.
2. Cluster 02 is composed of 6 nodes.
   On Cluster 02, only "Central Instance" and "Application Server"
   are running for 5 productive SAP systems
As read in "Diagnostics Agents installation Strategy", rules #4, slide 12 :
===================================================================
- Do not install a Diagnostics Agent on host that only run Database
or SAP Central Services.
- Install a Agent on EACH host running a Central Instance (CI)
and / or a Dialog Instance
===================================================================
For our productive environment, we do have to install Diagnostics Agents 7.11 on cluster 02 where we have CI + AS running.
Questions :
1. How do we monitor "database" and "central services" data on cluster 01 (DB + CS) as far as no "Diagnostics Agents"
   are installed ?
2. Do we have to install the new "SAP HOST AGENT" in our cluster 01 ?
3. As written in "Downloading and Installing Package SAPHOSTAGENT"
   guide, "you only need to install the host agent host taht not have
   an SAP Component". Does it mean that the new "SAP HOST AGENT"
   will have to be installed on our cluster 01 to monitor "DB+CS" data ?
4. What are for SAP a host that not have SAP Component ... ?
    "Database" and "Central Service" running for a SAP system should be consider as SAP Component or not ... ?
5. What is the difference between the new "SAP HOST AGENT" delivered by SAP today 23.11.2009
    and the "Wily Host-Level Introscope Agent"
   delivered by CA ?
Best regards
PC

Yes, it has to be installed.

Moving SAP Services between SAP hosts

I have several Web service created from RFC ABAP funciton Modules on one SAP system Client 005
I would like to move the Services to another SAP Host client 005
How can I do this?
The RFC ABAP function modules are imported into the new SAP host. will the Web services also get imported or do I have to create a new transport for those?
Thanks
Jawahar

Hi,
How u can go ahead with solution , for ur mentioned problem:
make PO with proper doc type , then in line item enter value 1000$ and qty 1 imp unit will be AU( activity Unit ). and maintained validilty period for same.
Means service entery based on how much invoice u have received out of 1000$ .i.e if u recived 700$ then do service entry sheet for 700$ and keep qty 1 with unit AU as this is service not a qty based PO.
Then u can do invoice.
After this remaing value invoice comes then again u can do ur service entry sheet for remaining value with qty 1 and unit AU.

SAP Hosting for the EP implementation?

I have been asked to investigate the hosting options available for EP 6.0.
Can anyone offer any experience or advice that I may use?
Thanks,
Ron Jones
[email protected]

Hi,
I guess SAP Hosting will be happy to offer something. gg
You could check http://www.saphosting.com/services/applicationhosting.asp for little more details. But at least there is mentioned a contact email.
Best Regards,
rAimund

SAPOSCOL does not start with SAP Host Agent processes

Dear all,
on one of our servers the SAPOSCOL process is not running. The latest SAP Host Agent is in place - automatic updating has been finished sucessfully but after the restart of the host agent processes SAPOSCOL returned the following entry in log dev_saphostexec:
[Thr 01] Fri Nov 25 11:23:30 2011
[Thr 01] *** WARNING => /usr/sap/hostctrl/exe/saposcol -l -w60 pf=/usr/sap/hostctrl/exe/host_profile exit with status 4 [OsCollectorW 171]
It is only a warning but as a consequence no SAPOSCOL process is running.
Any ideas? Your quick response will be very much appreciated
Regards,
Mattias Umlauf

Hi
if
/usr/sap/hostctrl/exe/saposcol -status
shows no PID but shared memory attached either cleanipc
or try to force start saposcol
/usr/sap/hostctrl/exe/saposcol -f
Regards
Stanislav

Certificacao para ser um SAP Hosting Parnter

Ola' Pessoal,
gostaria de obter algumas informacoes relacionadas ao processo de certificacao para ser um SAP Hosting Partner, tais como:
- macro plan
- capacity plan
- estimativas
- qual o esforco para ser compliant em termos de plataforma, processos, etc
obrigada
Maristela

Oi Maristela.
Veja se é isso que procuras...
http://partner.sap.com
http://www.sap.com/ecosystem/partners/pdf/Software_Solution_Partners_Application_Checklist.pdf
Abraço
Eduardo

SAP Host and Diagnostic agent

Dear Experts,
We are running ECC 6.6 and Portal on Net Weaver 7.31 ,and have Soution Manager 7.1,As I have read many places that host agent get installed automatically with Net Weaver Installation.
In My Portal server I am able to see hostctrl folder and SAPHostControl service related to host agent, but there is no such service or folder in R/3 server.So do I need to install Host Agent separately for R/3 system.
One more Question do I need to have Host agent mandatory for Diagnostic agent installation(SMD)?
Thanks
Chander

Hello
In our R/3 system Kernel release is 720 ,and we doesn't have SAP host agent,But for Java with same kernel release we have SAP host agent.
If this is an ECC system upgraded from an old R/3 system then you might have ignored to install SAP Host Agent as I have seen the upgrade guides suggesting to install SAP Host Agent starting from EHP5.
When we installed Net Weaver 7.31 for java portal SAP Diagnostic agent installed automatically and with that SAP host agent also came.
Read my previous reply. All new installation bring in SAP Host Agent.
My main purpose to install Diagnostic agent for R/3 for E2E analysis ,so i want more clarity regarding SAP host and diagnostic agent.
R/3 is on Net Weaver 7.31( ECC 6.6), So which version of diagnostic and host agent need to be installed and are they installed separately .
Follow the SAP note I have given above. The latest version is SAP HOST AGENT 7.20
Here is the SAP note once again 1031096 - Installing Package SAPHOSTAGENT
Regards
RB

Metric: SAP Host Agent Availability doubt

Hello folks!
I have a problem in technical monitoring from Solution Manager, and i would be happy, if someone could help me with this.
1 - SAP Solution Manager is trying to ping a IP that doesnt exists
2 - In the screenshot, the line is: "Ping to listener: xxx.xxx.xxx.xxx:port not successful".
Let's call the host of my managed object as "$HOST_NAME", and the IP as "$HOST_IP".
1 - The IP of $HOST_NAME is one, and the IP xxx.xxx.xxx.xxx that SolMan is trying to ping, is another, the ip doesnt even exists, because i can't reach him from anywhere. Is it not wrong? I think the "Listener" should be the $HOST_IP, not another...
2 - The correction for this problem, would be the adjustment of the "Listener" to the $HOST_IP? How could i do this?
Thanks already

Hi,
Host agent runs on physical machine.
Can you goto agent admin and find host name and IP from there.
Divyanshu

Issue in soap request SAP Host Control

Hi. I use SAP NW 7.4 SP2 and have issue in next request
POST / HTTP/1.1
SOAPAction: ""
Content-Type: text/xml; charset=UTF-8
Content-Length: 559
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:ns0="urn:SAPHostControl">
<SOAP-ENV:Header/>
<SOAP-ENV:Body>
    <ns0:MoveIpAddress>
      <aInterfaceName/>
      <aAddress>IP</aAddress>
      <aAddressFamily/>
      <aTargetHost>IP</aTargetHost>
      <aTargetUser/>
      <aTargetPassword/>
      <aTargetInterfaceName>???</aTargetInterfaceName>
      <aConnectionToTarget>???</aConnectionToTarget>
    </ns0:MoveIpAddress>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
maybe does anyone used this request, what I need write in aTargetInterfaceName && aConnectionToTarget aConnectionToTarget - http, tcp or https don't work
Thank you

Hi,
Run the program 'RSTXTRAN' using transaction SE38 and attach the Text object to your TR.
Last time I faced the same problem.
Everything gets transported except Text object.
Hope it will be useful to u.
Revert if not resolved.
Regards
Amit
Edited by: Amit Gupta on May 14, 2009 7:31 AM

P2v conversion of sap ecc6 host w/ ISCSI Lun

Hello, I am looking for some feedback here please.
Background:
We have an Physical SAP Host that has ISCSI LUNs (volumes) attached with are formatted as NTFS file system. These are then presented to the OS as drive letters L:\ (Logs) and D:\ (Database) and M:\ (Backups).
We want to virtualize the entire machine and create a virtual machine on ESX Virtual Infrastructure 3. We have an EMC AX4 SAN.
The question is how to do it?
There appear to be two ways:
1. The first way and perhaps the easier way would be to stop SAP, stop the Database and log off the ISCSI adapters from the OS. Then virtualize the physical machine (P2V) with only the C:\ drive. When the machine comes up as a virtual host, it should reattach directly to the existing LUNs through its internal configuration and attach to the existing LUN. We may have to fiddle around with the drive letters to get them to be as previously L:\ D:\ and M:\ but essentially there is not really anything else to do. The internal EMC Powerpath should still be working properly. The ESX Host is already connected and configured to have one physical adapter on the iSCSI VLAN; thus, there should be no additional configuration as long as the VM sees the same network.
2. The second way would be to perform the entire P2V migration and create a brand new gigantic LUN on the SAN and virtualize the entire physical host including all the attached drives. The disadvantages here would be that the entire machine would be on one gigantic LUN and each Drive Letter would be a different file. (I believe).
To complicate things we also have a Cluster with three ESX Hosts. VMotion between Hosts would be no issue under either solution.
I would like to get feedback on how to proceed and hear about any pros/cons and or any success or failure stories.
Thank you,
Pete

Hi Nadeem
Save your init<SID>.ora.
You can try to set processes and sessions parameters in the init<sid>.ora to the following value :
processes = 800
sessions =1600
- Stop your instance
- Stop your DB
- Recreate the spfile
- Start your DB
- Start your instance
If the issue does not solve the problem, you return back.
Otherwise, when you start your instance is that the processes dw.sap <SID> _DVEBMGSXX starts then dies or they do not start?
Best regards.

SAP HANA Lifecycle Manager Couldn't deploy using credentials

Hello,
After HLM 1.0.7.7 upgrade from 1.0.6 on IBM appliance we could not apply support packages in normal mode. When we launch the Upgrade process from Hana Studio or Command line we recive the following message:
Error Message: Execution of 'Deploys SAP Host Agent configurations using sidadm credentials' failed.
Detailed Message: null or empty argument
Help: http://help.sap.com/hana
We tried to downdgrade and reinstall HLM again with no luck. Users, Parsswords and Certificates was also renewed. We could read this log from HLM.
INFO 2014-05-08 16:05:15 com.sap.lm.hlm.common.wizard.process.WizardProcessExecutor
Submit for subtask with ID [6cd61e09-eb68-4448-86c0-b4319abbdc3f_GetUpdateTypeTask]
INFO 2014-05-08 16:05:15 com.sap.lm.hlm.common.wizard.process.WizardProcessExecutor
Submit for subtask with ID [6cd61e09-eb68-4448-86c0-b4319abbdc3f_GetUpdateTypeTask]
INFO 2014-05-08 16:05:15 com.sap.lm.hlm.common.wizard.process.WizardProcessExecutor
Starting execution of subtask with ID [6cd61e09-eb68-4448-86c0-b4319abbdc3f_DeployConfigWithSidAdmTask]
INFO 2014-05-08 16:05:15 com.sap.lm.hlm.common.wizard.process.WizardProcessExecutor
Starting execution of subtask with ID [6cd61e09-eb68-4448-86c0-b4319abbdc3f_DeployConfigWithSidAdmTask]
INFO 2014-05-08 16:05:15 com.sap.lm.hlm.common.tasks.process.AbstractProcessExecutor
Starting process [Deploys SAP Host Agent configurations using sidadm credentials, com.sap.lm.hana.hlm.update.slpp.task.deployconfig.DeployConfigWithSidAdmTask] ({})...
INFO 2014-05-08 16:05:15 com.sap.lm.hlm.common.tasks.process.AbstractProcessExecutor
Starting process [Deploys SAP Host Agent configurations using sidadm credentials, com.sap.lm.hana.hlm.update.slpp.task.deployconfig.DeployConfigWithSidAdmTask] ({})...
INFO 2014-05-08 16:05:15 com.sap.lm.util.status.StatusTracker
Status tracker initialized using storage file /usr/sap/hlm_bootstraps/HNB/HLM/param/configdeploystatus.properties.
INFO 2014-05-08 16:05:15 com.sap.lm.util.status.StatusTracker
Status tracker initialized using storage file /usr/sap/hlm_bootstraps/HNB/HLM/param/configdeploystatus.properties.
INFO 2014-05-08 16:05:15 com.sap.lm.hana.hlm.update.slpp.context.ProgressObserverAdapter
Progress [ 0%]
INFO 2014-05-08 16:05:15 com.sap.lm.hana.hlm.update.slpp.context.ProgressObserverAdapter
Progress [ 0%]
INFO 2014-05-08 16:05:15 com.sap.lm.hana.hlm.update.slpp.task.deployconfig.AbstractDeployConfigProcessExecutor
Deploying SAP Host Agent configurations on host with sidadm credentials.
INFO 2014-05-08 16:05:15 com.sap.lm.hana.hlm.update.slpp.task.deployconfig.AbstractDeployConfigProcessExecutor
Deploying SAP Host Agent configurations on host with sidadm credentials.
INFO 2014-05-08 16:05:15 com.sap.lm.hana.hlm.update.slpp.context.ProgressObserverAdapter
Process message: Deploying SAP Host Agent configurations on host
INFO 2014-05-08 16:05:15 com.sap.lm.hana.hlm.update.slpp.context.ProgressObserverAdapter
Process message: Deploying SAP Host Agent configurations on host
INFO 2014-05-08 16:05:16 com.sap.lm.services.hostcontrol.SAPHostControlService
Deployed Host Agent configurations [/usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-hdb-plugin.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-studio-repository.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-client-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-sedm-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-studio-repository-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/find-java-home-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-client-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-load-controller-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-sda-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-client-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-studio-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-hdbstudio-deliveryunit.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-studio.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/newdb-studio-repository-postupdate-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-client.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-sda-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-server.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/find-java-executable.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/newdb-studio-repository-postupdate.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-hdb-plugin-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-studio.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-studio-repository-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-load-controller.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-client-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-client-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/change-newdb-client-installation-path-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-studio-repository-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/updatehostagent-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-studio-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/find-java-executable-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-studio-repository.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/updatehostagent.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-server-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-client.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-load-controller-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/exists-path.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/gen-hdbstudio-deliveryunit.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/change-newdb-studio-repository-installation-path-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-server-nzdm.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-hdb-plugin.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-server.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-installation-number.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-load-controller.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-hdb-plugin-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-installation-number-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-hdb-plugin-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-server-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/updatehostagent-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-studio-repository.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-studio-repository-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-hostagent-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-hostagent.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/find-hdbeuspack.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-client.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-studio-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-server-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-client-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-studio-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/chmod-file.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-client.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/find-java-home.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-studio.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-sedm.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-studio-repository-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/exists-path-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-client-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-studio-v2.conf] with signature /usr/sap/hlm_bootstraps/HNB/HLM/SIGNATURE.SMF on host .
INFO 2014-05-08 16:05:16 com.sap.lm.services.hostcontrol.SAPHostControlService
Deployed Host Agent configurations [/usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-hdb-plugin.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-studio-repository.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-client-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-sedm-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-studio-repository-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/find-java-home-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-client-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-load-controller-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-sda-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-client-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-studio-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-hdbstudio-deliveryunit.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-studio.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/newdb-studio-repository-postupdate-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-client.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-sda-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-server.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/find-java-executable.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/newdb-studio-repository-postupdate.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-hdb-plugin-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-studio.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-studio-repository-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-load-controller.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-client-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-client-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/change-newdb-client-installation-path-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-studio-repository-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/updatehostagent-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-studio-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/find-java-executable-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-studio-repository.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/updatehostagent.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-server-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-client.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-load-controller-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/exists-path.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/gen-hdbstudio-deliveryunit.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/change-newdb-studio-repository-installation-path-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-server-nzdm.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-hdb-plugin.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-server.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-installation-number.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-load-controller.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-hdb-plugin-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-installation-number-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-hdb-plugin-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-server-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/updatehostagent-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-studio-repository.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-studio-repository-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-hostagent-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-hostagent.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/find-hdbeuspack.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-client.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-studio-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-server-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-client-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-newdb-studio-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/chmod-file.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-client.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/find-java-home.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-studio.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/detect-sedm.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/install-newdb-studio-repository-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/exists-path-v2.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/update-newdb-client-v3.conf, /usr/sap/hlm_bootstraps/HNB/HLM/operations.d/uninstall-newdb-studio-v2.conf] with signature /usr/sap/hlm_bootstraps/HNB/HLM/SIGNATURE.SMF on host .
ERROR 2014-05-08 16:05:16 com.sap.lm.hana.hlm.update.slpp.task.AbstractUpdateProcessExecutor
Process executor failed
java.lang.IllegalArgumentException: null or empty argument
at com.sap.lm.hlm.common.runtime.HlmRuntime.assertNotNullOrEmptyArgumens(HlmRuntime.java:342)
at com.sap.lm.hlm.common.runtime.HlmRuntime.deployHlmExecutableScripts(HlmRuntime.java:74)
at com.sap.lm.hlm.common.runtime.HlmRuntime.deployHlmExecutableScripts(HlmRuntime.java:69)
at com.sap.lm.hana.hlm.update.slpp.task.deployconfig.AbstractDeployConfigProcessExecutor.deployconfigurations(AbstractDeployConfigProcessExecutor.java:114)
at com.sap.lm.hana.hlm.update.slpp.task.deployconfig.DeployConfigWithSidAdmProcessExecutor.executeInternal(DeployConfigWithSidAdmProcessExecutor.java:42)
at com.sap.lm.hlm.common.tasks.process.AbstractProcessExecutor.startInterruptibleExecution(AbstractProcessExecutor.java:128)
at com.sap.lm.hlm.common.tasks.process.AbstractProcessExecutor$1.run(AbstractProcessExecutor.java:108)
ERROR 2014-05-08 16:05:16 com.sap.lm.hana.hlm.update.slpp.task.AbstractUpdateProcessExecutor
Process executor failed
java.lang.IllegalArgumentException: null or empty argument
at com.sap.lm.hlm.common.runtime.HlmRuntime.assertNotNullOrEmptyArgumens(HlmRuntime.java:342)
at com.sap.lm.hlm.common.runtime.HlmRuntime.deployHlmExecutableScripts(HlmRuntime.java:74)
at com.sap.lm.hlm.common.runtime.HlmRuntime.deployHlmExecutableScripts(HlmRuntime.java:69)
at com.sap.lm.hana.hlm.update.slpp.task.deployconfig.AbstractDeployConfigProcessExecutor.deployconfigurations(AbstractDeployConfigProcessExecutor.java:114)
at com.sap.lm.hana.hlm.update.slpp.task.deployconfig.DeployConfigWithSidAdmProcessExecutor.executeInternal(DeployConfigWithSidAdmProcessExecutor.java:42)
at com.sap.lm.hlm.common.tasks.process.AbstractProcessExecutor.startInterruptibleExecution(AbstractProcessExecutor.java:128)
at com.sap.lm.hlm.common.tasks.process.AbstractProcessExecutor$1.run(AbstractProcessExecutor.java:108)
ERROR 2014-05-08 16:05:16 com.sap.lm.hlm.common.wizard.process.WizardProcessExecutor
Execution of subtask with ID [6cd61e09-eb68-4448-86c0-b4319abbdc3f_DeployConfigWithSidAdmTask, Execution of 'Deploys SAP Host Agent configurations using sidadm credentials' failed.] has failed: {}
ERROR 2014-05-08 16:05:16 com.sap.lm.hlm.common.wizard.process.WizardProcessExecutor
Execution of subtask with ID [6cd61e09-eb68-4448-86c0-b4319abbdc3f_DeployConfigWithSidAdmTask, Execution of 'Deploys SAP Host Agent configurations using sidadm credentials' failed.] has failed: {}
Could you please help us with this issue?
Kind Regards,
Message was edited by: Tom Flanagan

Hi Alston,
I'm sorry for the late reply. Are you still experiencing this error?
I've seen this issue before with another customer and the final resolution was to make sure the /etc/hosts file does not have the ipv6 BEFORE ipv4. Here is an example:
>> cat /etc/hosts
# special IPv6 addresses
::1             localhost ipv6-localhost
ipv6-loopback
ff02::3         ipv6-allhosts
192.168.180.31 abceccd01.sap.com abceccd01
192.168.180.34 abceccs01.sap.com abceccs01
192.168.180.35 abccrms01.sap.com abccrms01
192.168.180.30 abceccs01.sap.com abceccs01
10.36.10.5      abceccs01-nfs.sap.com abceccs01-nfs
The resolution would be to change the ordering. So the IPv6 section appears below the IPv4 section.
After that is done, perform the following to "reset" HLM.
1. Stop all browsers that have HLM pages open
2. Stop the Studio
3. Execute /usr/sap/hlm_bootstraps/<SID>/HLM/stop-hlm.sh –f
4. Check that there are no any left HLM processes
5. Go to /usr/sap/hlm_bootstraps/<SID>/HLM/param/
and rename all files except logging.properties
6. go to directory: /usr/sap/hlm_bootstraps/<SID>/HLM
and rename directory persistence
7 restart SAP Host Agent - as root: /usr/sap/hostctrl/exe/saphostexec
-restart
8. open HLM ui via browser:
https://<hostname>:1129/lmsl/HLM/<SID>/ui/
I hope this helps.
Best Regards,
Jimmy

Crystal Report 2011- SAP Data Sources: CL - no items found

Background:
SAP ECC 6.0 was purchased three years ago with DSD package. Only FI and SD modules are in use. Accounts download data filesfrom SAP to produce spreadsheet reports. Few user trust these numbers. We are setup as "SAP in the Cloud" model- Listening to constant user complaints, it seems SAP is broken. Interim solution: Crystal Report for everyone.
Encouraged by Ingo Hilgefort papers and Crystal Report Forum:
We decided to deploy Crystal Report 2011 and Business Object XI 3.1 with SP4 for our small user community. These software are installed on local XP laptop and Business Object XI 3.1 installed in the SAP server as well.
Problem Description:
The desktop user cannot see SAP infosets or tables contents. When connect to the data sources. After user login, she can navigate to expand the data source CL.- displays "no items found ". I can reproduce this error. Using the Crystal Report wizard and selecting various data sources such as: SAP Table, Cluster and Functions: CL, DD and FN category only DD and FN display items.
Current Environment: SAP in the Cloud.
SAP Server::ECC 6.0 EhP3 dual stack. Database MSSQL, OS 2008 Server, Business Object Intergration Kit 3.1, Remote Acces VPN.
Desktop Environment: Crystal Report 2011: SP1, Business Object Xi 3.1, XP SP3
Surprise: Clicking on either DD and FN tab inside the connector window in Crystal- it expands and displays tables and content reference but not CL.
Questions: Do we have to move to EhP5 for the CRX 2011 to work ? What is wrong: ? Any help will be appreciated?
This question is for Ingo H. How to convince SAP hosting company otherwise to solve our problem ? Is is desktop problem or Host side configuration ?

Ahmad
K900687 is Open SQL Connectivity transport and required for direct SAP tables connectivity, so you need it, but I am not sure if the warning message relevant to your problem. Sometimes warning is just a warning.
You can see other objects in DD, but not in CL, it means the connection works. You probably do not have required authorisations to see objects.
I would suggest to review the Authorisation section of SAP Integration Kit Installation Guide here:
[http://service.sap.com/~sapidb/011000358700000559912010E/xi31_sp3_bip_sap_inst_en.pdf ]
You may also check what is the differences between DD and CL in terma of authorizations.
If you think CR 2011 is broken, then test CR 2008. Is still available for free 30-days trial download here:
[http://www12.sap.com/solutions/sapbusinessobjects/sme/freetrials/index.epx]
, but you would need to add SAP Integration Kit to it.
Vitaly

Timeouts increased after we moved USR, SAP data files and TLogs to new SAN

We are having issues with timeouts after we moved our USR, SAP SQL Datafiles and SAP Transaction Logs from our old SAN to a new SAN.
Timeouts for SAPGUI users are set to 10 minutes.
We are running Windows Server 2003 with SQL Server 2005.
The SAP database has 8 datafiles with a total size of about 350GB.
Procedure we used to move SAP to new SAN:
1. Attached 3 new SAN Volumes
     -a. USR
     -b. Data Files
     -c. Transaction Logs
2. Shutdown SAP and SQL services
3. Alligned the new volumes with a 1024kb offset and gave the Data files and Transaction log volumes a 64kb allocation
    size. (The alignment and 64kb allocation size were not setup for these volumes on the old SAN)
4. Copied the 3 volumes from old to new.
5. Changed the new volumes drive letter to the drive letters of the old volumes.
     -a. I had to restart in order to change the USR volume.
     -b. Because of this I had to resetup the sapmnt and saploc shares.
6. Started SQL services and then SAP services and everything came up just fine.
The week before we had anywhere from 1 to 9 timeouts per day.
This week: Monday had 20 and Tuesday had 26.
On Monday we saw that MD07 was the only transaction that was timing out, but Tuesday had others as well.
The amount of users in the system is about the same. The amount of orders going in are about the same. No big transports went in right before we switched.
Performance counters that I know about for disk look a lot better on the Data Files.
- PAGEIOLATCH_SH ms/request is about 50% better
- Under I/O Performance in DBACOCKPIT:
- MS/OP is now anywhere from 5 to 30 - Old SAN: 50 to 300
- The Hit Ratio is over 99% - same as the old SAN
Looking at Wiley Introscope graphs:
- The "SAP Host: Average queue length" is about 30% to 40% lower then the old SAN.
- the "SAP Host: Disk utilization in %" is about the same.
Questions:
1. Did we do anything wrong or miss anything with our move procedure?
     a. Do we have to do anything in SQL since we changed volumes even though we kept the drive letters the same?
2. What other logs or performance counters should I be looking at?
Thank you,
Neil

Our new SAN Vendor is Compellent. They have been fantastic. I would highly recommend checking them out.
The reasons for the timeouts had nothing to do with the SAN...Well kind of anyway.
I decided to check t-code SM20 to see what users were doing when these timeouts were happening. What I found was the program R_BAPI_NETWORK_MAINTAIN was being called thousands of times in a matter of 10 to 15 minutes at random times through out the day. It would take up about 50 to 80 percent of the amount of programs being executed during these times.
So, I sent this information to our developers and they found out that R_BAPI_NETWORK_MAINTAIN was being called from another program that was looping thousands of times. The trigger to stop the loop wasn't happening fast enough. They made a change and we haven't seen the timeouts since.
I think that the performance increases allowed the loop to run faster which caused the slow downs and timeouts to happen more often.
Thank you to everyone for their help!
Neil

LKM SAP BW to Oracle (SQLLDR) generates sintax error in ABAP code.

Hi Experts,
We are installing a SAP BW KM's in ODI 11g.
Actually, we are able to make reverse ingeneering succesfully.
Now we want to use the LKM in order to extract SAP data.
The KM fails, in step Generate ABAP Code. The code is uploaded to SAP system but with sintaxis errors.
That's the beginning of the SAPAbapExecuteOpenTool_8001_7001.log.
+##################################################+
+############ Open Tool Logger ####################+
+##################################################+
+############ Upload value: 1+
+############ Execute value: 1+
+############ BASE RKM FLAG: 0+
+############ ZRFC_RUN_INSTALL: 1+
+############ Abap Function Name: ZODI_8001_7001+
+############ Sap Host Name: XXXXXXXX+
+############ Sap User Name: XXXX+
+############ Sap password: ********+
+############ Sap Client: 100+
+############ Sap language: ES+
+############ Sap system no: 00+
+############ Sap Connection Pool Name: SAP_ODI_LKM_POOL_GLOBAL+
+############ Sap Connection Pool Size: 10+
+############ Sap Function group name: ZODIBW_LKM_FGRP+
+############ File Delimiter:+
+############ File Name: ZODI_8001_7001.txt+
+############ FTP Host: XXXXXXXXX+
+############ FTP User: ftpbi+
+############ FTP Password: ********+
+############ FTP Passive Mode: 1+
+############ FTP Transfer Time out: 100000+
+############ User abap parameter names: IV_DELIMITER,CHAR1;IV_FILENAME,CHAR255;IV_USER,CHAR35;IV_PWD,CHAR35;IV_HOST,CHAR35;IV_HASHVALUE,CHAR35;IV_PATH,CHAR35;IV_REQUID_L,RSSID;IV_REQUID_H,RSSID+
+############ Abap rfc table parameters: RETURN,BAPIRETURN;ET_FILE_RETURN,BAPIRET2+
+############ Log File Name: /tmp/SAPAbapExecuteOpenTool_8001_7001.log+
+############ OpenHub Path: /tmp/+
+############ Delta Extraction First Request ID : 0+
+############ Delta Extraction Last Request ID : 0+
+############ SAP Development Class : ZODIBW_PCKG+
+############ Max Row Count :+
+############ Fetch Batch Size :+
+############ Hash Value Marker: HVM+
+############ Generated Program:+
*** ODS DSO extraction
TYPES: BEGIN OF ty_final,
+/BIC/AZOFI_UTE00_/BIC/ZFI_SOCOR+
TYPE
+/BIC/AZOFI_UTE00-/BIC/ZFI_SOCOR,+
+/BIC/AZOFI_UTE00_SOURSYSTEM+
TYPE
+/BIC/AZOFI_UTE00-SOURSYSTEM,+
END OF ty_final.
In the SAP GUI shows a sintaxis error.
Functions Module ZODI_8001_7001. line 25
The name "/BIC/AZOFI_UTE00_/BIC/ZFI_SOCOR" is longer that allowed.
+30 characters.+
Really the TYPE "/BIC/AZOFI_UTE00_/BIC/ZFI_SOCOR" has 31 characters.
The sufix "/BIC/" is the "NAMESPACE", a SAP grouping concept.
AZOFI_UTE00 is a table name.
ZFI_SOCOR is a column name.
Are this sufix correct in the APAP code?
Has anyone had that problem?
Any comment will be wellcome.
Thank's in advance.

Hi Somchai,
r U able to resolve ur issue ..........i'm also struck there at the same point.
I am using shared folder for file transfer and my error message is
java.lang.RuntimeException: Error occured in open tool execute method...Error in executing ABAP program...Error in executing ABAP program...Error occurred when creating dataset\\<hostname>\bi-interface$\ZODI_11001_12001_GLOBAL.txt
Thanks.
Edited by: Drona on Mar 26, 2012 7:25 AM

SAP hosted PI 7.1

Similar Messages

Maybe you are looking for