Does anyone run java dynamic connector in E1 Standalone 812 (Tools 896) successful?

[arksue]

I found many posts befofe that no one seems to run this connector successful.

My environment is E1 Standalone 812 (Tools 896) in win2003 & msde.

According to e1_tools896tcn-b_0406.pdf(JD Edwards EnterpriseOne Tools 8.96 Connectors Guide),

I made some code like below.

BSFNSpecSource specSource = null;
// Step 1: Login
int sessionID = Connector.getInstance().login("DEMO", "DEMO", "DEMO812","*ALL");
System.out.println("ok1");

// Step 2: Get specSource
specSource = new OneworldBSFNSpecSource(sessionID);
System.out.println("ok2");

// Step 3: Get specSource
BSFNMethod bsfnMethod = specSource.getBSFNMethod("GetEffectiveAddress");
System.out.println("ok3");

Step1 and Step2 are ok, so I made sure my code could login jde server and got a sessionID.

It failed in Step3 as bellow exception log.

[SEVERE] - [com.jdedwards.system.connector]Fail to connect to Oneworld Spec Source: null

But in the jas log, there were no errors.

Does anyone know how to solve this error?

By the way, in the jdeinterop.ini, I set OCMEnabled=ture.

Then I used OCM to set B0100033 to Mpapping the Data Source(Local - DEMO Specs) in jde client and change the status is AV.

But the error still happened.

I also tried other Data Source to map,but it didn't work.

 

[ronbapa]

Re: Does anyone run java dynamic connector in E1 Standalone 812 (Tools 896) successful?

I spent countless hours looking for this info. Finally got it to work. Try this
1. Copy these files from the PeopleSoft EnterpriseOne server to a directory on the machine that you want to use:
• Connector.jar
• kernel.jar
• jdeutil.jar
• database.jar
• log4j.jar
• xerces.jar
• jdeinterop.ini
• jdbj.ini
• jdelog.properties
• JDBC drivers (obtain the JDBC drivers from the database vendor)
For example, you might copy the files to this directory on the machine:
C:\PeopleSoft\Interop
2. Add these files to the CLASSPATH:
• Connector.jar
• kernel.jar
• jdeutil.jar
• database.jar
• log4j.jar
• xerces.jar
• JDBC drivers
3. Add the path where the jdelog.properties, jdeinterop.ini, and jdbj.ini files are located into CLASSPATH.
4. Edit jdeinterop.ini, jdelog.properties, and jdbj.ini for proper settings.
Running the Dynamic Java Connector
This section discusses:r
• Calling a business function.
• BSFN cache.
• Transaction using the dynamic Java connector.
• OCM support for the dynamic Java connector.
Calling a Business Function
If you know the business function name and the parameters (data items) associated with the business function, you can use the dynamic Java connector to call the business function. The dynamic Java connector does not require pre-generated wrappers. This code sample shows you how to use the dynamic Java connector to call a business function:
// Step 1: Login
int sessionID = Connector.getInstance().login("user", "pwd", "env",
"role");

// Pre-condition: create the SpecDictionary or BSFNSpecSource

// Step 2: Lookup the BSFN method from SpecDictionary or BSFNSpecSource
BSFNMethod bsfnMethod = (BSFNMethod)specSource.getBSFNMethod
("Get EffectiveAddress");

// Step 3: create the executable method from the BSFN metadata
ExecutableMethod addressbook = bsfnMethod.createExecutable();

try {
// Step 4: Set parameter values
addressbook.setValue("mnAddressNumber", "1");
// Step 5: Execute the business function
BSFNExecutionWarning warning = addressbook.execute(sessionID);
// Step 6: Get return parameter values

System.out.println("szNamealpha"= + addressbook.getValueString
("szNamealpha"));
// Get the warnings if any
if (warning.hasWarnings()){
String warningMsgs[] = warning.getWarningMessages();
for (int i=0;i<warningMsgs.length;i++){
System.out.println(warningMsgs);
}
}
}catch (SystemException e) {
//SystemException is thrown when system crash, this is a fatal
//error and must be caught
System.exit(1);
} catch (ApplicationException e){
// ApplicationException is thrown when business function
// execution fail, this is RuntimeException and thus can be
// unchecked. But it is strongly recommend to catch this
// exception
} finally {
//Log off and shut down connector if necessary
connector.logoff(sessionID);
connector.shutDown();
}

 

[arksue]

Re: Does anyone run java dynamic connector in E1 Standalone 812 (Tools 896) successful?

Dear Ronbapa
Thanks for your replying

May I know if you tried in E1 Standalone 812 successful or other Jde version?

The steps you provided I have done.

I think the problem is how to config the data source in OCM of jde client.

Did you conifg that I mean you use OCM to set a business function to Mpapping the Data Source?

 

[ronbapa]

Re: Does anyone run java dynamic connector in E1 Standalone 812 (Tools 896) successful?

Sorry, I got it configured with 811.

Check out the thread at OTN
http://forums.oracle.com/forums/thread.jspa?messageID=3163228

 

[arksue]

Re: Does anyone run java dynamic connector in E1 Standalone 812 (Tools 896) successful?

[ QUOTE ]
Sorry, I got it configured with 811.

Check out the thread at OTN
http://forums.oracle.com/forums/thread.jspa?messageID=3163228

[/ QUOTE ]

Dear Ronbapa

That's ok. Finally I have run it successful on our es not in standalone. The key is setting of OCM. I think maybe the standalone has lack of these parts.
Anyway thanks for your replying.