on 01-24-2014 3:04 AM
Looks like you've only installed the designtime component (MMC console), and not the runtime component where the dispatcher and runtimes are.
Br,
Per Christian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Matt,
We have used a similar document that contains some of the same steps so I figured I would look at the differences and try to perform the differences in the file you posted that where not done.
This is where I ran into problems.... the JCE Policy files... I have no idea which ones I should be using, i viewed the note and still can't determine, were on oracle11g with red hat linux as the server OS.
According to my workmates this machine shares a sapjvm install with NWDS but when I login as idmadm and do a java -version I get JDK...
java version "1.7.0_09-icedtea"
OpenJDK Runtime Environment (rhel-2.3.8.0.el6_4-x86_64)
OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode)
Could this perhaps be part of the issue....that it is not SAPJVM?
Also at the bottom of page 5 per the document you mentioned the script that it says should be in the home directory is non-existent. postinst.sh does not exist anywhere on the system.... I don't even see it if I look into the CD image of the IDM install we used...
JCE files are particular to the version of Java you are using. My experience has always been best when using Java 6, not 7, Sun/Oracle, not SAP or open.
Make sure that your environment variables are set, and as Chris mentioned, make sure that you have the runtime component installed on that server.
What Linux are you using?
Matt
Red Hat Enterprise Linux Server release 6.4 (Santiago)
We installed a runtime component - ICRUNTIME08_1-20005938.zip from SAP Marketplace... The environment variables that Krishna mentioned are set but perhaps I have the wrong files? the specific JAR file he mentioned for "JDBC Driver Jar" are missing, but I would imagine since I am not utilizing SQL but instead oracle 11g it should be a different file?
I just implemented win64_11gR2_client.zip install on my workstation windows 7 and reloaded IDM MC on my workstation and attempted the "Test" dispatcher again after having already re-created the "Dispatcher Scripts" and I still get the same error as above only its pointing to a different path the one from which the Oracle Client was installed too.... here are my java settings...
Andrew.
Here's what I have in my Windows Oracle VM:
Here's my BAT file:
@echo off
:: =======================================================================================
:: MC_COMMAND One of: test/install/start/stop/remove
:: OPTIONS One of checkconfig/runonce
:: checkconfig Doesn't really run DISPATCHER -> just reads configuration(s) and exits
:: runonce Runs only once - and exits
:: "debug=<LEVEL>" Set loglevel to LEVEL (none=0,error=1,debug=2), Default=NONE. Note quotes!
:: DSEHOME Path to DSE installation directory
:: MXDISPATCHERPROP Property file name
:: MXDISPATCHERJAR Classpath including full path to DISPATCHER.jar
:: =======================================================================================
:: ----------------
SET MC_COMMAND=%1
SET OPTIONS=%2
:: ----------------
:: =======================================================================================
:: Dispatcher Run modes
::
:: Run Dispatcher on the command line:
:: Dispatcher_service_idmdispatcher.bat test
::
:: Read configuration and exit:
:: Dispatcher_service_idmdispatcher.bat test checkconfig
::
:: Run once and exit:
:: Dispatcher_service_idmdispatcher.bat test runonce
:: =======================================================================================
IF "%1" == "test" goto START
IF "%1" == "TEST" goto START
IF "%1" == "install" goto START
IF "%1" == "INSTALL" goto START
IF "%1" == "start" goto START
IF "%1" == "START" goto START
IF "%1" == "stop" goto START
IF "%1" == "STOP" goto START
IF "%1" == "remove" goto START
IF "%1" == "REMOVE" goto START
goto USAGE
:START
:: =======================================================================================
:: --- JVMDLL is pointing at the JVM dll used to start the Java Virtual Machine
:: =======================================================================================
SET JVMDLL=C:\Program Files (x86)\Java\jre6\bin\client\jvm.dll
:: =======================================================================================
:: --- DSE_HOME variable points to the installation directory
:: =======================================================================================
SET DSE_HOME=C:\usr\sap\IdM\Identity Center
:: =======================================================================================
:: --- MXDISPATCHERPROP variable points to the Dispatcher property file
:: =======================================================================================
SET MXDISPATCHERPROP=C:\usr\sap\IdM\Identity Center\Service-Scripts\Dispatcher_Service_idmdispatcher.prop
:: =======================================================================================
:: --- The dispatcher needs a JDBC driver to connect to the Identity Center DB
:: =======================================================================================
SET MXDRIVERJAR=C:\SQLJDBC\ojdbc5.jar
:: =======================================================================================
:: --- all necessary dispatcher-related jars: mxdispatcher.jar + mxmcapi.jar + driver for MC
:: =======================================================================================
SET MXDISPATCHERJAR=%DSE_HOME%\Java\mxdispatcher.jar;%DSE_HOME%\Java\mxmcapi.jar;%MXDRIVERJAR%;%CLASSPATH%
:: =======================================================================================
:: --- Start the Dispatcher
:: =======================================================================================
"%DSE_HOME%\MxService.exe" MxDispatcher_idmdispatcher %MC_COMMAND% mainclass=com/sap/idm/ic/services/dispatcher/MxDispatcher "jvmdll=%JVMDLL%" "homedir=%DSE_HOME%" "-Djava.class.path=%MXDISPATCHERJAR% " -DDSE_HOME="%DSE_HOME%" -DMCSERVICES_PROP="%MXDISPATCHERPROP%" %OPTIONS%
GOTO EXIT
:USAGE
ECHO.
ECHO USAGE: Dispatcher_service_idmdispatcher.bat Command Option
ECHO.
ECHO Command One of: test/install/start/stop/remove
ECHO Option Optionally one of checkconfig/runonce in combination with test
ECHO checkconfig Doesn't really run DISPATCHER - just reads configuration(s) and exits
ECHO runonce Runs only once - and exits
ECHO.
:EXIT
And my PROP file:
# ***********************************************************
# --- This file is reloaded each RELOAD_FREQUENCY ....
# ***********************************************************
# =====================================================================
# --- DISPATCHER PARAMETERS
# =====================================================================
# ---------------------------------------------------------------------
# --- The name of the dispatcher
# ---------------------------------------------------------------------
DISPATCHER_NAME=idmdispatcher
# ---------------------------------------------------------------------
# --- Driver and url necessary to reach MC
# ---------------------------------------------------------------------
MC_JDBCDRIVER=oracle.jdbc.driver.OracleDriver
MC_JDBCURL={DES3CBC}(REMOVED)
# ---------------------------------------------------------------------
# --- Classpath passed to DSE runtime engine.
# ---
# --- The delimiter used in this template is ':'.
# --- It is possible to use either ';' or ':' - dispatcher will create
# --- platform correct string ( with ';' on Windows, and ':' on Unix)
# ---
# --- %DSE_HOME% will be expanded by dispatcher (replaced with the value
# --- passed to dispatcher itself)
# ---
# --- The directory separator used in this template is '/'.
# --- It is possible to use either '\\' or '/' - dispatcher will create
# --- platform correct string ( with '\\' on Windows, and '/' on Unix)
# ---
# --- TODO
# --- The JCO driver is needed for connecting to ABAP. If running the
# --- dispatcher on Unix the path must be set to point to the actual
# --- JCO install directory.
# ---------------------------------------------------------------------
DSECLASSPATH=%DSE_HOME%/Java/DSE.jar:%DSE_HOME%/Java:%DSE_HOME%/Java/sapjco.jar:
# ---------------------------------------------------------------------
# 0=false , 1=true
# ---------------------------------------------------------------------
# ---------------------------------------------------------------------
# --- if 1, dispatcher displays all config information each time
# --- the configuration is read (and reloaded)
# ---------------------------------------------------------------------
MXDISPATCHER_PRINTRELOAD=0
# ---------------------------------------------------------------------
# --- if 1, dispatcher displays the the command that is used in order
# --- to execute DSE. This can be usefull for debuging: clip this line
# --- and execute directly from the command line
# ---------------------------------------------------------------------
MXDISPATCHER_REPORTEXEC=1
# ---------------------------------------------------------------------
# --- if 1, dispatcher will execute the command as one string
# --- (as opposite as string[], that is default)
# ---------------------------------------------------------------------
MXDISPATCHER_EXECSTRING=0
# ---------------------------------------------------------------------
# --- if 1, dispatcher will wait for dse that it executed.
# ---------------------------------------------------------------------
MXDISPATCHER_WAITFORDSE=0
# ---------------------------------------------------------------------
# --- Sets the log type
# --- 1=mc only, 2=console only, 3=both
# ---------------------------------------------------------------------
MXDISPATCHER_LOGTYPE=2
# ---------------------------------------------------------------------
# --- Additional Java options
# --- Please note that if you specify more than one option here you
# --- need to set MXDISPATCHER_EXECSTRING=1
# ---------------------------------------------------------------------
JAVAOPTIONS=
# ---------------------------------------------------------------------
# --- Drivers potentially needed by DSE, so it can execute
# --- The delimiter between drivers used in this template is ';'.
# --- It is possible to use either ';' or ':' - dispatcher will create
# --- platform correct string ( with ';' on Windows, and ':' on Unix)
# ---------------------------------------------------------------------
JDBCDRIVERS=oracle.jdbc.driver.OracleDriver;com.microsoft.sqlserver.jdbc.SQLServerDriver
# ---------------------------------------------------------------------
# --- Log level for DSE runtime engine
# ---
# --- 0 - None
# --- 1 - Error
# --- 3 - Info
# --- 4 - Extended
# --- 7 - Debug
# ---------------------------------------------------------------------
LOGLEVEL=3
# ---------------------------------------------------------------------
# --- Stack Trace for DSE runtime engine
# ---
# --- 0 - None
# --- 1 - Topmost entry
# --- 2 - Full trace
# ---------------------------------------------------------------------
STACKTRACE=1
Please let me know if this is helpful to you.
If you are supposed to run your dispatchers/IdM run-time on Linux you cannot start them on the MMC running on your local computer or Windows box.
You need to copy the scripts to your Linux box and start/run them there.
regards, Tero
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Andrew,
The jdbc driver field should point to the path of the sqljdbc.jar file. This is very important for the database connectivity.
Download the sqljdbc.jar drivers that are suitable for your database and install them.
After installation, provide the path in the field as shown in my earlier screenshot.
All the best,
~Krishna.
User | Count |
---|---|
85 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.