Interest indicator configuration steps

I have configured Interest indicator like below but while testing new interest indicator in FINT t-code i am getting "Maintain the customizing for the new intrest program error" pleas help me how to resolve that that error.
First create an Interest Indicator.
OB46 - Interest Settlement Calculation Type
Int Calc. Type
P - calculate interest based on line items.
S - calculate interest based on account balances.
Secornd, make it avaliable to the interest run program.
OB82 - Interest Terms
Third, determine the interest rate that will be used by the calculation.
OBAC - Define Reference Interest Rates
OB83 - Enter the Reference Interest Rates Value
Fourth, assign the interest indicator to the reference interest rate.
OB81 - Define Time Dependent Terms
Finally, determine the how and to which accounts the interest program will post.
OBV1 - Prepare Interest on Arrears Calculation

The forum [FPM - General|Enterprise Performance Management (SAP EPM); in which you originally posted your question deals mainly with the financial performance applications otherwise known as Enterprise Performance Management (EPM) carrying the BusinessObjects brand. Your question pertains to SAP [ERP Financials|SAP ERP Financials; which is covered by another forum. Therefore your message has been moved. Please adjust any bookmarks you might have and post to the appropriate area in the future, that way you are assured you will have the right audience reading your posts.
Thanks and best regards,
[Jeffrey Holdeman|http://wiki.sdn.sap.com/wiki/display/profile/Jeffrey+Holdeman]
SAP Labs, LLC
BusinessObjects Division
Americas Applications Regional Implementation Group (RIG)

Similar Messages

Configuration steps to create New Special GL

HI,
Can any one please send me configuration steps to create New Special GL. My client required to create new special GL for Rent Advance.
NOTE: hear I am not asking how configuration steps for assigning GL accounts for existing Special GL. I want new Special GL to be Create for rent advance.
Its very urgent
My mail id "[email protected]"
Thank you
mahesh

Hi,
go to transaction code fbzp where you assign GL account to the spl GL indicator.
Go and create a new spl GL indicator there by clicking create new.
Bye

Give me the Configuration steps for intercompany billing and third party s

Hi Gurus,
Give me the Configuration steps for intercompany billing and third party sales and give me a brief description with examples.
Regards,
YSR

Dear YSR
Check the links
[Cross Company Configuration|http://help.sap.com/bp_bblibrary/500/Documentation/J62_BB_ConfigGuide_EN_DE.doc]
[Third Party Without Shipping Notification|http://help.sap.com/bestpractices/BBLibrary/html/J55_ThirdPartyWOSN_EN_US.htm]
Third party order processing is as follows:
Assume three companies X, Y and Z
X - The company,
y - The customer
Z - Vendor
When ever X gets a PO from Y to supply some goods, X has an option of either manufacturing those goods or procuring those goods.
If he is procuring the goods, there are two methods that are generally followed:
Method 1)
After receiving the PO from Y, X creates a sales order against Y.
Now at the same time he also creates a PO to a vendor Z to produce the goods
Z produces the goods and supplies to X
X receives the goods from Z
Then X delivers the same goods to Y.
After that X invoices Y and Z invoices X.
Note : Here there is no direct/ Indirect relation between Z and Y.
This process is known as Trading Process. and the Material here is created with Material type HAWA.
The other method is a Third party order processing method:
Here the glaring difference is that instead of Z supplying the material to X and X in turn supplying the same material to Y.
X authorizes Z to supply the material to Y on his behalf and notify him once the delivery is complete.
Now Z supplies the material to Y and acknowledges the same to X.
Z will send a copy of delivery acknowledgement and invoice to X.
After receiving the delivery confirmation and invoice from Z, X has to verify the invoice and this process is known as invoice verification and is done in SAP through Tcode MIRO.
The next step for X is to create an invoice and submit to Y
Only after the invoice verification document is posted then only X can create an invoice for Y.
This is the business flow that is followed for third party order configuration.
There are few steps that have to be configured to enable the system to function as mentioned above.
Step1)
If you are always followwing a third party process for a material then you have to create the material using item category group BANS.
The procument type should be marked as External procurement (F) in MRP 2 view of the material master record.
if you are not always allowing third party order processing then u can create a material master record with item category group as NORM and the procurement type should be marked as ( X) meaning both types of procurment ( in house manufacturing and external procurement).
Step 2)
the item category in the order should be manually changed as TAS.
For that you need to confugure the item category determination
ord type + item cat grp + usge + Hiv level = Item cat + Manual item cat
OR + NORM + + = TAN . + TAS
OR + BANS + + = TAS
Step 3)
make sure that during the item category configuration for TAS you need to mark relevnat for billing indicator as F
Step 4)
The schedule line cateogry for this type should be CS.
make sure that you mark subsequent type as NB - purchase requisition in this schedule line category as this will trigger the purchase requision order immediately after the creation of the sales order and the PO to vendor is created against this purchase requiesion.
thanks
G. Lakshmipathi

Send faxes through F110 and Interest Indicator

Hello all,
we have SAP ECC 6.0. , and it is needed to send faxes through F110 ,
1) I would like to know the steps to send a fax through the f110 transaction
2) Only send faxes for the vendors with interest indicator
3) Do you know some user exit to calculate interest with different interest indicators?
Regards
Olga

Hi Olga,
For customers, to use different interest rates, and calculate the interest amount in the payment file created by transaction F110, program RFFOBR_A, you need to:
1) Go to "Define Interest Calculation Types", in customizing (SPRO).
2) Go to "Define Reference Interest Rates" in customizing (SPRO).
3) Go to "Define Time-Based Terms" in customizing (SPRO).
4) Go to Enter Interest Values in customizing (SPRO).
After, go to the customer master data, Company Code data, folder account management and fill the field "Interest Indicato" with the code created in the step 1 above.
When you run the proposal, the payment file will have the interest amount calculated considering the billing amount and the interest rate defined to the customer.
Her in Brazil, we work in this way.....
I hope that this could help you solve your issue....!!!!
Best Regards,
Francisco Moya

Need complete Configuration steps for creating Shipment & Shipment costs.

Hi,
Can anybody explain the Configuration steps in IMG required to create Shipment (T Code - VT01) & Shipment costs (VI01).
Thanks in advance.
Manjunath.

hi
Route can be determined in sales order with the help of 5 parameters: depart country, shipping conditions in customer master record, transportation group in material master, destination country, and weight group.
Weight group plays a vital role. The purpose of route determination is like in scenario's where company will ship goods to the customer in various ways not only that it has optional of having n number of routes select the best one & based on his customer priority (time & money.) for sending samples company will go for air, for delivering ordered goods it can go for different mode of transportation & routes.
Route Determination: Departure country zonedestination country zoneshipping condition+ transportation Group+Weight Group ( Optional)= Route.(0VRF)
Plant determination in the sales order: System will search first for Customer material Info Record, if it is not maintained there it will check for customer master record, if it is not maintained here also system will search for material master record..
Configuration part:
SPRO > Routes Basic shipping functions  Shipping -LE -
Define Routes:
Define mode of transportation
Define shipping types.
Assign shipping types to mode of transportation.
Define Routes and Stages
Maintain Stages For All Routes
Route Determination:
Define Transportation Zones
Maintain Country And Transportation Zone For Shipping Point
Define Transportation Groups
Define Weight Groups
Maintain Route Determination in the combination of
a) Departure country/Departure Zone - maintained in shipping point configuration
b) Shipping condition from the sales order
c) Transportation planning group maintained in General/Plant view of material master.
d) Destination country/Transportation zone maintained in General view -Address of Customer master of Ship to Party.
SHIPMENT COST:
Shipment cost in shipping contains create the shipment cost doc., process the shipment, monitor the shipment, calculate the shipment and settle the shipment.
Shipment cost doc. contains calculate the shipment, assign to accounting, transfer to FI and settle the shipment cost.
Shipment cost doc. divided into header, item and sub item data.
We need to assign transportation planning point to com. code to calculate and settle the shipment cost.
1. Define date rules:- In this IMG activity you define the date rules that determine which dates are chosen for determining the pricing date and the settlement date and the sequence in which they are accessed. The dates can be, for example, the end of transportation planning or the start of lading.
2. Define and assign tariff zones:-In this IMG activity, you define the tariff zones and assign postal code areas to the tariff zones for each organizational key. The tariff zones are represent geographical influencing factors during the calculation of shipment costs.
3. Define no. ranges for shipment cost:-In this IMG activity you define the number interval for the shipment cost documents. When creating a shipment cost document, a unique number is generated. The number comes from the number range that you create in this menu point as the internal number range.
You can also create an external number range. The option to specify a number from the external number range when creating the shipment cost document is, however, not currently supported.
4. Shipcost types and item cat.:-In this IMG activity, you define the shipment cost types and item categories that contain all important control features for the shipment cost document, such as:
Number range
Status requirements for the shipment documents
Parameters for shipment costing
Parameters for shipment settlement
5.shipcost relevance and default for shipcost types:-In this IMG activity you assign the shipment cost types to the shipment types and set an indicator to show whether the cost type is relevant to shipment costing. You do this for every cost type in every shipment type. .
Example
For the 'individual shipment' shipment type, you set the indicator for the cost types shipment header and leg, but not for the cost types border crossing or load transfer point. You also assign a shipment cost type to the shipment type. When you create a shipment cost document, this shipment cost type is determined automatically.
6. Settlement:-
Certain control elements must be maintained for calculating shipment costs with the transportation service agent and for forwarding of shipment costs to FI and CO.
you can maintain these control elements and carry out the corresponding assignments.
-- Assign purchasing data
--maintain acc. assignment cat.
--automatic G/L acc. determination
--automatic determination of CO assignments
--invoices and credit memos
The process of calculating the shipment costs for a shipment.
Shipment costs:
The total costs involved in the shipment of a product. Not just pure freight costs, but also cleaning costs, insurance, and other costs as well
check this link
http://help.sap.com/saphelp_46c/helpdata/en/4f/fceb47b535d1118b3f0060b03ca329/frameset.htm
and
http://help.sap.com/saphelp_470/helpdata/en/d5/2285347860ea35e10000009b38f83b/frameset.htm

CIN-MM Configuration steps required for First Stage Delaer purchases.

Hi,
I am looking for CIN-MM Configuration steps required for First Stage Delaer purchases.
We have steps Configured for CIN-MM from Manufacturer for purchase of Materials and Capital Goods.
Thanks in advance.
Regards,
Purna.

Hi Purnachandrarao... ,
There is no seperate configuration required in dealer's case.
For this you have to use zero Tax code.Material should be maintained in J1id.
So that Tax % will be picked up from there.
But at the time of GR you have to tick MRP indicator in excise tab.
And also you have to change values of BED and cess as per vendor's invoice.
So that value will be fetched at the time of invoice verification.
Regards,
Gitesh

OBIEE 11g installation failed multiple times at Distributing Repository Configuration Step

Hi,
I am getting the following error during the Distributing Repository Configuration step in the OBIEE 11g 11.1.1.7 enterprise installation in Windows 8 system.
Severe: Element Type:Domain
Element id: null
Operation result: failed to obtain domain file lock
Detail Message: java.util.concurrent.timeoutException.Timeout;
waiting for lock: Domain config lock;
c:\OBIEE\MIDDLE~1\USER_p~1\domains\EAM_DO~1\config\FMWCON~1\biee-config.lock;[121 secs]
Step Distributing Repository failed
Configuration Action 'Distributing Repository' has failed. Please check logs for details.
Step Distributing repository failed
I checked another blog for this https://forums.oracle.com/thread/2565716 and even there the explanation doesn't convince me.
I tried to look at the Locale of my system where I am installing and I could see it is using Eng-Us by default. One way suggested to check the Unicode format from the web browser and I could check that too to be UTF-8 as suggested by someone on some other blog.
I checked in the logs too as suggested by the Installation dialogue box but it didn't seem much conclusive too.
Here is the snapshot of the log file which I could found.
INFO: Current Inventory:
Oracle Home: OraDb11g_home1
This Oracle Home has not been changed in this session.
Oracle Home: OH1858390736
This Oracle Home has not been changed in this session.
Oracle Home: OH440082373
This Oracle Home has not been changed in this session.
Oracle Home: OH440082374
This Oracle Home has not been changed in this session.
Oracle Home: OH1597391518
This Oracle Home has not been changed in this session.
Oracle Home: OH1285215443
This Oracle Home has not been changed in this session.
INFO: Ending the inventory Session
INFO: Using an existing InstallAreaControl for this Inventory Session with existing access level 1
INFO: Using an existing InstallAreaControl for this Inventory Session with existing access level 1
INFO: Using an existing InstallAreaControl for this Inventory Session with existing access level 1
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
Can someone please help me with this since I am stuck with for quite some time now.
Is there any way to check in command prompt to check the locale as required by the system.
What could be the issue here?
Thanks,
Nitin

Hi all,
We are able to resolve the above issue with the below solution.
Root cause of the issue:
You may have a temp directory in the path C:\Documents and Settings\user_name\Local Settings\Temp. You got the above mentioned exception because of the temp directory path having spaces_+ in it.
Solution:
1. Create a new directory called TEMP in a different location for ex: C:\TEMP
2. Now, Right click on My computer --> Properties --> Advanced --> click on Environment Variables.
3. You should be having TEMP and TMP as variables under user variables section pointing to the C:\Documents and Settings\user_name\Local Settings\Temp path.
4. Edit the TEMP and TMP variables and mention C:\TEMP in the variable value.
5. Deinstall and re-install OBIEE 11g.
Happy OBIEE 11g installation!!
Thanks,
Rajesh Gurram

Product costing by sales order configuration steps

hi
plz send me product costing by sales order configuration steps.
sir, i know manufacturing order configuration step but i do not sales order configuration.
in the sales order also is same as manufacturing order like first we have to make planning cost , the planning cost should be updated to material master and next configure the actual cost.
for first step- costing variant -okkn
next -costing variant -opl1
for sales order also same we need to update planning price first- what is costing variant
for actual cost - what is costing variant
plz tell me detail
regards,
sowmya
Moderator: Please, read forum rules before posting

Hi Sashikanth,
Please send me the Configuration document for make to sales order.We are at Blue print stage need some docment for make to sales order.Plese send me the document it will will be very help full for me.
My id is [email protected]
Thanks in advance
Regards,
Nagaraju
Edited by: nagaraju sami on Mar 9, 2008 11:58 AM

Which driver to use in the BPM Configuration Steps?

Hi,
I´m in the BPM configuration steps and we will use BPM on a Weblogic Server, I´m in the step when you need to create to JDBC Data Sources for the Enterprise and Directory Databases, do you know which driver shoul I use? should it be XA o Non-XA?
Thanx in Advanced!
Kind Regards,
Gerardo J

Since there are no drivers, you can create your own, request one, use the Instrument I/O Assistant, or hope someone has one and posts it here. For help on creating one or requesting one, see the main Instrument Driver Network page. As long as you are familiar with the instrument and have the manual, creating a driver is not that hard.

Configuration steps for Extended Classic Scenario

Hi All,
Could you please let me know what are the configuration steps required for extended classic scenario.
Thanks in advance

Hi,
Important Settings that Determine the Extended Classic Scenario
The following settings are required for the extended classic scenario:
u2022 At least one backend materials management system and accounting system is connected to the SAP SRM system and defined in the configuration setting Define Backend Systems.
u2022 Product categories from the backend procurement system are replicated and used in the SAP SRM system.
u2022 The target system for each product category is the backend system in the configuration setting Define Backend Systems for Product Category. Optionally, BADI BBP_DETERMINE_LOGSYS is implemented to determine the backend system.
u2022 The extended classic scenario is activated in the configuration setting Activate Extended Classic Scenario. Alternatively, BAdI BBP_EXTLOCALPO_BADI is implemented to control the extended classic scenario based on customer defined rules.
u2022 If the backend system is an SAP R/3 version lower than 4.6B, you must define local purchasing organizations and purchasing groups.
u2022 If the backend system is an SAP R/3 version 4.6B or higher, you need to map the purchasing group used in the purchase order to the backend purchase group in one of the following ways:
u2022 Use a backend purchasing organization and purchasing group in the shopping cart and purchase order.
u2022 Use BAdI BBP_PGRP_FIND to determine a backend purchasing group in the shopping cart.
u2022 If a local (created in SAP SRM without reference to a backend system) purchasing group and purchasing organization are used, then a valid backend purchasing group is assigned to the RFC user that created the backend purchase order. This assignment is made in the backend system using user parameter EKG in Transaction code SU01.
u2022 Implement the user exit of the BAPIs BAPI_PO_CREATE1 (EXIT_SAPL2012_001 and EXIT_SAPL2012_003), and BAPI_PO_CHANGE (EXIT_SAPL2012_002 and EXIT_SAPL2012_004) to determine the purchasing group with a customer- specific logic.
This is for your additional information.
Hope this helps.
Regards,
Vikas

Interest indicator on customer

Hi
Suppose customer does not make payment in with in the due date.
at that time, we want to calculate interest on outstanding amount.
what is the process
please
thanks
vas

Dear Vas,
to build up the interest calculation settings, You have to go to IMG --> Financial accounting >Financial Accounting Global Settings>Accounts Receivable and Accounts Payable>Business Transactions> Interest Calculation
and to customize all the relevant points:
Define Interest Calculation Types
Prepare Interest on Arrears Calculation
Prepare Item Interest Calculation
or
Prepare Account Balance Interest Calculation
then You have to define
Prepare Account Balance Interest Calculation
Define Time-Based Terms
Enter Interest Values
then define into the posting part
A/R: Calculation of Interest on Arrears where You have to link the G/L Account to
the symbols and to the currency
Then You have to link the interest indicator to Your Customer master data under the TAB "Account management" and run the report
RFINTITAR (FINT transaction)for customers of RFINTITAP (FINTAP transaction)for vendors.
These reports use the Form F_INTITAR_SF SMARTFORM.
I hope this can help You.
Mauri

Business partner configuration steps in treasury

Reqiure Business partner configuration steps in treasury.
While creating business partner i get the message :Personal address doesnot exist.
How to rectify this?

No reply.Closed.

Error at DB downtime configuration step in SAP installation

Hello Gurus,
While installing CRM IDES 5.0 I am stuck at DB downtime configuration (step 9). After shutting down MSSQL server services are not automatically started. In usual case it should be. Its giving "could not start the MSSQLSERVER" service on host. And my MSSQL services are not starting either it is giving Named pipes provider, error:40 - could not open a connection to SQL Server. If any one faced similar kind of problems sugguest on this.
Regards,
Murali

Check your event log why your database is not coming up.
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.

Configuration Steps for Decentralized Adapter Engine

Hi all,
What all configuration steps are required to make Adapter Engine as
Decentralized AE.
I have made required changes in SLD DataSupplier in Visual Administrator.
what more configurations have to be done? On SAP XI Server and Decentralized
Adapter Engine.
With regards
Prasad

Prasad,
After configuring SLD data supplier in Visual Admin, you need to the following
1) Configure the gateway service for the central integration server on adapter engine host.
2) Perform Initial adapter engine cache refresh
3) Trigger data transfer to SLD
4) Check the connection parameters in exchangeProfile
5) Create HTTP destination pmistore in java environment
you have to go through all these tests for decentralized adapter engine. If you have XI configuration guide, it has all these steps in detail for you to configure
--Archana

Interest indicator configuration steps

Similar Messages

Maybe you are looking for