Release Procedure Configuration steps with screenshots
Hi,
Can anybody send release procedure configuration settings with screen shots.
Regards
Ramakrishna
Hi Ram,
Release strategy steps
SPRO-MM- Purchasing-Purchase Requisition-Release Procedure- Procedure with Classification
1.Edit Charatestic,(CT04), use Class 032
2.Edit Class(CL02)
3.Set up Procedure with Classification
3.1. Relesae Group,
3.2Relaese Code,
3.3.Relaese Inicator,
3.4Relaese Statergies
3..4.1. Relaese Prerequisities
3.4.2. Relaese Statuses
3.4.3. Classification
3.4.4. Realesae Simulation
Release procedure for Purchase orders here is process flow.
Go to spro>img>materials management>purchassing>Release procedure for Purchase orders
1. Create characterstics -Intially you will create characterstics based on which you would like to release a purchase order.
Charactrestics are like plant, purchase order value,purchase group etc.. Assign characterstics to release class 032.
2. Create Release group say 01 and create release codes like pm(project manager), gm(general manager) etcc..
3. Create a Release starategy say s1 and assign release group to it 01 and release class 032 and department to whom this release stategy applies say MM. define the order of release say first pm followed by gm etc..
4. under classfication define value limits for release of purchase order.
5. define release indicators
6. simulate the release
7. assign if there is any workflow.
For more Check the links:
http://www.scribd.com/doc/531679/Release-Procedure-for-Purchase-Requisitions
http://www.sap-img.com/workflow/workflow-of-purchase-requisition-release-strategy.htm
http://www.sap123.com/showthread.php?t=59
Similar Messages
-
Pricing Procedure Configuration steps with screenshots
Hi,
Can anybody send screenshots as per above said subject.
The main reasion now I am working in implementation project.
If you are able to give your contact no,I will be greatfull to you.
Regards
ramakrishna
9618087321You can confi. new Pricing procedure and can go for pricing manually or automatic. If you need pricing automatic you have to go for use of Access Sequences and Schema Group of Vendor. You can customize your pricing procedure according to your requirement such as like Domestic, Import and Stock transport.
For the above individually you have to configure Pricing Procedure and the following steps are:
SPRO->MM->Purchasing->Conditions->Define Price determination process
1. Define Condition Table:
2.Define Access Sequence,
3.Define Condition Type,
4.Define Calculating Schema,
5.Assign Calculation Schema, Access Sequence and Condition Type,
6.Define Schema Group Of Vendor,
7. Define Schema Group Of Purchasing Organization,
8.Assign Schema Group Of Vendor to Purchasing Organization,
9.Assignment of Schema Group Of Vendor ,Schema Group Purchasing Organization and Calculation Schema.
10.Assign Vendor to Schema Group Of Vendor (XK02)
11.Maintain Condition record(MEK1)
After above steps , you can go for create PO in ME21N.
In the case of Import PO, you have to activate Import PO.
SPRO->Materials Management -> Purchasing -> Foreign Trade/Customs ->Control Foreign Trade Data in MM and SD Documents ->Incompleteness Schemas for Foreign Trade Data .
For more check the links:
http://**********************/2008/09/price-determination-process-or-pricing.html
http://www.scribd.com/doc/7149675/Steps-for-MM-Pricing-Procedures
http://www.sap-img.com/materials/steps-for-mm-pricing-procedures.htm
Please refer the following threads
Pricing Procedure for PO
pricing procedure steps reg., -
I need ECC 6.0 installation steps with screenshots
please send me the ECC 6.0 installation guide.I need ECC 6.0 installation steps with screenshots. my mail id is <removed by moderator>.thanks in advance.
need SAP CRM 4.0 installation guide with screenshots.
Markus -
GC install fails on OMS Configuration step with NodeManager
I'm trying to install OEM Grid Control and I'm having some problems getting past the OMS Configuration step in the installation. I'm not very familiar with Oracle products. I've completed all the configuration steps listed in the documentation and in order to resolve an earlier problem, I deleted the Keynectis and Telesec certificates from the cacerts java keystore. NodeManager is being run as a service, though I think the configuration process is launching a new instance because it can't connect to the service. I've also been unable to connect to the service through the WLST nmConnect function, though it's possible my parameters are incorrect. If the only problem is that GCDomain is not registered in the nodemanager.domains file, I'm not sure what I'm doing wrong, because I put it in the nodemanager.domains file located at C:\Oracle\Middleware\wlserver_10.3\common\nodemanager:
#Domains and directories created by Configuration Wizard
#Fri Apr 22 15:23:16 EDT 2011
wl_server=C\:\\Oracle\\Middleware\\wlserver_10.3\\samples\\domains\\wl_server
medrec-spring=C\:\\Oracle\\Middleware\\wlserver_10.3\\samples\\domains\\medrec-spring
GCDomain=C\:\\Oracle\\gc_inst\\user_projects\\domains\\GCDomain
medrec=C\:\\Oracle\\Middleware\\wlserver_10.3\\samples\\domains\\medrec
note - the file paths are correct and use escaped slashes where appropriate, but this message board system is turning the last double backslash into a line break. I can't find any html solution that works, so just take my word for it
I restarted NodeManager after making the change as well. Any help would be appreciated. Thanks.
Details:
Machine - Windows Server 2008 x64
DB - 11gR2
WLS - 10.3.2
GC - 11.1.0.1
Install Log:
FINE: Connecting to Node Manager ... Apr 22, 2011 3:23:19 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: <Apr 22, 2011 3:23:19 PM EDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.> Apr 22, 2011 3:23:19 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: <Apr 22, 2011 3:23:19 PM EDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.> Apr 22, 2011 3:23:19 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: <Apr 22, 2011 3:23:19 PM EDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.> Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: This Exception occurred at Fri Apr 22 15:23:20 EDT 2011. Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: weblogic.nodemanager.NMConnectException: Connection refused: connect. Could not connect to NodeManager. Check that it is running at win2008x64-2:7,401. Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at java.net.PlainSocketImpl.socketConnect(Native Method) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at java.net.Socket.connect(Socket.java:525) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at weblogic.nodemanager.client.SSLClient.createSocket(SSLClient.java:38) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at weblogic.nodemanager.client.NMServerClient.connect(NMServerClient.java:227) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerClient.java:199) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerClient.java:205) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at weblogic.nodemanager.client.NMServerClient.getVersion(NMServerClient.java:52) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at weblogic.management.scripting.NodeManagerService.verifyConnection(NodeManagerService.java:175) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at weblogic.management.scripting.NodeManagerService.nmConnect(NodeManagerService.java:168) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at java.lang.reflect.Method.invoke(Method.java:597) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at org.python.core.PyReflectedFunction.__call__(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at org.python.core.PyMethod.__call__(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at org.python.core.PyObject.__call__(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at org.python.core.PyObject.invoke(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at org.python.pycode._pyx2.nmConnect$3(<iostream>:118) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at org.python.pycode._pyx2.call_function(<iostream>) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at org.python.core.PyTableCode.call(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at org.python.core.PyTableCode.call(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at org.python.core.PyFunction.__call__(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at org.python.core.PyObject.__call__(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at org.python.pycode._pyx41.startNM$1(C:\Oracle\Middleware\oms11g\sysman\omsca\scripts\wls\start_server.py:20) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at org.python.pycode._pyx41.call_function(C:\Oracle\Middleware\oms11g\sysman\omsca\scripts\wls\start_server.py) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at org.python.core.PyTableCode.call(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at org.python.core.PyTableCode.call(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at org.python.core.PyFunction.__call__(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at org.python.pycode._pyx39.f$0(C:\Oracle\Middleware\oms11g\sysman\omsca\scripts\wls\create_em_infra.py:74) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at org.python.pycode._pyx39.call_function(C:\Oracle\Middleware\oms11g\sysman\omsca\scripts\wls\create_em_infra.py) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at org.python.core.PyTableCode.call(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at org.python.core.PyCode.call(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at org.python.core.Py.runCode(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at org.python.util.PythonInterpreter.execfile(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at weblogic.management.scripting.WLST.main(WLST.java:131) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at java.lang.reflect.Method.invoke(Method.java:597) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: at weblogic.WLST.main(WLST.java:29) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: Fri Apr 22 15:23:20 EDT 2011 Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: Node Manager is down starting it Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: Not connected to Node Manager Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: Launching NodeManager ...
Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: Properties: {ListenAddress=win2008x64-2,ListenPort=7401,NodeManagerHome=C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239,StartScriptEnabled=true,StartScriptName=startEMServer.cmd,}
Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: Command: C:\Oracle\MIDDLE~1\JROCKI~1.5-3\jre\bin\javaw.exe -classpath "C:\Oracle\MIDDLE~1\JROCKI~1.5-3\jre\lib\rt.jar;C:\Oracle\MIDDLE~1\JROCKI~1.5-3\jre\lib\i18n.jar;C:\Oracle\MIDDLE~1\patch_wls1032\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\patch_oepe1032\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\JROCKI~1.5-3\lib\tools.jar;C:\Oracle\MIDDLE~1\utils\config\10.3\config-launch.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.jar;C:\Oracle\MIDDLE~1\modules\features\weblogic.server.modules_10.3.2.0.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\webservices.jar;C:\Oracle\MIDDLE~1\modules\ORGAPA~1.0\lib\ant-all.jar;C:\Oracle\MIDDLE~1\modules\NETSFA~1.0_1\lib\ant-contrib.jar;C:\Oracle\Middleware\oms11g\sysman\jlib\emConfig.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrf-api.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\resources\jrf-wlst.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.odl_11.1.1\ojdl.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.odl_11.1.1\ojdl2.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.dms_11.1.1\dms.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.dconfig-infra_11.1.1.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.fabriccommon_11.1.1\fabric-common.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.xdk_11.1.0\xmlparserv2.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.xdk_11.1.0\xml.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.wsm.common_11.1.1\wsm-pmlib.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.wsm.common_11.1.1\wsm-policy-core.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.wsm.common_11.1.1\wsm-secpol.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.wsm.common_11.1.1\wsm-dependencies.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.wsm.policies_11.1.1\wsm-seed-policies.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.webservices_11.1.1\orawsdl.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.webservices_11.1.1\mdds.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.webservices_11.1.1\ws_confmbeans.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\org.apache.commons.digester_1.7.jar;C:\Oracle\MIDDLE~1\ORACLE~1\..\modules\javax.xml.bind_2.1.1.jar;C:\Oracle\MIDDLE~1\ORACLE~1\..\modules\javax.activation_1.1.jar;C:\Oracle\MIDDLE~1\ORACLE~1\..\modules\javax.xml.stream_1.1.1.0.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.http_client_11.1.1.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jmx_11.1.1\jmxframework.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jmx_11.1.1\jmxspi.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.adf.dconfigbeans_11.1.1.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.adf.share.ca_11.1.1\adf-share-base.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.adf.share.ca_11.1.1\adf-share-ca.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.adf.share_11.1.1\adflogginghandler.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.adf.share_11.1.1\adfsharembean.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.adf.share_11.1.1\commons-el.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.adf.share_11.1.1\jsp-el-api.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.adf.share_11.1.1\oracle-el.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\resources\auditwlst.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\resources\sslconfigwlst.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\resources\oamap_help.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\resources\ossoiap_help.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\resources\jps-wlst.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.auditprovider_11.1.1\jps-wls-auditprovider.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jps_11.1.1\jps-manifest.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jps_11.1.1\jps-mbeans.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jps_11.1.1\jps-upgrade.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jps_11.1.1\jps-patching.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\lib\ADF-SH~1.JAR;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\lib\mdswlst.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\AUDITW~1.JAR;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\jps-wlst.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\jrf-wlst.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\OAMAP_~1.JAR;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\OAMAUT~1.JAR;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\ossoiap.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\OSSOIA~1.JAR;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\SSLCON~1.JAR;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\wsm-wlst.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\common\eval\pointbase\lib\pbembedded57.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\common\eval\pointbase\lib\pbclient57.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\common\eval\pointbase\lib\pbtools57.jar" weblogic.NodeManager "-v"
Apr 22, 2011 3:23:21 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: <Apr 22, 2011 3:23:21 PM> <INFO> <Loading domains file: C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239\nodemanager.domains> Apr 22, 2011 3:23:21 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Apr 22, 2011 3:23:21 PM weblogic.nodemanager.server.NMServerConfig initDomainsMap Apr 22, 2011 3:23:21 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: INFO: Loading domains file: C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239\nodemanager.domains Apr 22, 2011 3:23:21 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: <Apr 22, 2011 3:23:21 PM> <WARNING> <Domains file not found: C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239\nodemanager.domains> Apr 22, 2011 3:23:21 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Apr 22, 2011 3:23:21 PM weblogic.nodemanager.server.NMServerConfig initDomainsMap Apr 22, 2011 3:23:21 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: WARNING: Domains file not found: C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239\nodemanager.domains Apr 22, 2011 3:23:22 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: <Apr 22, 2011 3:23:22 PM> <INFO> <Loading identity key store: FileName=C:/Oracle/MIDDLE~1/WLSERV~1.3/server\lib\DemoIdentity.jks, Type=jks, PassPhraseUsed=true> Apr 22, 2011 3:23:22 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Apr 22, 2011 3:23:22 PM weblogic.nodemanager.server.SSLConfig loadKeyStoreConfig Apr 22, 2011 3:23:22 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: INFO: Loading identity key store: FileName=C:/Oracle/MIDDLE~1/WLSERV~1.3/server\lib\DemoIdentity.jks, Type=jks, PassPhraseUsed=true Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: <Apr 22, 2011 3:23:23 PM> <WARNING> <Node manager configuration properties file 'C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239\nodemanager.properties' not found. Using default settings.> Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Apr 22, 2011 3:23:23 PM weblogic.nodemanager.server.NMServer <init> Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: WARNING: Node manager configuration properties file 'C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239\nodemanager.properties' not found. Using default settings. Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: <Apr 22, 2011 3:23:23 PM> <INFO> <Saving node manager configuration properties to 'C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239\nodemanager.properties'> Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Apr 22, 2011 3:23:23 PM weblogic.nodemanager.server.NMServer <init> Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: INFO: Saving node manager configuration properties to 'C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239\nodemanager.properties' Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Node manager v10.3 Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Configuration settings: Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: NodeManagerHome=C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239 Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: ListenAddress=win2008x64-2 Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: ListenPort=7401 Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: ListenBacklog=50 Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: SecureListener=true Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: AuthenticationEnabled=true Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: NativeVersionEnabled=true Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: CrashRecoveryEnabled=false Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: JavaHome=C:\Oracle\MIDDLE~1\JROCKI~1.5-3\jre Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: StartScriptEnabled=true Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: StopScriptEnabled=false Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: StartScriptName=startEMServer.cmd Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: StopScriptName= Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: LogFile=C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239\nodemanager.log Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: LogLevel=INFO Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: LogLimit=0 Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: LogCount=1 Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: LogAppend=true Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: LogToStderr=true Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: LogFormatter=weblogic.nodemanager.server.LogFormatter Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: DomainsFile=C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239\nodemanager.domains Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: DomainsFileEnabled=true Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: StateCheckInterval=500 Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: QuitEnabled=true Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Interface= Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: NetMask= Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: UseMACBroadcast=false Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: DomainRegistrationEnabled=false Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Domain name mappings: Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: <Apr 22, 2011 3:23:23 PM> <INFO> <Secure socket listener started on port 7,401, host WIN2008x64-2/192.168.182.135> Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Apr 22, 2011 3:23:23 PM weblogic.nodemanager.server.SSLListener run Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: INFO: Secure socket listener started on port 7,401, host WIN2008x64-2/192.168.182.135 Apr 22, 2011 3:23:30 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: Successfully launched the Node Manager. Apr 22, 2011 3:23:30 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: The Node Manager process is running independent of the WLST process. Apr 22, 2011 3:23:30 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: Exiting WLST will not stop the Node Manager process. Please refer Apr 22, 2011 3:23:30 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: to the Node Manager logs for more information. Apr 22, 2011 3:23:30 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: The Node Manager logs will be under C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239 Apr 22, 2011 3:23:30 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: Connecting to Node Manager ... Apr 22, 2011 3:23:41 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: <Apr 22, 2011 3:23:41 PM> <WARNING> <Configuration error while reading domain directory> Apr 22, 2011 3:23:41 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: weblogic.nodemanager.common.ConfigException: The domain 'GCDomain' at 'C:\Oracle\gc_inst\user_projects\domains\GCDomain' was not registered in the nodemanager.domains file and dynamic domain registration is not supported. Please register the domain in the nodemanager.domains file. Apr 22, 2011 3:23:41 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: at weblogic.nodemanager.server.NMServer.getDomainManager(NMServer.java:257) Apr 22, 2011 3:23:41 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: at weblogic.nodemanager.server.Handler.handleDomain(Handler.java:224) Apr 22, 2011 3:23:41 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:108) Apr 22, 2011 3:23:41 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: at weblogic.nodemanager.server.Handler.run(Handler.java:70) Apr 22, 2011 3:23:41 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: at java.lang.Thread.run(Thread.java:619) Apr 22, 2011 3:23:41 PM oracle.sysman.omsca.util.ProcessOutputReader run
...I have a JDK already installed, but isn't JRockit being used by NodeManager in this case? Does NodeManager need to run on the JDK?
Regardless, I tried changing JavaHome in the nodemanager.properties file to the JDK/jre directory, but the log file still has the original path. The log seems to indicate that the process thinks that NodeManager is down because it can't connect, so it launches a new instance and uses default configuration parameters, which naturally wouldn't have my changes to the nodemanager.domain or nodemanager.properties files.
Also, the log says it can't connect to NodeManager at win2008x64-2:7,401. I'm not sure why there's a comma in there, but by the time this configuration step fails, there is a javaw.exe process listening on port 7401 and if I retry the step without killing it, the step will fail earlier because the port is already bound. -
I am installing ADFS 3.0 alongside an existing ADFS 2.0 farm. I followed the steps as detailed here:
http://office365support.ca/migrating-ad-fs-2-0-to-ad-fs-3-0-for-office365-single-sign-on-2/
That worked fine initially, but I ran into problems and decided to remove ADFS 3.0 completely and start over. When I rerun the the Active Directory Federation Services Configuration Wizard, it gets almost all the way through, but fails with a generic
error of: An error occurred while trying to configure this machine.
Down below in the Detailed operation results, it displays:
ADRepository.CreateTopContainer
I am guessing I haven't cleared out something in Active Directory, but I'm not sure what that is.
In my research, I found suggestions for deleting everything under ProgramData\Microsoft\ADFS, but I don't believe I can do that since I am still relying on the ADFS 2.0 installation until I can cut over.
Any help would be much appreciated.
Regards,
David CollinsADFS 2.0 uses IIS and so the installation is under /inetpub/adfs/ls.
There's also a backup here:
ADFS : Restoring / re-installing ADFS v 2.0. -
I have configured the PO release procedure for PO with header value of more then 25000. In the process I have created the following -
1. Custom Characterstic
2. Custom class
3. Release group
4. Release code
5. Release indicator
6. Release strategy
but the problem I am having is that the workflow event 'ReleaseStepCreated' is generated in the system even for PO with header value of less than $25000. Also the 'Release' tab is not appearing in the PO header.
Please help. Appreciate you time.
Sridhar JamiI think this issue is also related to mis entries in SWEC.
Go thru' this Note 797775 - Entry in Transaction SWEC hinders workflow. Verify all the steps stated in this note even you think it might not be the right note.
Regards, IA -
Release Procedure in PR .....
Hi SAP Gurus,
We do release procedure in PR with Account assignment category K.Here ,for collective release in pr (ME55),check box is disabled... Kindly help me how we enable the check box.We use scope of list as "F".All customization for release procedure is correct.
Thnks & Regards
SAP MM UserYou use this component if you wish to set up approval procedures for purchase requisitions or other purchasing documents. Under such a procedure, if a purchase requisition or external purchasing document fulfills certain conditions (e.g. the total order value exceeds $10,000), it has to be approved (by the cost center manager, for instance) before it can be processed further. This process of approving (clearing, or giving the "green light" to) a proposed item of expenditure is replicated in the SAP System by the "release procedure".
It is sensible to define separate release procedures for different groups of materials for which different departments are responsible, and to define separate procedures for investment goods and consumption goods.
Features
Each person involved in the release procedure effects release (signifies approval) via a release transaction, using his or her release code. Once effected, a release can also be cancelled with the same code (that is to say, the original status is reinstated).
If linkage to SAP Business Workflow has been defined for a release code, rejection is also possible. This is only possible for purchase requisitions.
Which Documents Can be Released (Approved)?
Release procedures can be defined for the following documents:
Purchase Requisition
The external purchasing documents purchase order (PO), contract, scheduling agreement, request for quotation (RFQ), and service entry sheet
Release Procedure for Purchase Requisitions
Two different procedures are available for requisitions:
With classification
With this procedure, requisitions can be released both at item level (i.e. item-by-item) and in total. The latter approach is also termed "overall release".
Without classification
With this procedure, requisitions can only be released at item level.
The two procedures are mutually exclusive (that is to say, you must decide in favor of one of them only - you cannot use both).
Release Procedure for External Purchasing Documents
External purchasing documents (i.e. purchasing documents other than requisitions) are released at header level. Item-by-item release is not possible. These documents can only be released using the release procedure with classification.
sri -
Release codes Indicators in Release procedure
Hi sap gurus
In my release procedure Configuration, we have 4 release codes
01 engineer
02 Manager
03 DGM
04 GM
the release indicators must be configured such that if any value changes or qnty changes is done by 04 GM code it must be re-released by 03 DGM only,
and it should go back to codes 01 and 02 for approval again,
i used 4 and 6 indicators for codes 04 and 06 but could not find any difference nor my requirement was met
can any one pls tell me how to meet the requirement.
1 Cannot be changed
2 Changeable, no new determination of strategy
3 Changeable, new release in case of new strategy
4 Changeable, new release in case of new strat. or val. change
5 Changeable, new release if new strategy/outputted
6 Changeable, new rel. if new strat. or value change/outputted
Changeable, new release in case of new strategy
also what is the change in codes 3,4, 5 and 6 .
Thanks and Regards
SathishGoto This thread http://www.sap123.com/showthread.php?t=59
it will explain you averything -
How to configure release procedure for rate contracts release
Dear all,
How to configure release procedure for rate contract following are the requirements
they are two release codes c1 & c2 <=100000,>=100000
if c1 is not there c2 has to be approved
Change in the value of the rate contract contract
Change in the validity of the rate contract
Addition of deletion of line items
While using a non u2013 released rate contract in the PO an error message should shoot out.
Also the logic should be changed while using the rate contract in the PO.
The usage of the rate contract should be till the validity of the rate contract. i.e. the measurement should be end date of the rate contract and the PO creation date and not the delivery date of the PO. &
It should be possible to refer existing valid rate contracts in purchase orders.
Regards,
bhaskarHi,
In SAP rate contract is known as value contract denoted with wk. The release procedure for rate contract is same as that of other contracts and scheduling agreements. The tables for contracts will vary with SA (Scheduling agreement) .You may try and maintain condition records based on the customer combination and maintian the validity date of condition records as per your requirement.For contract and PO will have the same header/item table as EKKO/EKPO, and the release
class in standard is the same FRG_EKKO, you can use the same for contract.
To distinguish if it's a contract or PO, EKKO-BSART can be used.
For contract EKKO-BSART will be MK or WK, while PO will have NB/UB etc..
You can restrict the document type to set up the release strategy for only contract.
Of cause, you can also create your own release class Z* for contract copying standard
one FRG_EKKO via CL01/Class type 032, and then assign the class Z* to customizing:
OLME:
-> contract
->Release Procedure for Contracts
->Define Release Procedure for Contracts
->Release Groups
If you have already created the PO release class.
Assign a new chracteristic of Document Category -BSTYP
Please check below link for detailed release procedure. I hope this wil help you out .Thanking you.
http://wiki.sdn.sap.com/wiki/display/ERPSCM/RELEASE+PROCEDURE#RELEASEPROCEDURE-TABLESUSEDFORRELEASEPROCEDURES -
Release procedure with classification not getting triggered
Hi,
I have configured the new release procedure for the PR release of type with classification, but its not getting triggered. Earlier my SAP system had without classification in place, but I wanted to have with classification. Can any one suggest how do I switch between two.
Ideally once I create the release group in with classification procedure that procedure gets activated and gets triggered. Unfortunately its not happening in my case. I tried deleting the entries from the without classification side too, but still it doesnt respond. Is there in patch or note missing.
Your suggestion would be highly appreciated.
sachinHi Jurgen,
I am configuring it for PR and with classification method. Well for simplification I am using just purchase group as characteristics, but still its not working. Earlier system had without classification in place, as its there in a default system and used to get triggered. When I created new procedure its not getting triggered. To be assured I deleted the data from witout classification, but still its not working.
Where as I did the same setting for PO, its working and giving me correct releaes strategy.
My characteristic is PRGRP using the communication structure CEBAN and field as EKGRP
Please suggest me on this.
sahcin
Edited by: sachin sagane on May 18, 2010 6:32 PM -
Steps to configuring log4j with plain text file
can anyone help me with the steps involved with configuring log4j with a plain text configuration file...Where should log4j.properties file be stored?.....do you have a simple example of a config file using a file appender?.....do I have to make changes within the startWebLogic.cmd script?.....Is it possible for you to lay out the procedure for me to begin logging?.....nothing I have tried thus far has worked.....Any help you may be able to provide will be greatly appreciated.
i am using sun jsf implementaion version 1.2
can i know do we need to specify anything for application bean to be called. beacause when i tried to print in sample application also my log was not getting printed.
i have mentioned in my managed bean
<managed-bean>
<managed-bean-name>ApplicationBean1</managed-bean-name>
<managed-bean-class>webapplication3.ApplicationBean1</managed-bean-class>
<managed-bean-scope>application</managed-bean-scope>
</managed-bean>
i my page class
protected webapplication3.ApplicationBean1 getApplicationBean1() {
return (webapplication3.ApplicationBean1)getBean("ApplicationBean1");
can i know why it is not getting called. -
Need consignment cycle steps with configuration
Hi all,
plz brief me abt the consignment cycle with the configuration steps.
regards,
nishith
<<Locked - reason: failed to search properly before posting question>>
Edited by: Csaba Szommer on Feb 7, 2011 9:46 AMHello,
Consignment is the act of consigning, which is placing a person or thing in the hand of another, but retaining ownership until the goods are sold or person is transferred. This may be done for shipping, transfer of prisoners, or for sale in a store (i.e. a consignment shop).
the material is at customers place and customer use it in portions and pays accordingly,liability of material is with vendor till
like in case of pertochem , it is been stored at refinering company premises adn the ref comp use it in portions and pays accordingly aslo the ref company get paid for the premises place
Features of consignment are:
1.The relation between the two parties is that of consignor and consignee and not that of buyer and seller
2.The consignor is entitled to receive all the expenses in connection with consignment
3.The consignee is not responsible for damage of goods during transport or any other procedure.
4.Goods are sold at the risk of consignor. The profit or loss belongs to consignor only.
in SAP consignment scenario is as follows
Consignment Info Record create with material and vendor.
Consignment Purchase Order (create with item catagery k)
Goods Receipt with movement type 101K
Consignment Stock to Own Stock,Transfer posting with
Movement type 411 k
Goods Issue to direct consuption 201K
Settlement throughu2014mrko
or Follow below links for more clear help.
Consignment scenario in SAP:
1) Process flow:
http://help.sap.com/bp_bblibrary/600/Documentation/J58_Scen_Overview_EN_DE.ppt#271,5,Component View u2013 Customer Consignment Processing
2) Configuration in SAP:
http://www.sap-img.com/sap-sd/consignment-sales-process-in-sap.htm
Regards
Mahesh Naik. -
How to configure sso with SSL step by step
Purpose
In this document, you can learn how to configure SSO with SSL. After user have certificate installed in browser, he can login without input username and password.
Overview
In this document we will demonstrate:
1. How to configure OHS support SSL
2. How to Register SSO with SSL
3. Configure SSO for certificates
Prerequisites
Before start this document, you should have:
1. Oracle AS 10g infrastructure installed (10.1.2)
2. OCA installed
Note:
1. “When you install Oracle infrastructure, please make sure you have select OCA.
2. How Certificate-Enabled Authentication Works:
a. The user tries to access a partner application.
b. The partner application redirects the user to the single sign-on server for authentication. As part of this redirection, the browser sends the user's certificate to the login URL of the server (2a). If it is able to verify the certificate, the server returns the user to the requested application.
c. The application delivers content. Users whose browsers are configured to prompt for a certificate-store password may only have to present this password once, depending upon how their browser is configured. If they log out and then attempt to access a partner application, the browser passes their certificate to the single sign-on server automatically. This means that they never really log out. To effectively log out, they must close the browser.
Enable SSL on the Single Sign-On Middle Tier
The following steps involve configuring the Oracle HTTP Server. Perform them on the single sign-on middle tier. In doing so, keep the following in mind:
l You must configure SSL on the computer where the single sign-on middle tier is running.
l You are configuring one-way SSL.
l You may enable SSL for simple network encryption; PKI authentication is not required. Note though that you must use a valid wallet and server certificate. The default wallet location is ORACLE_HOME/Apache/Apache/conf/ssl.wlt/default.
1. Back up the opmn.xml file, found at ORACLE_HOME/opmn/conf
2. In opmn.xml, change the value for the start-mode parameter to ssl-enabled. This parameter appears in boldface in the xml tag immediately following.
<ias-component id="HTTP_Server">
<process-type id="HTTP_Server" module-id="OHS">
<module-data>
<category id="start-parameters">
<data id="start-mode" value="ssl-enabled"/>
</category>
</module-data>
<process-set id="HTTP_Server" numprocs="1"/>
</process-type>
</ias-component>
3. Update the distributed cluster management database with the change: ORACLE_HOME/dcm/bin/dcmctl updateconfig -ct opmn
4. Reload the modified opmn configuration file:
ORACLE_HOME/opmn/bin/opmnctl reload
5. Keep a non-SSL port active. The External Applications portlet communicates with the single sign-on server over a non-SSL port. The HTTP port is enabled by default. If you have not disabled the port, this step requires no action.
6. Apply the rule mod_rewrite to SSL configuration. This step involves modifying the ssl.conf file on the middle-tier computer. The file is at ORACLE_HOME/Apache/Apache/conf. Back up the file before editing it.
Because the Oracle HTTP Server has to be available over both HTTP and HTTPS, the SSL host must be configured as a virtual host. Add the lines that follow to the SSL Virtual Hosts section of ssl.conf if they are not already there. These lines ensure that the single sign-on login module in OC4J_SECURITY is invoked when a user logs in to the SSL host.
<VirtualHost ssl_host:port>
RewriteEngine on
RewriteOptions inherit
</VirtualHost>
Save and close the file.
7. Update the distributed cluster management database with the changes:
ORACLE_HOME/dcm/bin/dcmctl updateconfig -ct ohs
8. Restart the Oracle HTTP Server:
ORACLE_HOME/opmn/bin/opmnctl stopproc process-type=HTTP_Server
ORACLE_HOME/opmn/bin/opmnctl startproc process-type=HTTP_Server
9. Verify that you have enabled the single sign-on middle tier for SSL by trying to access the OracleAS welcome page, using the format https://host:ssl_port.
Reconfigure the Identity Management Infrastructure Database
Change all references of http in single sign-on URLs to https within the identity management infrastructure database. When you change single sign-on URLs in the database, you must also change these URLs in the targets.xml file on the single sign-on middle tier. targets.xml is the configuration file for the various "targets" that Oracle Enterprise Manager monitors. One of these targets is OracleAS Single Sign-On.
1. Change Single Sign-On URLs
Run the ssocfg script, taking care to enter the command on the computer where the single sign-on middle tier is located. Use the following syntax:
UNIX:
$ORACLE_HOME/sso/bin/ssocfg.sh protocol host ssl_port
Windows:
%ORACLE_HOME%\sso\bin\ssocfg.bat protocol host ssl_port
In this case, protocol is https. (To change back to HTTP, use http.) The parameter host is the host name, or server name, of the Oracle HTTP listener for the single sign-on server.
Here is an example:
ssocfg.sh https login.acme.com 4443
2. Restart OC4J_SECURITY instance and verify the configuration
To determine the correct port number, examine the ssl.conf file. Port 4443 is the port number that the OracleAS installer assigns during installation.
If you run ssocfg successfully, the script returns a status 0. To confirm that you were successful, restart the OC4J_SECURITY instance:
ORACLE_HOME/opmn/bin/opmnctl restartproc process-type=OC4J_SECURITY
Then try logging in to the single sign-on server at its SSL address:
https://host:ssl_port/pls/orasso/
3. Back up the file targets.xml:
cp ORACLE_HOME/sysman/emd/targets.xml ORACLE_HOME/sysman/emd/targets.xml.backup
4. Open the file and find the target type oracle_sso_server. Within this target type, locate and edit the three attributes that you passed to ssocfg:
· HTTPMachine—the server host name
· HTTPPort—the server port number
· HTTPProtocol—the server protocol
If, for example, you run ssocfg like this:
ORACLE_HOME/sso/bin/ssocfg.sh http sso.mydomain.com:4443
Update the three attributes this way:
<Property NAME="HTTPMachine" VALUE="sso.mydomain.com"/>
<Property NAME="HTTPPort" VALUE="4443"/>
<Property NAME="HTTPProtocol" VALUE="HTTPS"/>
5.Save and close the file.
6. Reload the OracleAS console:
ORACLE_HOME/bin/emctl reload
7. Issue these two commands:
ORACLE_HOME/opmn/bin/opmnctl restartproc process-type=HTTP_Server
ORACLE_HOME/opmn/bin/opmnctl restartproc process-type=OC4J_SECURITY
Registering mod_osso
1. This command sequence that follows shows a mod_osso instance being reregistered with the single sign-on server.
$ORACLE_HOME/sso/bin/ssoreg.sh
-oracle_home_path $ORACLE_HOME
-config_mod_osso TRUE
-mod_osso_url https://myhost.mydomain.com:4443
2. Restarting the Oracle HTTP Server
After running ssoreg, restart the Oracle HTTP Server:
ORACLE_HOME/opmn/bin/opmnctl restartproc process-type=HTTP_Server
Configuring the Single Sign-On System for Certificates
1. Configure policy.properties with the Default Authentication Plugin
Update the DefaultAuthLevel section of the policy.properties file with the correct authentication level for certificate sign-on. This file is at ORACLE_HOME/sso/conf. Set the default authentication level to this value:
DefaultAuthLevel = MediumHighSecurity
Then, in the Authentication plugins section, pair this authentication level with the default authentication plugin:
MediumHighSecurity_AuthPlugin = oracle.security.sso.server.auth.SSOX509CertAuth
2. Restart the Single Sign-On Middle Tier
After configuring the server, restart the middle tier:
ORACLE_HOME/opmn/bin/opmnctl restartproc process-type=HTTP_Server
ORACLE_HOME/opmn/bin/opmnctl restartproc process-type=OC4J_SECURITY
Bringing the SSO Users to OCA User Certificate Request URL
The OCA server reduces the administrative and maintenance cost of provisioning a user certificate. The OCA server achieves this by authenticating users by using OracleAS SSO server authentication. All users who have an Oracle AS SSO server account can directly get a certificate by using the OCA user interface. This reduces the time normoally requidred to provision a certificate by a certificate authority.
The URL for the SSO certificate Request is:
https://<Oracle_HTTP_host>:<oca_ssl_port>/oca/sso_oca_link
You can configure OCA to provide the user certificate request interface URL to SSO server for display whenever SSO is not using a sertificate to authenticate a user. After the OracleAS SSO server authenticates a user, it then display the OCA screen enabling that user to request a certificate.
To link the OCA server to OracleAS SSO server, use the following command:
ocactl linksso
opmnctl stoproc type=oc4j instancename=oca
opmnctl startproc type=oc4j instancename=oca
You also can use ocactl unlinksso to unlink the OCA to SSO.I have read the SSO admin guide, and performed the steps for enabling SSL on the SSO, and followed the steps to configure mod_osso with virtual host on port 4443 as mentioned in the admin guide.
The case now is that when I call my form (which is developed by forms developer suite 10g and deployed on the forms server which is SSO enabled) , it calls the SSO module on port 7777 using http (the default behaviour).
on a URL that looks like this :
http://myhostname:7777/pls/orasso/orasso.wwsso_app_admin.ls_login?Site2pstoreToken=.......
and gives the error :
( Forbidden
You don't have permisission to access /sso/auth on this server at port 7777)
when I manually change the URL to :
https://myhostname:4443/pls/orasso/orasso.wwsso_app_admin.ls_login?Site2pstoreToken=.......
the SSO works correctly.
The question is :
How can I change this default behaviour and make it call SSO on port 4443 using https instead ?
Any ideas ?
Thanks in advance -
With classification release procedure for PO
Dear Experts ,
here one issue is with classification release procedure for PO
when I create characteristics
in Additional data
table name :-- Cekko field name :-- match code
enter
click all sec charars then which block I select to go next screen
and fill name is right or ?
please help mehi,
in additional data field you have to give the field name of characteristic you are maintaining. like if you want to maintain characteristic as document type of the PO then we have to give the field name for document type mentioned in table CEKKO i.e. BSART.
then you have to do the value assignment. here you have to tick the check box for "NOT READY FOR INPUT".
JASH -
Release procedure with out classification
HI, AJIT SINGH HERE,
after making proper settings in the 'release procedure with out classification', when i try to create a puchase requisation by ME51N to test the working of release procedure ,i'm not getting check boxes of approval levels.
please guidehi
did u took the pur grp as the chrecteristic for release
if yes then put the value of pur grp in release strategy
plz check ur release strategy as per follows
http://www.sap123.com/showthread.php?t=59
http://www.sapstudymaterials.com/search/label/0270-MM%20Configuration%3A%20PR%20Release%20Strategy%E2%80%93Basic%20Concept
regards
kunal
Maybe you are looking for
-
Cannot DELETE rows from LOV on running...is it a bug ??
One of the features I appreciated in the new version of JHeadstart is that we can now insert, modify and delete rows on LOV (even in the database). We have just to check on Lookup properties : Multi-row insert allowed Multi-row update allowed Multi-r
-
Converting songs already on my computer to itunes...
The day i got my ipod i started to convert all the songs on my computer to itunes, but it started storming so i had to shut the computer down. does anyone know how to get it started back converting the songs?
-
Oracle apps forms doesnot load froom java
Hi My ebiz version is oracle appications r12.1.3 with 11.2.0.3 database When i click the security >user_define for opening the forms the forms windows doesnot appear JAVA doesnot load and i dont see any java icon on the bottom right corner of my syst
-
Hi All, Is it possible to have a degault values to the texts maintained in PO header. or is it possible to have content of standard text available as default to this header text. The requirement is to choose between different header texts available i
-
If I make a little picute in pages ... HOW DO I DUPLICATE THE IMAGE MULTIPLE TIMES ON THE SAME PAGE!11?????!!!!