Portal dialog instance questions

Dear SDN,
2 questions on installing a dialog instance for the portal.
1. Does the dialog instance need to have a a different instance number than the central instance if it is on a separate physical host
2. Can you log onto the portal from the dialog instance?
dialog inst # = 3
Ci inst # = 1
i.e. http://dialoghost:50003/irj?
Thanks

Prakash Singh wrote:"No if the dialog instance is not on the same machine. 2. Yes you should be able to logon to portal from dialog instance. http://name of your dialog instance server: port/irj"
The above statement is accurate, because any SAP instance is uniquely identified by its hostname and its instance number. So, on the same host you must have a different instance number for your SAP instance and on multiple hosts you could run an SAP instance with the same instance number as your central instance.
Regards,
Phani.

Similar Messages

Slow portal login on Dialog instances

Hello.
We are having issues with our portals in the sense that it is taking users up to two minutes to login to our portal system. The long login times seem to only happen on our "dialog servers", and the central instance logs in fine and fast.
Furthermore, after the users login to the system (either DI or CI), the system runs fast, and performs well,,, it is just the login that is taking a considerable amount of time.
1. The only the portal dialog instances (app servs) are slow.. the central instance is fast when loggin in.
2. This seems to only affect users logging in from the active directory. Users such as "administrator" login fast.
Has anyone experienced this before? Any advice or suggestions would be greatly appreciated.
Thank you
Praveen

Hi Praveen, facing the same situation. I´ve noticed that if the user is involved in any role with R/3 ivies , such as ESS, MSS or PS/PLM roles, the performance is really poor as you say and the behaviour is exactly the one you have described.
Now I´m looking for some strange and hide parameter used in the system definition of my R3 systems inside the portal.... it seems that the portal is checking one by one all the iviews with an external R3 connection before it open....
Please, if you find the solution, help me!!

Installing Java Dialog Instance - Error while connecting to DB

We would like to add a dialog instance to our production Portal server. We installed Portal as stand-alone on the central instance. We have another server we would like to setup to serve as a Portal dialog instance.
So far I have installed Windows 2003 Server Standard. Installed MSSQL server client tools (database is mssql server). Installed jdk 1.4.62. Set java home and path environmental variables. I'm now installing the Java dialog instance (I can't find any documentation on this). From Netweaver installation CD> SAP NetWeaver '04 Support Release 1> Java System> MS SQL Server> Dialog Instance Installation>
SAP System ID: (sid) ES2
Central Host: SAPEPS02
Path to JAVA DVD supplied> JDK Directory confirmed> Domain paramaters confirmed> domain<sid> account passwords supplied> domain<service><sid> account password supplied> Instance number confirmed>
Installation started> It gets to step 8 and fails stating "Error while connecting to DB". I looked through all the log files and couldn't come up with anything (i'm very thorough).
I tried adding the users to the database as dbowners (no luck). I installed SQL server 2000 with SP4. No where during this installation did I get prompted for database parameters?
Is there something basic i'm missing? Does this scenario not work? Any help would be greatly appreciated. Pointing me in the right direction of the correct documentation would also be appreciated. Thank you in advance.
Sincerely,
Brad Dridi

Hi Brad,
I am facing the same problem. I hope by now you must have got the solution for this.
Can you please let me know how did you overcome this situation?
Thank you!!
Regards,
Abhijeet Bhagat

Dialog Instances in remote locations

Hello,
we have a couple of remote locations where the response time of the portal is rather high.
Has anyone ever tried having a portal dialog instance in a remote location with rather slow WAN connection and could let me know if that improved things a bit?
Regards,
Andi

Ah - now you mention webdynpros, you could probably do that yes as they just make RFC calls. I would probably set up a separate portal (or webdynpro) system at the remote location. If you did a remote portal, you could have webdynpro on it and federate it into the main portal for any other content.
Paul

Question about SSO (for Java Dialog instance) for Portal EP 6.0 SP 20

Hi All
I have following question.
We are running Portal 6.0 SP 20. We have JAVA (Portal) CI+DB running on single host SAPQP1 and Two JAVA Dialog Instances (J2EE Application servers) running on separate host namely SAPAP35 and SAPAP36.
I was able to configure SSO between SAPQP1 (CI+DB) and ECC R/3 system (QC1). SSO is working fine. Users can access all ESS/MSS data in portal when they use Portal URL running on SAPQP1 (http://sapqp1.xxxxx.com:50000/irj).
But when users try to access ESS/MSS data via portal (URL) running on SAPQP35 (http://sapap35.xxxxx.com:50000/irj) and SAPAP36 ((http://sapap36.xxxxx.com:50000/irj) SSO does not work, i.e it system asks user id and password.
So , how I can configure SSO between SAPAP35 and SAPAP36 JAVA Dialog instances and ECC R/3?

Hi Sandip,
obviously you already configured QC1 to accept Tickets issued by the Java Engine on SAPQP1. Did you imported the public (java) certificates from SAPAP35 and SAPAP36 into your ECC System? The certicficates need to be added in client 000 to your System PSE and in your production client to your ACL.
Regards,
Enno

Dialog instance for portal installation error in db2 linux

Dear all,
i am installing a dialog instance for the exsisting portal server for the load balancing .while installing i am facing the following error.
SAPINST_DEV.log is as follows
TRACE 2011-08-17 12:17:39.380
NWException thrown: nw.configError:
Java EE Engine configuration error. DIAGNOSIS: See output of logfile batchconfig.log: '
Warning : /usr/sap/ESP/SYS/global/db6/jdbc/db2jcc.jar file stated but does not exist !
Warning : /usr/sap/ESP/SYS/global/db6/jdbc/db2jcc_license_cu.jar file stated but does not exist !
Can not get DB connection. Batchconfig will only be able to execute offline tasks. '.
TRACE 2011-08-17 12:17:39.380
Function setMessageIdOfExceptionMessage: nw.configError
WARNING[E] 2011-08-17 12:17:39.381
 CJSlibModule::writeError_impl()
CJS-30059 Java EE Engine configuration error. DIAGNOSIS: See output of logfile batchconfig.log: '
Warning : /usr/sap/ESP/SYS/global/db6/jdbc/db2jcc.jar file stated but does not exist !
Warning : /usr/sap/ESP/SYS/global/db6/jdbc/db2jcc_license_cu.jar file stated but does not exist !
Can not get DB connection. Batchconfig will only be able to execute offline tasks. '.
TRACE 2011-08-17 12:17:39.381 [iaxxejsbas.hpp:483]
 EJS_Base::dispatchFunctionCall()
JS Callback has thrown unknown exception. Rethrowing.
TRACE 2011-08-17 12:17:39.398 [syuxctask.cpp:1382]
 CSyTaskImpl::start(bool)
A child process has been started. Pid = 7072
TRACE 2011-08-17 12:17:39.435 [syuxctask.cpp:1382]
 CSyTaskImpl::start(bool)
A child process has been started. Pid = 7073
ERROR 2011-08-17 12:17:39.718 [sixxcstepexecute.cpp:951]
FCO-00011 The step runBatchconfig with step key |NW_DI|ind|ind|ind|ind|0|0|NW_DI_Instance|ind|ind|ind|ind|10|0|runBatchconfig was executed with status ERROR .
TRACE 2011-08-17 12:17:39.727 [iaxxgenimp.cpp:752]
 CGuiEngineImp::showMessageBox
<html> <head> </head> <body> An error occurred while processing service SAP NetWeaver 7.0 Support Release 3 > Software Life-Cycle Options > Application Server > IBM DB2 for Linux, UNIX, and Windows > Dialog Instance. You may now <ul> <li> choose Retry to repeat the current step. </li> <li> choose View Log to get more information about the error. </li> <li> stop the task and continue with it later. </li> </ul> Log files are written to /tmp/sapinst_instdir/NW04S/LM/AS/DB6/DI. </body></html>
TRACE 2011-08-17 12:17:39.727 [iaxxgenimp.cpp:1255]
 CGuiEngineImp::acceptAnswerForBlockingRequest
Waiting for an answer from GUI
SAPINST.log error
INFO 2011-08-17 12:17:36.946
Creating file /tmp/sapinst_instdir/NW04S/LM/AS/DB6/DI/batchconfig.log.
INFO 2011-08-17 12:17:36.971
Output of /opt/IBMJava2-amd64-142/bin/java -classpath /tmp/sapinst_instdir/NW04S/LM/AS/DB6/DI/install/sharedlib/launcher.jar -Xmx256m com.sap.engine.offline.OfflineToolStart com.sap.engine.configtool.batch.BatchConfig /usr/sap/ESP/SYS/global/security/lib/tools:/tmp/sapinst_instdir/NW04S/LM/AS/DB6/DI/install/lib:/tmp/sapinst_instdir/NW04S/LM/AS/DB6/DI/install/sharedlib:/usr/sap/ESP/SYS/global/db6/jdbc/db2jcc.jar:/usr/sap/ESP/SYS/global/db6/jdbc/db2jcc_license_cu.jar /tmp/sapinst_instdir/NW04S/LM/AS/DB6/DI/BatchConfig.xml is written to the logfile batchconfig.log.
WARNING 2011-08-17 12:17:39.377
Execution of the command "/opt/IBMJava2-amd64-142/bin/java -classpath /tmp/sapinst_instdir/NW04S/LM/AS/DB6/DI/install/sharedlib/launcher.jar -Xmx256m com.sap.engine.offline.OfflineToolStart com.sap.engine.configtool.batch.BatchConfig /usr/sap/ESP/SYS/global/security/lib/tools:/tmp/sapinst_instdir/NW04S/LM/AS/DB6/DI/install/lib:/tmp/sapinst_instdir/NW04S/LM/AS/DB6/DI/install/sharedlib:/usr/sap/ESP/SYS/global/db6/jdbc/db2jcc.jar:/usr/sap/ESP/SYS/global/db6/jdbc/db2jcc_license_cu.jar /tmp/sapinst_instdir/NW04S/LM/AS/DB6/DI/BatchConfig.xml" finished with return code 183. Output:
Warning : /usr/sap/ESP/SYS/global/db6/jdbc/db2jcc.jar file stated but does not exist !
Warning : /usr/sap/ESP/SYS/global/db6/jdbc/db2jcc_license_cu.jar file stated but does not exist !
Can not get DB connection. Batchconfig will only be able to execute offline tasks.
WARNING[E] 2011-08-17 12:17:39.381
CJS-30059 Java EE Engine configuration error. DIAGNOSIS: See output of logfile batchconfig.log: '
Warning : /usr/sap/ESP/SYS/global/db6/jdbc/db2jcc.jar file stated but does not exist !
Warning : /usr/sap/ESP/SYS/global/db6/jdbc/db2jcc_license_cu.jar file stated but does not exist !
Can not get DB connection. Batchconfig will only be able to execute offline tasks. '.
ERROR 2011-08-17 12:17:39.718
FCO-00011 The step runBatchconfig with step key |NW_DI|ind|ind|ind|ind|0|0|NW_DI_Instance|ind|ind|ind|ind|10|0|runBatchconfig was executed with status ERROR .
kindly help on this issue.
Regards
Revantha Vishnu

> Java EE Engine configuration error. DIAGNOSIS: See output of logfile batchconfig.log: '
What do you see in that log?
Markus

EP Central System + Dialog Instance Installation options

Hi Friends
For my production EP 6.0 WAS 6.40-Java instance I am getting 3 AIX servers, say server DBserver, Appserver1 & Appserver2, we want to install the database & CI on the DBserver, the other 2 servers need to serve the role of Application servers to the DB+CI server.
In our SAP R/3 Production systems we don't allow the users to login to the server hosting the (database+CI) & we allow them to login only to the appication servers, I want to do a similar setup for my Production portal landscape & require that the portal users are load-balanced using the SAP Web Dispatcher to the 2 application servers.
I have 2 questions on which installation options to choose to achieve the above objective.
1. Can somebody check & confirm if the below mentioned Installation sequence is correct for Installing the WAS on the 3 servers.
a) Using Installation option "Java System ->Oracle->Central System->Custom Installation-Java system" for the DBserver.
b) Installation option "Java System ->Oracle->Central System->Dialog Instance Installation" for Appserver1 & Appserver2.
2. Can somebody advice how do I need to install the portal on the 3 servers so that the above objective of load-balancing the users to the 2 App servers is met.
a) Do I need to install portal only on the DB+CI server & then the portal platform will be setup on the 2 App servers as well or
b) Can I install the portal separately on the 2 portal App servers.
Thanks & Rgds,
Abhishek

Hi Friends
Any replies will be appreciated & also rewarded with points.
Thanks & Rgds,
Abhishek

WAS or Dialog instance in DMZ zone

Hello All,
Please clarify me by answering the following question.
I have a plan to use the erecuting functionality without Portal system and have plans to use this functionality outside the intranet. ( Note : Not planned to move the back end system to DMZ zone)
So kindly suggest me with your valuable points.
The options which we have are.
1. Installing WAS 7.00 engine in DMZ zone and Using this ICM in Erecruting system (back end) by changing the ICM host parameter
2. Installing Dialog Instance and requesting all the erecruting request will send to dialog instance which will be placed in DMZ zone.
Will the above 2 option will work out for my case? Looking for your suggestions
Vijay

hi,
to install an application server in DMZ, confirm that you will get the port 445 open.
The TCP port 445 is required to access the sapmnt directory, which contains u201CSAP profilesu201D.
or,
alternative you place an application server lan which will communicate to CI and reverse proxy server (in DMZ)
request flow:
Internet>reverse proxy->application server--->Database server.
-gokul

ADS in the Java stack of a Dialog instance on Windows + CI on iSeries

Hi,
I read the document "Using Adobe Document Services with SAP on IBM DB2 for i5/OS".
Summary of the document -
There are two possible technical scenarios:
1. ADS in the Java stack of a Dialog instance on Windows
1.1. ABAP+Java dialog instance on Windows
1.2. Java dialog instance on Windows
2. ADS in a SAP system on a supported platform
2.1. ABAP+Java central instance on Windows/Unix
2.2. Java central instance on Windows/Unix
The document recomammeds technical scenario 1, that is, install a Windows Dialog instance.
Choosing an ABAP+Java or Java system depends on the usage scenario for Interactive Forms:
- Interactive PDF use: Java mandatory, ABAP+Java possible
- Interactive use in SAP Maanger Self_Services/batching of forms:
ABAP+Java mandatory but Note 993612 describes the status for NW04s SP12 onwards.
End of summary -
Our prefered rechnical scenario is: "1.2. Java dialog instance on Windows" to minimice resources.
Our usage scenario for Interactive Forms includes "SAP Manager Self- Services".
Our interpretation of note 993612 is that we do not need double stack installation. Could you confirnm this ?.
If yes, we are going to install a Java Dialog instance on Windows connected to our Java Central instance on iSeries (our SAP Portal system) to use ADS.
Best regards.

Hello Torrell,
your statements sound reasonable, also including SAP Note 993612.
To decide, though, whether a single stack would be enough (especially based on the aforementioned note), you will need the advise of an ADS application expert (or someone else who has implemented your scenario, independent of the platform).
I thus assume that you will not get an answer in this forum. Your question is ADS application specific.
When you know for sure that a single stack will be enough, your approach to use a Windows dialog instance will be fine.
Best regards, Barbara

How to Install a Dialog Instance on NT server which CI is running on Unix

Dear expert:
Recently, we wanna add new dialog instance for our production system, but only one NT server can be used. Our SAP version is ECC6.0 SR3 and it's CI is running on HPUX 11.31. steps below:
1. I have configed the SAMBA with shared /sapmnt -> /usr/sap. Also from NT side this directory can be accessed.
2. I have add the <SID>adm and SAPService<SID> into SAMBA for access this directory with read and write rights.
3. I installed the DI on NT server with x86 master.(our NT is windows 2003 x64 SP2)
4. during the installation, the Master needs a directory named 'saploc' ( I think this should be only for NT with CI has this shared directory name, but no idea how to make this also in UX, so i create a new directory in UX named saploc and also share it). Is this normally?
5. At the end, the DI in NT can not be running normally..first is dispwork.exe can not running. After I change the rights for 'saploc' in ux, the dispwork is running but can not connected to message server.
6. I have updated the kernel for DI and make sure both the DI and CI has same version 236.
7. After that , the disp+work.exe can never been running anymore
8. I reboot the NT server try to fix this issue. but too bad! after reboot, I can not even start the DI from SAPMMC! with error 'permission deniedu2018..
My question:
1. do any one of yours has such experiences before? I mean install app server on different OS system.
2. Is that possible for SAP ECC6.0 SR3, since I know that lots of successful storys for 46C or 470
3. If it is possible.. how to ....
Hope yous can give me some suggestions!
Regards
Ethern

Hi my friend
Did you check note 680617? Sorry I don't have hands on experience for this matter but I'm quite sure it's doable and fully supported.
Here's the checklist I can imagine:
1. release the /usr/sap directory as SAPMNT -- you already did and made sure it can be accessed from NT server
2. edit DEFAULT.PFL in the profile directory and add the parameter SAPGLOBALHOST to it -- you didn't indicate
3. have your target X86_64 kernel directory ready on CI HPUX host -- you didn't indicate but you did finish the DI install
4. use SAPPAD to edit DI profile
5. optional steps for oracle
Please let me know what progress you have there.
Thanks,
Effan

Dialog instance installation procedure.

Hi
We are planning to install a new dialog instance to our production system in a seperate host(A new server).
The normal way of doing is to initiate SAPINST tool on the new server and install just the dialog instance and club this with the main central instance.
But the client wants to do in a different way, by creating directories on the central host itself for the new app server....Like if X50 is central instance and X51 & X52 are application server located in the CI itself. And now we create X53 and all the subdirectories and mount the whole directory to the new host.
Here are my questions...
1. Is this advisable way of doing?
2. Where does a Java instance directory is located? Dont we have J2ee directory on each instance wether its CI or DI?
3. Can anyone let me know the directory structure of a dialog instance?
Thanks
Subbu

Hello,
You would need to rn SAPINST on app servers too.
However what you can do is create a share /sapmnt/SID/
/sapmnt/SID should have the following sub dirs.
/sapmnt/SID/exe
/sapmnt/SID/global
/sapmnt/SID/profile
by sharing these directory, you can keep your Kernel centrallly located and de-risk the Kernel upgrades.
Also profiles are maintained centrally.
And this config is supported by SAP.
Regards,
Siddhesh

Dialog Instance Installation - Error while connecting to DB

Hi All,
We have installed a WAS 640 SP15 and successfully running a Portal EP6.0 (SP15) on the same. Now, we wish to install a dialog instance on the same for load balancing the Portal on the same Hardware/Server.
During the DI installation in the phase "Configuring J2EE Engine", the installation fails with the error "Error while connecting to DB".
I tried to restart the installation by replacing the JDBC and OS_LIB of the new instance with the JDBC and OS_LIB of the already running CI instance but it didnt help either.
Any pointers in this direction will be appreciated.
Thank you!!
Regards,
Abhijeet

We have the same issue. We have a NW04 SP19 J2EE standalone WAS and are using the SP19 SAPINST to add a second dialog instance on the same host as the central instance.
We restarted the Oracle listener ... to no avail
The error in the Oracle batchconfig log is given below.
Thanks for any insight that you can provide.
Cheers .... Bart
com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.
 at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection
(DBConnectionPool.java:360)
 at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:125)
 at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>
(PersistenceHandler.java:38)

J2EE Engine cannot be started. SAP CRM EHP1 Dialog Instance Installation

Hi All,
During Installation of a DI on a Linux host, I encounterd a problem. An error occured during " start dialog instance". The ABAP enginee is started successfully where as the JAVA Enginee cant be started. During investigation I found from the log directory
..j2ee/cluster/server0/log as stated below ..
#1.#0050569F663E001E0000000C0000054F0004803004D18B3F#1266843634469#com.sap.engine.core.service630.container.ServiceRunner##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_64##0#0#Error#1#/System/Server#Java###Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
[EXCEPTION]
#1#com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: null
 ume.db.connection_pool_type=SAP/BC_UME
 ume.db.connection_pool.j2ee.xatransactions_used=false
 ume.db.connection_pool.j2ee.is_unicode=false
 ume.db.connection_pool.j2ee.oracle_native_driver_used=false: (No text available)
 at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)
 at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
 at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
 at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
 at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
 at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:83)
 at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:109)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: null
 ume.db.connection_pool_type=SAP/BC_UME
 ume.db.connection_pool.j2ee.xatransactions_used=false
 ume.db.connection_pool.j2ee.is_unicode=false
 ume.db.connection_pool.j2ee.oracle_native_driver_used=false: (No text available)
 at com.sap.security.core.persistence.datasource.imp.DataBasePersistence.init(DataBasePersistence.java:887)
 at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:440)
 at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
 at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
 at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
 at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)
 at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)
 ... 6 more
#1.#0050569F663E001E0000000E0000054F0004803004D18C49#1266843634469#com.sap.engine.core.Framework##com.sap.engine.core.Framework#######SAPEngine_System_Thread[impl:5]_64##0#0#Fatal#1#/System/Server/Critical#Plain###Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.#
I checked with the env variable and parameter, it all looks good. If anybody finds the same issue please suggest ....
Thanks in Advance.
Regards,
Shashi

There is a troubleshooting topic for this on the Help Portal.
See http://help.sap.com/saphelp_nw70ehp1/helpdata/en/20/361941edd5ef23e10000000a155106/frameset.htm.
-Michael

Installing 620 SAP_BASIS Dialog Instance with 6.40 Installation Master CD

Greetings,
At present we have a SAP R/3 Enterprise 47x200 which is dsitributed across two (windows 2003) clustered servers, one for the Central Instance and other for the Database (Oracle 9.2.0.5).
Now and due to perfomance issues on the Central Instance we'd lke to add a Dialog Instance and here is where the doubts come up.
Our SAP_BASIS version is 620 (System -> Status) whereas our SAP Kernel level is 640_REL (SM51).
We have the original 6.20 Kernel CD but we don't have any valid SAP Installation Master CD (originally we made an upgrade from a 4.6B version) so I downloaded from service.sap.com/support the 51033746_13.ZIP (Installation_Master_6.20_6.40_06_08) file (I didn't found any other file better that this one).
The first problem is that when I start sapinst.exe it ask (CD Browser Dialog) for a SAP 6.40 Kernel CD and not the 6.20 Kernel CD I already have. I have found a workaround editing LABEL.ASC file but I think it isn't a good practice.
If I download the Kernel 6.40 from service.sap.com 51030763_1.ZIP (DVD_NW04_SR1_6.40_SAP_Kernel_Oracle) the Sapinst application works perfectly, but here comes up our doubts...
- Could be any problem using these 6.40 installation (Master Installation & Kernel) files for a Dialog Instance installatio in our environment? Are there other installation files which could fit better than these one? Where could I find them?
- When I install a Dialog Instance, does it make changes into the Database Server and Central Instance?
- Initially we'd like to install the Dialog Instance in a test Server, try it, check that it works as we expect, and discard it in order to buy a big and powerful server where we'll definitely install the Dialog Instance. In this case, can we simply discard the test server or we have to follow a complex process for uninstall it? (this question is somehow related to the previous one).
Any help would be greatly appreciated. Thanks in advance.
Javier

Hi,
it is OK that you have 640 kernel even if your BASIS is 620. 620 kernel is no longer supported by SAP.
- Could be any problem using these 6.40 installation (Master Installation & Kernel) files for a Dialog Instance installatio in our environment? Are there other installation files which could fit better than these one? Where could I find them?
You master DVD is correct
- When I install a Dialog Instance, does it make changes into the Database Server and Central Instance?
It does not make any changes to DB, you will see next Dialog instance in SM51 then
- Initially we'd like to install the Dialog Instance in a test Server, try it, check that it works as we expect, and discard it in order to buy a big and powerful server where we'll definitely install the Dialog Instance. In this case, can we simply discard the test server or we have to follow a complex process for uninstall it? (this question is somehow related to the previous one).
You can discard your dialog instance without following special procedures.

Dialog Instance Host Name

Hi,
I am having a problem in SM51 where the dialog instance host name is the same as the central instance host name.
Server Name     Host Name     Message Types                          Server Status
HHA55_ECP_00     HHA55          Dialog Batch Update Upd2 Spool ICM J2EE       Active
HHA56_ECP_00     HHA55          Dialog Batch Update Upd2 Spool ICM J2EE       Active
We have a central instance and a dialog instance installed on seperate nodes in a HA cluster. This problem only happens when the message server runs on the primary node. When the message server is failed over to the node where the dialog instance runs the hostname for HHA56_ECP_00 is HHA56 which is correct. This is effecting load balancing and prevents me from signing on through the Portal with the HTML gui.
I have checked the parameters for each of the instance profiles which are correct. The message server points to a virtual host and SAPLOCALHOST and SAPGLOBALHOST are correctly defined for each instance. I have setup each instance to use the logon group PUBLIC in SMLG. The hosts and services files are the same in each node of the cluster. I can successfully resolve the host names using DNS. Also the internal RFC destinations in SM59 are configured with the correct hosts.
Does anyone know where the data for these host names is maintained?
Thank you!

I have solved the problem.
I discovered the network bindings were being accessed in the wrong order.

Portal dialog instance questions

Similar Messages

Maybe you are looking for