SMD Setup on Cluster System

Hi,
I am in process of setting up SMD in our landscape.
I have set up the monitoring system successfully on our SOLMAN.
But i am facing issues while installing the SMD Agent on my CRM system which is a cluster .
The installer is selecting C:\usr\sap\SMD as the default drive and is throwing error:
ERROR 2009-05-20 13:02:24
FSL-06002 Error 2 (The system cannot find the file specified.
) in execution of a 'CreateProcess' function, line (284), with parameter (C:\usr\sap\SMD\exe\sapstartsrv.exe ...).
Please suggest me how to proceed on this.
Regards,
Shashank
Edited by: Shashank Singh on May 21, 2009 10:27 AM
Hi ,
I extracted the SCS.SAR file and placed the files in the c:\usr\sap\SMD\exe directory.
After that the installation was successfull.
Shashank

Hi,
I extracted the SCS.SAR file to c:\usr\sap\SMD\exe and continued with the installation which completed successfully.
Thanks,
Shashank

Similar Messages

SMD Setup for MDM

Hello Gurus,
While configuring SMD setup for MDM system, i am getting following error, for MDIS and MDSS
[Wilyhost Agent] Failed to configure EP Agent for sapkrftmox01.krft.net (MDM Host)
My MDM system is not an EP system, strainge how am i getting this error related to EP.
Also in the Local SMD Agent Application log on MDM Host getting the error
[Thread[Thread-14,5,main]] Warning    com.sap.smd.wily.hostagent.action.AbstractAction - run(): Action SAPOsCol not running because status is PERMANENT_ERROR
[Thread[Thread-23,5,main]] Warning    com.sap.smd.wily.hostagent.action.SapOsColAction - launchDaemon(): launchDaemon: saposcol exited with -1
[Thread[ExecutionRunner_4,5,ExecMgrThreadGroup]] Warning    com.sap.smd.wily.hostagent.destination.ProcessReader - readOutput: Error output: prtdiag can only be run in the global zone
Need the help...please....
Regards
Manoj

Hi,
Can you check your SAP OS Collector is running (SSAPOSCOL)?
What is your Solman version?
Thanks,
Pradeep

System shows wrong product version in smsy and SMD Setup Wizard

Hi
We have a SOLMAN EHP1 SPS22 running. The Satellite systems are correctly registered in SLD, also the SOLMAN Fetchjobs is running successfully.
I wanted to run the SMD Setup for a NetWeaver ABAP system, when I click in the Setup Wizard on the System the following link is under Managed Products apears: [NOT DIAGNOSTICS RELEVANT] .
By clicking the link you get the products to be managed, but i only two products are for selection.
SAP ERP 6.0 and SAP FSCM 6.0.
In smys checked the assignment in Systems --> <SID> in the Header Tab I clicked Installed Product version. The List in the Pulldown menu in "Product" are the same as above: SAP ERP 6.0 and SAP FSCM 6.0.
I tried to assign the product manually with no luck. Running the Solman_setup for the Diagnostics did not solve the problem either.
Thanks for your help
Murat

Hi Stuart,
In SolMan, goto t-code SMSY-> Product Definitions-> Select any product.
On the right hand side, click on the button "System Roles"-> Click "Select Product".
Now activate the relevant product as required by clicking on the "Active" checkbox.
Hope this helps!
Regards,
Rinkal

SMD database monitoring for Java MSCS cluster system

Dear All,
We have install SAP netweaver 7.0 EHP1 java stack on oracle 10.2.0.5 with windows 2008 R2 MSCS cluster enviornmant.
now we are configuring SMD
From SMD, while configuring Managed system(JAVA ONLY system)--> database monitoring I am getting following error
DB connection Id :%_SID_virtualhost_SAPSR3DB
Connectivity test :
Database history :This connection could not be tested, thus the DB performance warehouse was not set up
Extractors activation :This connection could not be tested, thus the DB extractors were not set up
Connectivity test details :
Database connection %_SID_virtualhost_SAPSR3DB : SQL error 12505 ORA-12505: TNS:listener does not currently know of SID given in connect descriptor
Database connection :%_SID_virtualhost_SAPSR3DB could not be established
System Details
Solman - SAP EHP 1 for SAP Solution Manager 7.0
managed system - Netweaver 7.0 ehp1AS JAVA(New Installation)
Connection parameters
Database Name: SID
Database Host :virtual host
TNS Name:SID.WORLD
User Name:SAPSR3DB
Password:xxxxxxxxxxx
Tns ping command is also not working when we give host name as virtual host of JAVA system
but when we change it to phyiscal IP address of the cluster server it is working fine.
Could you please let me know any setting need to be done
Sincerely
Paresh

Hi Paresh,
>> Tns ping command is also not working when we give host name as virtual host of JAVA system
but when we change it to phyiscal IP address of the cluster server it is working fine.
>> SQL error 12505 ORA-12505: TNS:listener does not currently know of SID given in connect descriptor
Virtual hostname must be resolved on both hosts while configuring SMD. Otherwise you'll not able to access Oracle Listener.
Best regards,
Orkun Gedik

SMD Error in managed system type PI 7.1 EHP1 Step Logical Ports error

Hi people,
Solution Manager Ehp1 7.0 SPS24
I am currently runnig the wizard setup for managed System, everything is fine but when I run for PI 7.1 I get the following error:
Fri Sep 10 20:29:48 2010 Logical Ports A failure occured while creating the logical port for JAVA XI : PORT_NOT_CREATED
Step Logical Ports Details
A failure occured while creating the logical port for JAVA XI : PORT_NOT_CREATED
!! Exception : PORT_NOT_CREATED
Exceptions
com.sap.mw.jco.JCO$AbapException: (126) PORT_NOT_CREATED: PORT_NOT_CREATED
at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1511)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3980)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3514)
at com.sap.sup.admin.setup.SolManRfcAdapter.createXIlogicalPort(SolManRfcAdapter.java:185)
at com.sap.sup.admin.setup.SetupStep.runExec(SetupStep.java:427)
at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:335)
at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:549)
at com.sap.sup.admin.setup.SapCluster.setup(SapCluster.java:1695)
at com.sap.sup.admin.setup.SapCluster.access$000(SapCluster.java:35)
at com.sap.sup.admin.setup.SapCluster$SetupRunner.run(SapCluster.java:1965)
at java.lang.Thread.run(Thread.java:534)
Any ideas?
Thanks in advance

Hi everyone,
Thanks everyone.
Guilherme, finally I understand what really happens. "Refresh" is not working properly in the Setup Wizard.
First I have done what I can:
System    Type      Managed Products                    Product Instances
DPI           ABAP     SAP Netweaver PI 7.1               Application Server ABAP (I could not select PI at the same time)
DPI           JAVA     SAP Netweaver PI 7.1               Application Server Java + Process Integration
But, when I refresh the browser Internet Explorer appears the following:
System    Type      Managed Products                    Product Instances
DPI           ABAP     SAP Netweaver PI 7.1               Application Server ABAP + Process Integration
DPI           JAVA     SAP Netweaver PI 7.1               Application Server Java + Process Integration
And then I do not get the error anymore. (I have to repeat step 2 in the wizard "Check Prerequisites for Diagnostics)
And If I run transaction SMSY, I can see how PI is mantained since the wizard refresh SMSY.
Product Instance Selection tab:
Application Server ABAP (Flag selected: relevant)
Process Integration (Flag selected: Also Installed, Technical System[ DPI, Java])
Application Server Java (Flag selected: relevant, Technical System[ DPI, Java])
So, if I use this configuration in the SMSY, when I run "solman_setup", configuring DPI (My PI7.1), when I run "Configure Diagnostics", the wizard shows ABAP + PI as expected.
Thanks a lot Guilherme!!

SMD Setup

Hello Guru's,
I have configured solution manager diagnostics on solution manager and installed SMD agent on satellite system (BW). While starting the agents on solution manager both systems are keep dumping with CALL_FUNCTION_NOT_FOUND & CALL_FUNCTION_REMOTE_ERROR errors. I couldnt able to figure out the problem.
Sequence of things done on Solution Manager
1. Change the Backend Client from 001 to 350
2. Deploy the SMD server package (SPS13).
3. Deployment of IS Agent (ISAGENTSMD71*.SCA)
4. Disable Maintenance Mode
5. Run SMD Upgrader
6. SMD Diagnostic Server Setup Wizard
7. Wily Enterprise Manager Installation
8. Install the SAP Management Modules
9. SMD Server Setup Wizard (Monitored System Setup)
10. Connect Managed System to SMD Server
11. SMSY Landscape Definition
Sequence of things done on Solution Manager
1.SMD AGENT Installation
2. Wily Introscope Agent Installation & Configure the Agent on BWS
3. Creating Auto Probe Connector
4. New JAVA VM Parameter on BWS for Auto Probe
5. Setup RFC Destinations to Managed System
ERROR 1:
Runtime Errors         CALL_FUNCTION_NOT_FOUND
Date and Time          12/17/2007 14:05:33
Short text
     Function module "SMD_DATA_LOADER100" not found.
What happened?
     The function module "SMD_DATA_LOADER100" is called,
     but cannot be found in the library.
     Error in the ABAP Application Program
     The current ABAP program "SAPLE2E_FUNC" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.
What can you do?
     Note down which actions and inputs caused the error.
     To process the problem further, contact you SAP system
     administrator.
     Using Transaction ST22 for ABAP Dump Analysis, you can look
     at and manage termination messages, and you can also
     keep them for a long time.
Error analysis
    The program "SAPLE2E_FUNC" contains the CALL FUNCTION statement.
    The name of the function module to be called is "SMD_DATA_LOADER100".
    No function module exists with the name "SMD_DATA_LOADER100".
    All function modules are listed in the Function Library (SE37).
    Possible reasons:
    a) Wrong name specified. Pay particular attention to
       upper/lower case and underscores ("_").
       or
    b) Transport error
    c) In the case of an enqueue/dequeue module,
       the lock object may not have been activated
       (ABAP/4 Dictionary).
How to correct the error
    Check the last transports to the SAP System.
    Is the program "SAPLE2E_FUNC" currently being changed?
    If an enqueue/dequeue module is involved, is the activation
    of the lock object missing in the ABAP/4 Dictionary?
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"CALL_FUNCTION_NOT_FOUND" " "
"SAPLE2E_FUNC" or "LE2E_FUNCU15"
"E2E_ME_RFC"
Function modules with names similar to "SMD_DATA_LOADER100":
SMD_DOWNLOAD
SMSY_DATA_XML_UPLOAD
SAP_OI_LOAD_MIME_DATA
S_AUTH_ROLE_DATA_LOAD
SCPR_TR_READ_DATA_LOBJ
SMD_USAGE_DATA
SMSY_DATA_XML_DOWNLOAD
SMSYAD_GET_DATA_FROM_LCR
SMSYAD_GET_DATA_FROM_LIS
SMSYAD_GET_AC_DATA_FROM_LCR
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
ERROR 2
Runtime Errors         CALL_FUNCTION_REMOTE_ERROR
Date and Time          12/12/2007 13:08:25
Short text
     "Function module "SMD_MDX_QUERY_EXECUTE" not found."
What happened?
     Error in the ABAP Application Program
     The current ABAP program "SAPLE2E_FUNC" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.
     The error occurred during an RFC call to another system.
     In the target system, a short dump has been written as well.
     More detailed information on the error cause can be found there.
What can you do?
     Note down which actions and inputs caused the error.
     To process the problem further, contact you SAP system
     administrator.
     Using Transaction ST22 for ABAP Dump Analysis, you can look
     at and manage termination messages, and you can also
     keep them for a long time.
Error analysis
    An error occurred when executing a REMOTE FUNCTION CALL.
    It was logged under the name "CALL_FUNCTION_NOT_FOUND"
    on the called page.
How to correct the error
    Please refer to the notes described in the
    short dump.
Please help me ASAP....................
Regards,
Ravi.

Hi!
Can you please help me with my issue?
I would like to setup SMD functionality.
I use SAP Solution Manager 4.0 with SP 13.
Here are the steps I already executed:
a) Installation of Wily Introscope Enterprise Server 7.1 (Location: Server of SOLMAN)
b) Deployment if file ISAGENTSMD71*.SCA (Location: Server of SOLMAN)
c) Setup steps on SOLMAN (conf. of at least 3 BTC processes, activation of BI source system, configuration of SLD according to tcode SPRO)
The errors I currently have:
1) Managed Systems Setup
I am about to set up the SMD for the monitored systems via http://server:50000/smd --> Diagnostics Setup --> Managed Systems --> Setup Wizard
Retrieval of selected solutions failed
The contents of at least one solution could not be retrieved from Solution Manager, or could not be uploaded to Diagnostics DB
Server->Server : java.lang.IllegalStateException: Warnings occured during Initial Upload : XML Template parsing generated warnings
Sat Jan 05 16:18:57 CET 2008 | storeHost(...):Host []
serverIP-Adressnull:Cannot insert/update the host
'[IHost: key=119954633765http://... (RC=2)
Do you still want to proceed to next step?
2) Acces to Root Cause Analysis --> Exceptions Error
Logon failed
What has happened?
Call of URL http://server:8000/SAP/BW/BEX terminated due to error in logon data.
Note
Logon performed in system <SID>.
Logon performed for client xxx and language EN.
What can I do?
Check the validity of your SSO ticket for this system.
If you do not yet have a user ID, contact your system administrator.
Error Code: ICF-LE-http-c:666-l:E-T:21-C:6-U:5-P:5-L:3
HTTP 401 - Unauthorized
My questions:
- Which additional settings for SDM setup (on SOLMAN and on the site of satellite systems) should be done?
- How can the errors (see above) be fixed?
- Should some additional SLD configurations be executed for the monitored systems?

SMD setups end with http error.

Dear All,
I am running SMD setup for our java system.
All the steps success full exept the HTTP one
we got below error.
A problem occured while updating log formatter type, please check log formatter : service_dsr_format_trc is of type TraceFormatter
Step Http Details
Http Log settings failed : a failure occured while updating Http service properties
Failed to update http service logs settings : null
A problem occured while updating HTTP access log levels
Failed to check or set Http log levels : Unable to connect to connector server.
A problem occured while updating log formatter type, please check log formatter : service_dsr_format_trc is of type TraceFormatter
Failed to check or set log formatter 'service_dsr_format_trc' : Unable to connect to connector server
===============
Step Http Details
Http Log settings failed : a failure occured while updating Http service properties
Failed to update http service logs settings : null
A problem occured while updating HTTP access log levels
Failed to check or set Http log levels : Unable to connect to connector server.
A problem occured while updating log formatter type, please check log formatter : service_dsr_format_trc is of type TraceFormatter
Failed to check or set log formatter 'service_dsr_format_trc' : Unable to connect to connector server.
Exceptions
com.sap.engine.services.jmx.exception.JmxConnectorException: Unable to connect to connector server.
at com.sap.engine.services.jmx.connector.p4.P4ConnectorClient.<init>(P4ConnectorClient.java:96)
at com.sap.engine.services.jmx.connector.p4.ConnectorFactory.getJmxConnector(ConnectorFactory.java:31)
at com.sap.jmx.remote.JmxConnectionFactory.getConnector(JmxConnectionFactory.java:191)
at com.sap.engine.services.adminadapter.impl.ManagementInterfaceProxyFactoryImpl.<init>(ManagementInterfaceProxyFactoryImpl.java:51)
at com.sap.smd.agent.plugins.remotesetup.LogConfiguratorAdapter.updateLogFormatterType(LogConfiguratorAdapter.java:135)
at com.sap.smd.agent.plugins.remotesetup.SetupManager.updateLogFormatterType(SetupManager.java:351)
at com.sap.smd.agent.plugins.remotesetup.RemoteSetupStep.setupHttp(RemoteSetupStep.java:278)
at com.sap.smd.agent.plugins.remotesetup.RemoteSetupStep.execute(RemoteSetupStep.java:119)
at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:549)
at com.sap.smd.agent.plugins.remotesetup.RemoteSetupService._setup(RemoteSetupService.java:171)
at com.sap.smd.agent.plugins.remotesetup.RemoteSetupService.setup(RemoteSetupService.java:88)
at com.sap.smd.agent.plugins.remotesetup.RemoteSetupServicep4_Skel.dispatch(RemoteSetupServicep4_Skel.java:112)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:330)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java:721)
at java.lang.Thread.run(Thread.java:664)
Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during getInitialContext operation. No server is running. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:494)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:363)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorClient.<init>(P4ConnectorClient.java:69)
... 15 more
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContextExt.<init>(RemoteLoginContextExt.java:34)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:81)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:355)
... 20 more
Caused by: java.net.SocketException: Software caused connection abort: recv failed
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at com.sap.engine.services.rmi_p4.Connection.run(Connection.java:374)
... 1 more
please let us know any thing is missing from our end.
Thanks in advance.
Paresh

Hi experts,
The error is because of the Privacy settings in Internet explorer.
we did the following settings in inter net explorer
Tools -> Internet Options ->Privacy->High.
Rergards
Naveen

SMD Setup - saposcol problem

Hello Gurus,
We have done the SMD and willy setup for our MDM system (Non Abap).
The problem we are facing is saposcollector data is not visible in willy web view.
While looking into the agent application log we see following error
"Warning com.sap.smd.wily.hostagent.action.AbstractAction - run(): Action SAPOsCol not running because status is PERMANENT_ERROR"
We are using solman system 7.0 EHP1, SMD Agent 7.01, MDM system 7.1. Saposcol verion 700 patch-159 64 bit.
Need your help to resolve the issue related to oscol and have the oscol data available in willy webview.
Regards
Manoj

Hi Manoj,
please keep in mind that the saposcol on the satellite system and the saposcol of the SMD Agent on the same sattelite system has to be synchronized.
It means you should have the same version, the lastest one, on the satellite system. You do not need to change the version of saposcol on SMD server.
After changing the version of saposcol of the SMD Agent, you have to restart the agent or reboot the applications via SMD -> Diagnostics Administration -> Managed System -> Agent Administration, click on the corresponding SMD agent and select Reboot Agent.
Please check also that the management modules not based on an old version:
In general there are 2 possibilities:
1. Upgrade the Management Module
2. Upgrade of the entire Enterprise Managers
Regards,
Shyam.

Upgrade to SAP BPC 7.0 with cluster system (Front-End & Back-End)

Hello,
I have to do an upgrade document about an outlooksoft 5.0 SP2 to SAP BPC 7.0 SP4 in a cluster system.
It has 2 front-ends (IIS cluster windows) & 2 back-ends (SQL Cluster).
We are going to do first the migration in 1 node, and then in another. The first upgrade in the first node I understand. I uninstall outlookdoft 5.0, install SAP BPC 7.0 SP4 and then restore the backup of the Appset, and do the posts upgrade action of the Dimension TIME.
But in the second, what do we do??? I uninstall outlookdoft 5.0, install SAP BPC 7.0 SP4 and then what??? Do I have to restore the backup of the Appset again???
I need help.
Best regards.
Pablo Mortera.

Hello,
On the second cluster node, you have only to install the software, nothing related to the appset. If you alreay run the migration stepts for the appset, all the information are into daatbase and file server.
However, the normal behaviour is to make the installation on the both nodes, make the basic tests to validate the installation and then proceed with the appset migration.
Best regards,
Mihaela

How to setup the cluster environment for BPM using weblogic

want to setup the cluster environment for BPM using weblogic....
i have installed the oracle weblogic server 10gr3 and oracle BPM enterprise for weblogic 10gR3
i have used the Admin tools from the "oracle BPM enterprise for weblogic" to setup the configuration and create the weblogic domain servers.
i can launch the process administrator and import the project exp file to domain server.
but what should i do to setup cluster environment using weblogic?
what i want to do is :
setup one admin machine..
setup two product machine..
enable the cluster so the admin machine can monitor the status of the product machine..
thanks a lot ...

The install guide at http://download-llnw.oracle.com/docs/cd/E13154_01/bpm/docs65/config_guide/index.html gives a reasonable amount of info on how to do this.
Personally I have not used the OBPM option to configure WebLogic instead I've used the information in the above install guide to create the weblogic domain in advance of configuring OBPM.
Once you've setup WebLogic configure OBPM using the values I mention in the following thread: How to set the JMX Engine parameter in Process Administation?
Let me know any specific config questions and I'll do my best to answer them for you.
Thanks,
Mike

PI 7.0 Java stack config of the stand-alone server to new cluster system

Hi colleagues,
we have a PI installation in stand alone server (SAP with abap +
java and Oracle in the same server)
The system number of the ABAP stack is 00, and we are conecting to the
Java stack to the for example the URL
http://hostname:50000/rep/start/index.jsp
We have installed a new PI in a MSCS and in some weeks, we´ll have to
copy the database and configuration of the stand-alone server to the
new cluster system. In the SAP PI installation on the MSCS, we have
confirmed that with the ABAP stack, we won´t have any issue because the
ASCS has the system number 00 (message server), so we only have to
install a SAP system in each nodes without care these new system
numbers because we are configuring a Logon group but the question is in
the Java stack... The SCS (service in the cluster) has the 01 system
number...
What is the best way to keep the same URL to the Java stack that in the
stand-alone server? (remember:
http://hostname:50000/rep/start/index.jsp )
Have we to install a Webdispatcher in the MSCS and one Java stack in
each node of the cluster? we think that is right but we have a lot of
doubts about the URL, the files of the Java (if they are stored in
local disk in one node, how are they replicated to the second node?)
and so on....
Could you give us any suggestion to make the "migration" from the stand-alone to a cluster in a transparent way for the users?
Thanks in advanced and kind regards !!
Victor

Thanks a lot.
For information
Our central SLD is on a standalone system
However slave SLD (to ensure autonomy and HA for production XI system) will be deployed on Java separated hardware system of Xi production system.
On master SLD all systems are described and all machine are linked with it (SLDAPICUST) except production XI one
On slave SLD, all data of master one are replicated and only XI system is linked with (SLDAPICUST)

How to setup a Cluster of 3 servers on weblogic 9.2?

I'm trying to setup a cluster of 3 servers on WebLogic 9.2 on one physical computer.
I managed to startup 3 servers from cmd in windows like this:
startmanagedweblogic BiPublisher1 http://127.0.0.1:7101
startmanagedweblogic BiPublisher2 http://127.0.0.1:7101
startmanagedweblogic BiPublisher3 http://127.0.0.1:7101
Now I can open each of the 3 servers directly from my browser:
http://127.0.0.1:8101/xmlpserver
http://127.0.0.1:9101/xmlpserver
http://127.0.0.1:9501/xmlpserver
My questions are:
How to setup servers so that I can start them automatically from administration console?
How to configure address in administration console through which I will open my application in a browser?
And after that, how to configure that when server on which I work breaks, it automatically restarts application in another server (no need for failover because BI Publisher does not support session replication, I think)?
Do I need machine and virtual host, and what is their purpose? Node manager? Can somebody explain those things? What i did wrong?
I made this in administration console:
Administration console:
SERVERS:
AdminServer:
Name: BIPublisherServer
Listen address: 127.0.0.1
Listen port: 7101
Server1:
Name: BIPublisher1
Machine: tp43
Cluster: BiPublisherCluster
Listen address: 127.0.0.1
Listen port: 8101
Server2:
Name: BIPublisher2
Machine: tp43
Cluster: BiPublisherCluster
Listen address: 127.0.0.1
Listen port: 9101
Server3:
Name: BIPublisher3
Machine: tp43
Cluster: BiPublisherCluster
Listen address: 127.0.0.1
Listen port: 9501
CLUSTERS:
Cluster: BiPublisherCluster
Multicast Address: 237.0.0.101
Multicast port: 8050
VIRTUAL HOSTS:
Name: bicluster
Virtual Host Names: 127.0.0.1
Targets: Clusters: BiPublishercluster: All servers in the cluster
MACHINES:
Name: tp43
DEPLOYMENTS:
Name: xmlpserver
Path: C:\BiPub\xmlpserver.war
Targets: Virtual Hosts: bicluster

You have some reading to do to increase your familiarity with cluster / managed servers.
How to setup servers so that I can start them automatically from administration console?Add the 3 servers into your cluster. Use the cluster to start and stop all 3 servers from within the console instead of starting / stopping each server individually.
How to configure address in administration console through which I will open my application in a browser?You'll need some sort of load balancer to direct traffic so that the end user doesn't have to know the server/port combinations. Apache + Weblogic plugin for instance, but I don't think you'll be keeping all 3 instances on the same physical machine as your production design.
And after that, how to configure that when server on which I work breaks, it automatically restarts application in another server (no need for failover because BI Publisher does not support session replication, I think)?Target your application to "All servers in the cluster". You should have your managed instances on separate physical machines since your current configuration is vulnerable to a single machine failure which would shutdown all 3 instances.

Need detail information, steps would be nicer, to upgrade from Exchange 2003 to Exchange 2010 to setup in test system first then try on production, since not much room for downtime, thanks bekir

Need detail information, steps would be nicer, to upgrade from Exchange 2003 to Exchange 2010 to setup in test system first then try on production, since not much room for downtime, thanks bekir

Hi,
Overview of the upgrade progress from Exchange 2003 to Exchange 2010 including the following steps:
Installing Exchange 2010 within your organization on new hardware.
Configuring Exchange 2010 Client Access.
Creating a set of legacy host names and associating those host names with your Exchange 2003 infrastructure.
Obtaining a digital certificate with the names you'll be using during the coexistence period and installing it on your Exchange 2010 Client Access server.
Associating the host name you currently use for your Exchange 2003 infrastructure with your newly installed Exchange 2010 infrastructure.
Moving mailboxes from Exchange 2003 to Exchange 2010.
Decommissioning your Exchange 2003 infrastructure.
For more details, please refer to this following document.
http://technet.microsoft.com/en-us/library/ff805040(v=exchg.141).aspx
Best Regards.

SQL Error 0 during DBACockpit setup in Managed System Configuration

Hi All,
I'm getting SQL Error 0 during DBA Cockpit setup in Managed system configuration. I'm trying to connect MsSQL 2005 from Linux system(Solution Manager 7.1 SP10). I have installed necessary ODBC and microsoft drivers. Any suggestions will be appreciated.
Regards,
Pragadees

If I've understood you correctly, you are trying to setup a remote database connection from an SAP Solution Manager system running on Linux with a database which is NOT MSSQL to a database which is MSSQL running on Windows.
In that case have you checked these SAP notes ?
1265134 - DBA Cockpit: Connecting a remote database
1388700 - SolMan 7.0 EHP1 Database Warehouse for MSSQL
Regards
RB

Problem of setuping a source system in bi 7.0

Dear All,
I'm now using BI 7.0, and when I wants to setup a souce system in the folder SAP, I found a problem. The system appears in BI folder with a strange icon. I don't know why, can anybody explain it and give a solution?
Thanks a lot.

I've searched sap notes and found , I should import support package 01 into BI, however, I've imported support package 09....Why

SMD Setup on Cluster System

Similar Messages

Maybe you are looking for