Dual Stack Dialog instance install

Anyone know the correct path to install a dialog instance for abap+java once sapinsta is started?

Hi, Dialog instances are only for ABAP stack, that's why it is called Dialog xxxxx because this are mainly used for Dialog workprocesses for load balancing (they can be used for other workprocesses also).
The path is Software Lifecycle options - Application server - <your DB> - Dialog instance

Similar Messages

Install additional "dialog" instance on another drive on the server

We are running NW2004S (SR2) with BW on SQL 2000, Windows 2003 on a two-node cluster. We have an existing ABAP/Java instance installed on
the "C" drive (#11) on one of the servers. I would like to install
another dialog instance on the same server as instance "01" on the "D"
drive, but when I run the install (sapinst) and select "custom", the
installation recognizes the existing instance on "C" and doesn't give
me the ability to install the new instance on "D" (just "C"). How can
I install this instance on the "D" drive ? Do I need to uninstall the
existing "11" instance on "C". Also, on this server there are two "enq"
server processes installed (ABAP #30, and Java #35) on the "C" drive -
what happens with them ?

Hi Ruchit,
I did specify the CI node when referencing the SAP profiles in the cluster and they are all recognized. My problem is that the installation only gives me the ability to install on the "C" drive. As a follow-up, SAP stated that since this is an additional dialog instance install, sapinst will perform the installation wherever the "saploc" shared says (in my case "C" - /usr/sap). It appears that if I want to basically move my existing dialog instance (11) from the "C" drive to the "D" drive, I need to uninstall the instance, along with the "enq" instances, then re-install the instance on the "D" drive.

Problems with Java dialog instance after System Copy

Hi Folks,
I've performed a System Copy from PRD to QAS both ABAP and JAVA Stack (Netweaver 2004s SEM-BW). The ABAP is up and running and the central instance JAVA too. But there was two applications (dialog instances JAVA) that desappeared after the HSC. I can't see them in Visual Administrator and can' t start them as well.
Will you give a hand on it? I know this is a pretty weird situation but if somebody experienced this please help me. As far as I know I've double-check the procedure used for this System Copy and everything has been followed.
Best regards,

Hi Prem,
Yes, this sap note is very useful, but there is no reference to Java Dialog Instance, which in this case SAP said that we need to re-install all Dialog instance, in my case I have two Appl Servers which has Java Dialog Instance installed so I have to re-install twice.
Regards,
Washington Neves

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.

Dialog Instance writing and reading from wrong global directory

Hi,
I have just completed a HA installation of ECC 6 on a Windows 2008 cluster. On node B we have the CI installed and on node A we have an additional DI installed. The installation drive for these local instances is the I drive in both cases. The ASCS instance is installed on the clustered N drive.
For some reason when a job runs on the Dialog Instance installed on node A it writes it log file to the I:\usr\sap\<SID>\SYS\global\100JOBLG directory rather that to the
<sap cluster hostname>\sapmnt\<SID>\SYS\global\100JOBLG directory (which would equate to N:\usr\sap\<SID>\SYS\global\100JOBLG). Similarly when I try a read a job log from the DI on node A it tries to read from I:\usr\sap\<SID>\SYS\global\100JOBLG and when it can find the log it gives an error.
If anybody has any ideas as to how I can reconfigure the instance to read and write to the correct directory that would be much appreciated.
Cheers,
Greg.

Have you set a different SAPGLOBALHOST or DIR_GLOBAL in your instance profile?
Kind regards,
Mark

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

Is it really necessary to re-install the dialog instances?

Hi,
We are upgrading from NW04 (WAS 6.40) to NW04s (WAS 7.00) ABAP SR2 only on Windows 2003 with Oracle 9i. There is no JAVA stack in our environment and we don't need it.
In production system we have five separate dialog instances on five different physcial machines. All these application servers runnon Windows 2003 as well.
Reading through the NW04s upgrade guide "SAP NetWeaver 2004s
Application Server ABAP" dated 28th November 2006,
section 6.26 states we have to "install the new dialog instance on top of the old dialog instance".
In the past upgrades eg. upgrade to NW04, we did not have to use SAPINST to re-install the dialog instance. Instead, the official NW04 (WAS6.40) upgrade guide just instructs us to amend instance profile parameters and copy the new version of kernel binaries either manually or using sapcpe.
I want to avoid doing this re-installation work for the five dialog insatnces. Because I want to reduce the production outage period.
Question all the upgrade experts
1) Does any one have experience that indicates I should follow the SAP documentation to un-install 6.40 instance and then re-install at 7.00 level again?
2) Also, what is the technical reason to uninstall and re-install?
The full section 6.26 section paragraph is pasted here.
6.26 Upgrading or Installing Dialog Instances
After the upgrade of the central instance, you need to upgrade the dialog instance to the new release.
To do this, you install the new dialog instance on top of the old dialog instance using the tool SAPinst.
You can now also install additional dialog instances, if necessary.
Procedure
Proceed as described in the document Installation Guide ‒ <SAP NetWeaver / SAP solution> <Technology> on
<Operating System>: <Database>.
Caution
If you upgrade a dialog instance, make sure to use the same instance number as on the source release.

Hi Matt,
Thanks for your detailed response. Our system is very much heavy batch processing oriented. Therefore our management does not want to hand over the production system until all dialog instances are ready at the new version.
It would be great if the upgrade process is quick as you pointed out.
Can you show me where this "upgrade dialog instance" option in V7 SAPINST? FYI. I should be able to start sapinst over the next few days to look for this upgrade option.
However, I just got a response from ASIA-PACIFIC OSS that says I have to un-install and re-install the existing dialog instance. Their response is as follows :
The dialog instance does not need to be upgraded since in the dialog
instance, no database exists but only the kernel files and some
profiles exist. After the upgrade, you should re-install the dialog
instance since in the central instance, the kernel release has been
changed to 700 due to the upgrade. But in the old dialog instance,
it should still have the old release kernel files and profiles.
Thus, by using reinstallation, the new release kernel files will be
installed in the dialog instance.
As to the procedure, you should uninstall the old instance firstly since during the installation, the files will be put to the same path of the
old instance.We recommend you to backup the old dialog instance files
before the installation.Sorry there is no related note but you can refer to the upgrade and installation guides.
Thanks for your input and assistance.
Benny Kwan
National Australia Bank

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

Error installing Dialog Instance ABAP+JAVA

Hi,
We're having a little issue with installation of a ERP dialog instance. The problem is, when the initial
installation was made, it was a system copy but not in the traditional way, the partner performed a copy
in OS level (cp -rp .... , etc). Once it was finished, renaming of certain this happended.
As we can see, DEV was the initial installation (normal way) but QAS and PRD were copies of DEV ( oracle
schema in PRD is SAPDEV too) this apparently doesn't cause a problem. But now the installer of a dialog
instance stops with this error:
PerfTimes : loadNativeLayer: loading jperflib failed. no jperflib in java.library.path
com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.
 at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>
(DBConnectionPool.java:115)
 at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>
(PersistenceHandler.java:38)
 at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>
(ConfigurationCache.java:149)
 at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init
(ConfigurationManagerBootstrapImpl.java:236)
 at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>
(ConfigurationManagerBootstrapImpl.java:49)
 at com.sap.engine.configtool.batch.BatchConfig.go(BatchConfig.java:47)
 at com.sap.engine.configtool.batch.BatchConfig.main(BatchConfig.java:83)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Caused by: com.sap.sql.log.OpenSQLException: Error while accessing secure store: The encryption key
(usually in the key file) is not the key that is required to decrypt the data in the secure store file or
the system name (SID) is wrong..
 at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:106)
 at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:145)
 at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:226)
 at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:197)
 at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>
(DBConnectionPool.java:112)
 ... 11 more
Caused by: com.sap.security.core.server.secstorefs.WrongKeyException: The encryption key (usually in the
key file) is not the key that is required to decrypt the data in the secure store file or the system name
(SID) is wrong.
 at com.sap.security.core.server.secstorefs.SecStoreFS.openExistingStore(SecStoreFS.java:2017)
 at com.sap.sql.connect.OpenSQLConnectInfo.getStore(OpenSQLConnectInfo.java:802)
 at com.sap.sql.connect.OpenSQLConnectInfo.lookup(OpenSQLConnectInfo.java:783)
 at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:209)
 ... 13 more
Caused by: com.sap.security.core.server.secstorefs.InvalidStateException: Internal error during the
decryption process.
 at com.sap.security.core.server.secstorefs.Crypt.decrypt(Crypt.java:850)
 at com.sap.security.core.server.secstorefs.SecStoreFS.openExistingStore(SecStoreFS.java:1985)
 ... 16 more
Caused by: javax.crypto.BadPaddingException: Invalid PKCS#5 padding length: 176
 at iaik.security.cipher.s.b(Unknown Source)
 at iaik.security.cipher.w.a(Unknown Source)
 at iaik.security.cipher.w.engineDoFinal(Unknown Source)
 at javax.crypto.Cipher.doFinal(DashoA12275)
 at com.sap.security.core.server.secstorefs.Crypt.decrypt(Crypt.java:825)
 ... 17 more
Error while connecting to DB.
The error occurs when the installer tries to connect to oracle via jdbc, but the files
SecStore.properties and SecStore.key are from DEV, and they were created with the values of DEV, so when
the installer tries with PRD as central instance name, it doesn't work, how can we recreate this files or
reconfigure the j2ee engine so the installer can connect and finish installation ?
Thanks in advance

Exactly, the problem is when the installer tries to execute the following:
/usr/j2se/bin/java -classpath /tmp/sapinst_instdir/ERP/LM/AS/ORA/DI/install/shar
edlib/launcher.jar -Xmx256m -d64 -d64 com.sap.engine.offline.OfflineToolStart co
m.sap.engine.configtool.batch.BatchConfig /usr/sap/PRD/SYS/global/security/lib/t
ools/iaik_jce.jar:/usr/sap/PRD/SYS/global/security/lib/tools/iaik_jsse.jar:/usr/
sap/PRD/SYS/global/security/lib/tools/iaik_smime.jar:/usr/sap/PRD/SYS/global/sec
urity/lib/tools/iaik_ssl.jar:/usr/sap/PRD/SYS/global/security/lib/tools/w3c_http
.jar:/tmp/sapinst_instdir/ERP/LM/AS/ORA/DI/install/lib:/tmp/sapinst_instdir/ERP/
LM/AS/ORA/DI/install/sharedlib:/oracle/client/10x_64/instantclient/ojdbc14.jar /
tmp/sapinst_instdir/ERP/LM/AS/ORA/DI/BatchConfig.xml
The file /tmp/sapinst_instdir/ERP/LM/AS/ORA/DI/BatchConfig.xml has this:
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE config [
<!ELEMENT config (dbproperties, task*)>
 <!ELEMENT dbproperties (property*)>
 <!ELEMENT task (property*)>
 <!ATTLIST task name CDATA #REQUIRED>
 <!ELEMENT property (#PCDATA)>
 <!ATTLIST property key CDATA #REQUIRED>
 <!ATTLIST property value CDATA #REQUIRED>
]>
<config>
<dbproperties>
 <property key="rdbms.maximum_connections" value="5"/>
 <property key="system.name" value="PRD"/>
 <property key="secstorefs.keyfile" value="/sapmnt/PRD/global/security/data/S
ecStore.key"/>
 <property key="secstorefs.secfile" value="/sapmnt/PRD/global/security/data/S
ecStore.properties"/>
 <property key="secstorefs.lib" value="/sapmnt/PRD/global/security/lib"/>
 <property key="rdbms.driverLocation" value="/oracle/client/10x_64/instantcli
ent/ojdbc14.jar"/>
 <property key="rdbms.connection" value="jdbc/pool/PRD"/>
 <property key="rdbms.initial_connections" value="1"/>
As you can see the are values "system.name" with PRD. This cause an error:
PerfTimes : loadNativeLayer: loading jperflib failed. no jperflib in java.library.path
com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.
 at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:115)
 at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(PersistenceHandler.java:38)
 at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:149)
 at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:236)
 at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:49)
 at com.sap.engine.configtool.batch.BatchConfig.go(BatchConfig.java:47)
 at com.sap.engine.configtool.batch.BatchConfig.main(BatchConfig.java:83)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Caused by: com.sap.sql.log.OpenSQLException: Error while accessing secure store: The encryption key (usually in the key file) is not the key that is required to decrypt the data in the secure store file or the system name (SID) is wrong..
 at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:106)
 at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:145)
 at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:226)
 at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:197)
 at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:112)
 ... 11 more
Caused by: com.sap.security.core.server.secstorefs.WrongKeyException: The encryption key (usually in the key file) is not the key that is required to decrypt the data in the secure store file or the system name (SID) is wrong.
 at com.sap.security.core.server.secstorefs.SecStoreFS.openExistingStore(SecStoreFS.java:2017)
 at com.sap.sql.connect.OpenSQLConnectInfo.getStore(OpenSQLConnectInfo.java:802)
 at com.sap.sql.connect.OpenSQLConnectInfo.lookup(OpenSQLConnectInfo.java:783)
 at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:209)
 ... 13 more
Caused by: com.sap.security.core.server.secstorefs.InvalidStateException: Internal error during the decryption process.
 at com.sap.security.core.server.secstorefs.Crypt.decrypt(Crypt.java:850)
 at com.sap.security.core.server.secstorefs.SecStoreFS.openExistingStore(SecStoreFS.java:1985)
 ... 16 more
Caused by: javax.crypto.BadPaddingException: Invalid PKCS#5 padding length: 176
 at iaik.security.cipher.s.b(Unknown Source)
 at iaik.security.cipher.w.a(Unknown Source)
 at iaik.security.cipher.w.engineDoFinal(Unknown Source)
 at javax.crypto.Cipher.doFinal(DashoA12275)
 at com.sap.security.core.server.secstorefs.Crypt.decrypt(Crypt.java:825)
 ... 17 more
The same as configtool with PRD value.
So can we change the system.name value to PRD and is there a posibility to change the encpytion key so it can be used with PRD value ??
My theory is: The SecStore.key file is used to decript the SecStore.properties but the system.name value plays an important role in decryption, am I right??
Can I regenerate the key with the system.name = PRD so the error solves??
Regards.

Question about the number of ERS instances in a dual-stack MCS environment

Hello to the group.
I have a simple question for those running a NetWeaver 7.0 (i.e. 2004s) dual stack (ABAP/JAVA) setup in an MCS environment. On each individual node, do you have two separate ERS processes running on the node (as seen in Task Manager) that is opposite to the system running the ASCS/SCS instances? If so, do you have a set of profiles for each of these ERS processes (I am guessing that is true)?
Thanks in advance for your help.
J. Haynes

Has anyone found a good description of the process that runs after one node fails over to another one? help.sap.com mentions that the ASCS will restart and run the command enstatus.cmd but I cannot find what is supposed to happen after that. Is the ERS service itself stopped?
Thanks
J. Haynes

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

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.

Installing Dialog Instances with ECC 6.0 and SQL Server 2005

Hi, I have my ECC 6.0 SAP Server, it is Central Instance, Database instance, all in one. My users are working fine, however we will be adding some new users (15) and we want add a Dialog Instance. Can I add one Dialog instance to my landscape without any changes to my SAP Server ??? ..... My dialog instance will be in a new host.
My hardware SAP Server is: 16 GB RAM, 500 GB RAID 5 for my database, four processors.
What could be my Dialogue Instance hardware?
I have read than I must install with sapinst and select Dialogue Instance and follow instructions. Are there any others considerations?? .....
Do I must install SQL Server in the host Dialog instance ??.
Please if you have some suggestions.
Regards.

Hello Jose,
You can install your dialog instance without doing any change to the existing setup as you have mentioned its on a seprate new host.
Two CPU's and 8GB memory would be fine for your dialog instance.It all depends on your requirement.
Yes you need to install the dialog instance using SAPINST, its kool and sapinst would take care of all.
You need not install any SQL server in the dialog instance host only you need to have a SQL client installed but that would be taken care by SAPINST.
Hope this would clarify your query.
Thanks and Regards,
-Bijesh.

Installing a Dialog instance on a 2008 server while having the CI on 2000

Hi all,
Can we do such a thing? Install the Dialog Instance on a 2008 server while having the CI on 2000?
Thanks!
Samer

Yes you can do it.
What you need to keep in mind that both system should be in network and /sapmnt should be mounted into DI server.
We have tested it into 2 different Linux version yesterday.
Regards
Subhash

Installing dialog instance on cluster.

Hi ,
I have installed ASCS, SCS,CI and DI , on Unix Cluster Evironment ,
Now i am trying to install Dialog instance on Node B, but it is looking for Default profile which is available on /sapmnt/sid/profiles,
How do i get it on node B, Can anyone guide me how to do it using NFS, or is there any other way.
Regards,
SM..

Hi
you need to export your /sapmnt/<SID> structure using NFS on the host where it resides .
If you want to use the inactive Node as an Application Server , you need to mount /sapmnt/<SID> from the NFS-Server , where it was exported , to your Node B Application Server .
There is nothing different to an regular application server so far .
Since there are different management interfaces on different operating systems , I cannot give more detailed informations , but I suppose , you will get this managed .
If you have any technical difficulties , let us know and provide more details to your cluster environment (At least , which operating system you use and which error you get).
Best regards
dirk

Dual Stack Dialog instance install

Similar Messages

Maybe you are looking for