JDeveloper and Fusion Applications Explained (Part 2)

In the first part of this series we explained how to find the appropriate version of JDeveloper for your Fusion Applications customization or extension project.  We also covered the installation.  This second post walks you through the next steps on your journey: we will launch JDeveloper with the necessary parameters and configure the domain of the integrated WebLogic Server (WLS).

A prerequisite for using JDeveloper that is somewhat buried in the Developer Guide (Rel 6 edition) is Python.  Specifically, you need Python 2.7.x.  Some versions of the documentation list Python 2.4 as the minimum version, but I have never seen anyone actually get this to work, so the guide was updated and should now list 2.7. Do not, however, try it with version 3.x of Python: there are significant incompatibilities between the 2.7.x series and the 3.x series of the language, and 3.x does not work for our purposes.  You may be wondering what Python is actually needed for, given that JDeveloper itself is written in Java and Fusion Applications does not use Python as a programming or scripting language.  Well, it turns out the JDeveloper extension that configures the WebLogic Server domain to run Fusion code is written in Python.

The Fusion Applications Developer Guide documents a number of environment variables that need to be set before JDeveloper can be launched.  For the purpose of this blog post we are looking at Windows as the host operating system; Linux-based developers can hopefully easily adjust the necessary syntax.  One way to define the environment variables is by adding them to a little launch script (let's call it launchjdev.cmd).  For example:

 JDeveloper Launch Script

Copy/paste-able version – be sure to adjust for your machine’s specific directories: 

set MW_HOME=C:\Oracle\Middleware
set JAVA_HOME=%MW_HOME%\jdk160_24
set PATH=%JAVA_HOME%\bin;c:\PYTHON27;%PATH%
set JDEV_USER_HOME=c:\Projects\FaDevRel
set FADEV_VERBOSE=true
set USER_MEM_ARGS=-Xms256m -Xmx1024m -XX:MaxPermSize=512m -XX:CompileThreshold=8000
%MW_HOME%\JDeveloper\jdev\bin\jdev

The JDEV_USER_HOME variable defines the location where JDeveloper by default puts workspaces.  It is also the location of the "System" directory, home of many JDeveloper settings.  And the Default Domain of the integrated WebLogic Server resides in the "System" directory.

Instead of a launch script you can also set up the environment variables using the standard Windows mechanism (System Properties dialog).  I prefer the script because it's easier for me to see what the settings are and to modify them as appropriate.

Run the launchjdev.cmd script and choose the pre-selected Default role.  We have not yet installed the Fusion-specific extensions.  As you will see in a minute, they will add additional roles.  Once JDeveloper has completely launched, dismiss the Tip of the Day dialog and choose "Check for Updates" from the "Help" menu.  In step 2 of the wizard click the "Add" button (note: if you are behind a corporate firewall, you may be prompted to enter information about your proxy server before you can click the button).  With the help of the "Add" button we're adding a local (on your disk) update center from which JDeveloper can install extensions.  Enter a meaningful name and then select via the "Browse" button the fusion_apps_updatecenter.xml file from your unzipped Companion DVD/zip file (see part 1 for details).  It should be in a directory called "fusion_apps_extensions" together with a lot of zip files (the actual extensions).

Adding Local Update Center

Adding Local Update Center 

Back in Step 2 of the Wizard, make sure the only update center that is selected is the local one you just added before moving on to Step 3.  Here you select "Fusion Apps Development Environment 11.1.1.x" extension (version depends on your release) and that will automatically also select all the dependent extensions.

Select the Fusion Applications Development Environment Extension

Select the Fusion Applications Development Environment Extension

Click "Next" and the extensions will be installed.  JDeveloper will claim that it is "downloading" updates, but those are really pulled from the local update center (=files) on your disk and copied into the JDeveloper MW_HOME.  Step 5 of the wizard then confirms which extensions and their versions were installed.  As you can see, quite a few were added to the base JDeveloper install that we started out with.

The List of Newly Installed Extensions

Close the wizard and confirm that you want to restart JDeveloper at this time to enable the extensions. The IDE will close, and it will appear that nothing else is happening.  But resist the temptation to restart it manually and just leave the computer alone for a couple of minutes: JDeveloper will in fact "magically" start again and present you with the role picker.  It may seem that nothing changed, but if you scroll through the list of roles, you should at the end see two new roles that were provided by the extensions we installed: 

The New Roles

The "Oracle Fusion Applications Administrator Customization" role is only used to create meta-data customizations. For instance, you can use it to add a validation to an existing business object (EO).  The second new role, "Oracle Fusion Applications Developer" role, is more versatile and lets you create entirely new artifacts -- pages, business components, task flows etc.  These extensions can then be integrated into existing product functionality by, for example, customizing an existing page (using the Administrator Customization role).  Future parts of this blog post series will show you an example.  You can also read more about it in the Extensibility Guide.

For now, to complete the setup of JDeveloper, we need to create the Default domain for the integrated WebLogic Server (WLS).  In fact, once you select the "Oracle Fusion Applications Developer" role and proceed with the launch of JDeveloper, the IDE will actually prompt you to do just that.  Select "Yes" to enter the Domain Configuration wizard.

A side note: depending on your release, you may at this time see scary looking warnings in the JDeveloper console log about Exceptions "while querying ExalogicOptimizationsEnabled Attribute" and even memory leaks.  These can be ignored (and have been reported as bugs).

The first step of the wizard lets you choose between the standalone and integrated domain configuration. Choose "integrated" -- it's for the WebLogic Server that's part of the JDeveloper installation.

In step 2 you are being asked for the password for the "weblogic" user for WLS.  This admin user account gives you access to the WebLogic console. A password is defaulted.  The masking (*********) makes it impossible to tell that it is the standard WLS default password -- "weblogic1".  For an installation that needs access protection, be sure to change it.

Step 2 of the Domain Creation Wizard

In some releases (screenshot is from Release 4) there is an additional field "Fusion Family Name".  It was removed in future versions and if you have it, you can leave it as defaulted: "Common".

In step 3 of the wizard, enter the database information for your Fusion Applications database.  One of the many schemas, "OWSM MDS", is typically not in the Fusion Applications database, but rather in the identity management (IDM) database.  Override the connect string if necessary.  In general, it's worthwhile double-checking all the usernames and passwords via SQL*Plus or SQL*Developer to make sure they are correct as the domain will otherwise be configured incorrectly.  Unfortunately the current version of the wizard does not offer any built-in validation feature (an enhancement request has been filed).

Step 3 of the Domain Creation Wizard

Step 4 requires that you know the parameters for the LDAP server for your Fusion Applications environment.  The domain will be configured to use that server for authentication and authorization.  If you don't know the values to be entered here, please contact the administrator of your Fusion environment.

Step 4 of the Domain Creation Wizard

Once you finish the wizard, the domain creation and configuration begins.  You can follow the progress in the JDeveloper console pane. It will, depending on the speed of your machine, take a few minutes.  As part of the process, the WebLogic Server will be started; this is necessary to configure the LDAP server as a security provider.

Don't be discouraged by the seemingly endless messages that stream by in the console pane.  If everything works smoothly and as expected, you should in the end have a running WLS server.  If WLS does not start up properly, you need to review the console log for possible errors.


WLS Domain Configuration Failed

As you can see in the above screenshot, the configuration script advises you which log files to review for detailed errors.  They are located in the system directory.  The third part of this blog post series will discuss some of the more common problems we have seen people run into. 


Comments:

Very helpful post. Thank you very much for the walk-through. That completes my Fusion Applications Development environment setup.

Posted by Sree Harsha on March 04, 2013 at 10:42 AM PST #

Thanks Oliver for the post.
I was following your blog to install and setup my Jdev,11.1.1.6.3 for Fusion Apps.

While creating the WLS domain configuration, the process is apparently stuck with the below error message,
"
[11:47:25 AM] ... AdminServer log files still does not exist, sleep another 10 seconds
[11:47:25 AM] ... AdminServer log files still does not exist, sleep another 10 seconds
[11:47:25 AM] ... AdminServer log files still does not exist, sleep another 10 seconds
"

Can you please provide any suggestions?

Posted by guest on March 13, 2013 at 11:23 PM PDT #

Hello guest, thanks for your comment. The question will hopefully be answered in part 3 of the series.

But you probably don't want to wait for that. So, from memory (I am not on the machine right now that has my notes and JDeveloper install):

The likely problem is that WLS did not start up when the domain configuration script tried to start it up. There are a variety of possible causes for it, and you can probably find a clue in the log and err files in

%JDEV_USER_HOME%\system11.1.1.5.X.Y.Z\o.apps.fadev.11.1.1

E.g., if you see this

"...\Java\jre6\lib\ext\QTJava.zip was unexpected at this time."

it's because you have QTJava.zip in the CLASSPATH with a directory that has a space in the name (typically PROGRAM FILES).

Hope this helps, and reply back if it doesn't. Or use our OTN forum at https://forums.oracle.com/forums/forum.jspa?forumID=1424&start=0 if you prefer.

Posted by Oliver Steinmeier on March 13, 2013 at 11:49 PM PDT #

Thanks Oliver for the prompt response.
I do not see that error in any of the OUT or ERR files under the directory, %JDEV_USER_HOME%\system11.1.1.6.39.63.37\o.apps.fadev.11.1.1.

Instead, I see an error, "Error occurred during initialization of VM
Could not reserve enough space for object heap" in the log file, fadev_config_startup_1.out.

Could that be the cause of the problem?

Posted by guest on March 14, 2013 at 12:14 AM PDT #

The error basically means that Java ran out of memory, and so WLS could not start up. How much physical memory do you have on your machine? I would strongly recommend 8gb of RAM. Also, did you use the memory settings parameters for the JVM that are suggested in the article (and install guide)?

Posted by Oliver Steinmeier on March 14, 2013 at 12:18 AM PDT #

I have an 8 GB RAM and I am on Windows 7.
I set the memory settings as instructed as part of launchjdev.cmd

set USER_MEM_ARGS=-Xms256m -Xmx1024m -XX:MaxPermSize=512m -XX:CompileThreshold=8000

Posted by guest on March 14, 2013 at 03:15 AM PDT #

Hi Oliver,

The log issue is fixed by using a 64 bit install of JDK(jdk1.6.0_43). The JDK that was shipped with the Jdeveloper was jdk1.6.0_24.

The configuration continued but eventually exited with status 1.
When I checked the log file, I can see many errors that is apparently related to the database connection.
weblogic.common.ResourceException: Unknown Data Source Activities-CustomPortalDS

I also got a LDAP error in the log,
[06:04:24 PM] ... LDAP configuration: create default authenticator
[06:04:24 PM] log file: C:\Jdev\jdevhome\jdev\system11.1.1.6.39.63.37\o.apps.fadev.11.1.1\fadev_execConfigDomain_defauth.out
[06:04:24 PM] ... wlst LDAP configuration (create default authenticator) failed <<<<<<<<<<

I will touch base with my Admin reg this.

On another note, in the Copy/Paste able version of setting environment variables in this article, one line(set JAVA_HOME=%MW_HOME%\jdk160_24 ) has an extra space in the end, which causes an addition of extra space in the subsequent variable,PATH.
Appreciate if you can remove that, so that the people in future will not commit the same mistake that I did :)

I shall update here the status of my domain configuration. Thanks again for this post.

Posted by guest on March 14, 2013 at 06:29 AM PDT #

Thanks again for your comments. I have removed the extra space at the end of the JAVA_HOME env variable setting.

I am a bit surprised that your problem went away with the 64-bit version. We generally test with the 32-bit version that comes with the JDeveloper install. I'll see if I can find out more about possible root causes. That said, if you plan on using standalone WLS, there are some technology stack components that will require you to use 64-bit JDK anyway.

Please double-check that your database connection and the LDAP connection info is correct. Unfortunately the wizard doesn't check it (I have an enhancement request open for that), so you need to test with SQL*Plus or similar. For LDAP I use JXplorer (free download).

Posted by Oliver Steinmeier on March 14, 2013 at 03:47 PM PDT #

Hi Oliver,

Maybe you can help. I'm trying to setup Jdeveloper 11.1.1.6.2 with our Fusion Environment (11.1.4). However I can't seem to get the Weblogic Domain working.

I keep getting this error message:

Apr 9, 2013 1:05:36 PM oracle.adf.share.ADFContext isHighPerformanceEnvEnabled
WARNING: Exception while querying ExalogicOptimizationsEnabled Attribute
Apr 9, 2013 1:05:41 PM oracle.security.jps.internal.common.util.StrictValidationEventHandler handleEvent
WARNING: Failed to validate the xml content. SchemaLocation: schemaLocation value = 'http://xmlns.oracle.com/oracleas/schema/11/jps-config-11_1.xsd' must have even number of URI's. Location: unavailable.
Apr 9, 2013 1:05:49 PM oracle.adf.share.ADFContext isHighPerformanceEnvEnabled
WARNING: Exception while querying ExalogicOptimizationsEnabled Attribute
Apr 9, 2013 1:06:07 PM oracle.adf.share.ADFContext getCurrent
WARNING: Automatically initializing a DefaultContext for getCurrent.
Caller should ensure that a DefaultContext is proper for this use.
Memory leaks and/or unexpected behaviour may occur if the automatic initialization is performed improperly.
This message may be avoided by performing initADFContext before using getCurrent().
For more information please enable logging for oracle.adf.share.ADFContext at FINEST level.
[01:06:14 PM] The Integrated Weblogic domain has been deleted.
[01:06:15 PM] Creating Integrated Weblogic domain...
[01:07:10 PM] Extending Integrated Weblogic domain...
[01:08:53 PM] Integrated Weblogic domain processing completed successfully.
[01:08:53 PM] Configuring domain with "C:\Oracle\Middleware\jdeveloper\fadev\bin\FADevConfigure.py -i -m C:\Oracle\Middleware -s C:\Projects\system11.1.1.6.39.62.68\"
[01:08:54 PM] Configuring domain for Fusion Applications Development ...
[01:08:54 PM] Traceback (most recent call last):
[01:08:54 PM] ... initialize
[01:08:54 PM] File "C:\Oracle\Middleware\jdeveloper\fadev\bin\FADevConfigure.py", line 848, in <module>
[01:08:54 PM] ... checkMwHome
[01:08:54 PM] checkPropFile()
[01:08:54 PM] ... MW_HOME specified in MW_HOME environment variable: C:\Oracle\Middleware
[01:08:54 PM] File "C:\Oracle\Middleware\jdeveloper\fadev\bin\FADevConfigure.py", line 212, in checkPropFile
[01:08:54 PM] ... Using MW_HOME C:\Oracle\Middleware
[01:08:54 PM] defaultPropFile= os.path.join(os.getenv('HOME'),'fusion_apps_wls.properties')
[01:08:54 PM] ... getSAValues
[01:08:54 PM] File "C:\Python27\lib\ntpath.py", line 96, in join
[01:08:54 PM] ... checkPropFile
[01:08:54 PM] assert len(path) > 0
[01:08:54 PM] TypeError: object of type 'NoneType' has no len()
[01:08:54 PM] Domain configuration exited with status 1.

Maybe you can point me in the right direction?

Thanks,
Martijn Rijpkema

Posted by Martijn Rijpkema on April 09, 2013 at 04:13 AM PDT #

Hello Oliver,

I'm trying to get Jdeveloper up and running on our fusion 11.1.4 environment. I run into the following error when creating the integrated weblogic server. Maybe you can help?

Apr 9, 2013 2:27:08 PM oracle.adf.share.ADFContext isHighPerformanceEnvEnabled
WARNING: Exception while querying ExalogicOptimizationsEnabled Attribute
Apr 9, 2013 2:27:21 PM oracle.security.jps.internal.common.util.StrictValidationEventHandler handleEvent
WARNING: Failed to validate the xml content. SchemaLocation: schemaLocation value = 'http://xmlns.oracle.com/oracleas/schema/11/jps-config-11_1.xsd' must have even number of URI's. Location: unavailable.
Apr 9, 2013 2:28:04 PM oracle.adf.share.ADFContext isHighPerformanceEnvEnabled
WARNING: Exception while querying ExalogicOptimizationsEnabled Attribute
[Starting Server Instance IntegratedWebLogicServer]
Apr 9, 2013 2:43:37 PM oracle.adf.share.ADFContext getCurrent
WARNING: Automatically initializing a DefaultContext for getCurrent.
Caller should ensure that a DefaultContext is proper for this use.
Memory leaks and/or unexpected behaviour may occur if the automatic initialization is performed improperly.
This message may be avoided by performing initADFContext before using getCurrent().
For more information please enable logging for oracle.adf.share.ADFContext at FINEST level.
#### Server Instance IntegratedWebLogicServer could not be started: Error starting Server Instance.
[02:43:47 PM] The Integrated Weblogic domain has been deleted.
[02:43:47 PM] Creating Integrated Weblogic domain...
[02:50:29 PM] Extending Integrated Weblogic domain...
[02:52:11 PM] Integrated Weblogic domain processing completed successfully.
[02:52:11 PM] Configuring domain with "C:\Oracle\Middleware\jdeveloper\fadev\bin\FADevConfigure.py -i -m C:\Oracle\Middleware -s C:\Projects\system11.1.1.6.39.62.68\"
[02:52:13 PM] Configuring domain for Fusion Applications Development ...
[02:52:13 PM] ... initialize
[02:52:13 PM] ... checkMwHome
[02:52:13 PM] ... MW_HOME specified in MW_HOME environment variable: C:\Oracle\Middleware
[02:52:13 PM] ... Using MW_HOME C:\Oracle\Middleware
[02:52:13 PM] ... getSAValues
[02:52:13 PM] ... checkPropFile
[02:52:13 PM] Traceback (most recent call last):
[02:52:13 PM] File "C:\Oracle\Middleware\jdeveloper\fadev\bin\FADevConfigure.py", line 848, in <module>
[02:52:13 PM] checkPropFile()
[02:52:13 PM] File "C:\Oracle\Middleware\jdeveloper\fadev\bin\FADevConfigure.py", line 212, in checkPropFile
[02:52:13 PM] defaultPropFile= os.path.join(os.getenv('HOME'),'fusion_apps_wls.properties')
[02:52:13 PM] File "C:\Python27\lib\ntpath.py", line 96, in join
[02:52:13 PM] assert len(path) > 0
[02:52:13 PM] TypeError: object of type 'NoneType' has no len()
[02:52:13 PM] Domain configuration exited with status 1.

Thanks!
Martijn

Posted by guest on April 09, 2013 at 05:53 AM PDT #

Hi Martijn, thanks for your question.

Actually, that particular error is what's currently holding me back from publishing part 3 (Troubleshooting) of this blog post series. I have never experienced this problem myself, and neither has anyone at Oracle that I have talked to, but I know it's been reported before (tracked as bug 16555695) and I was just yesterday looking into it. The current thinking is that it might be caused by a faulty Python install.

Posted by Oliver Steinmeier on April 09, 2013 at 09:29 AM PDT #

I was finally able to find a machine with reproducible test case. The problem is indeed caused by a problem with the Python install and can be fixed by editing the Windows registry entries that control how python.exe is called by .py files. The problem here is that parameters passed to the FADevConfigure.py script are not received and so the code goes down the wrong path (standalone WLS instead of integrated, as supposed to be used here based on -i parameter). There are several sources on the internet explaining how to fix the registry. The exact registry keys seem to depend on the Python version and perhaps the Windows version. See http://eli.thegreenplace.net/2010/12/14/problem-passing-arguments-to-python-scripts-on-windows/ for example.

Posted by Oliver Steinmeier on April 12, 2013 at 02:52 PM PDT #

Hi Oliver, I always get stuck at either "Creating Integrated Weblogic domain" or "Extending Integrated Weblogic domain", when I look into the log file in o.j2ee.adrs folder, I can see it's stuck at "wlst > Initializing WebLogic Scripting Tool (WLST) ...". I tried many combinations of JDK and JDeveloper version, it seems like if I use a 32-bit JDK, either it's downloaded from Oracle or the shipped one, and with JDeveloper 11.1.1.6.2, I can reach "Extending Integrated Weblogic domain", otherwise I will be stuck at "Creating Integrated Weblogic domain". There are two times that I passed these two steps, but when I want to retry, I still get stucked. It's like lottery, and I just can't win. Do you have any ideas about my problem?

Posted by guest on May 13, 2013 at 10:40 PM PDT #

Next week's blog post (part 3 of this series) will be focused on troubleshooting the domain configuration. But I have never seen this particular problem.

A couple of questions/comments:

- When you say it get's stuck, how long do you wait for it to complete that step?

- What operating system are you using, and what are your hardware specs (memory, CPU primarily)

- What version of Python?

- While you should be using a 64-bit JDK (per recent blog posts), the domain configuration should work fine with the JDK that's bundled with the JDeveloper download. So I wouldn't worry about switching around JDKs at this point.

- what are the PATH and CLASSPATH values displayed right before "wlst > Initializing WebLogic Scripting Tool (WLST) ..." ?

Posted by Oliver Steinmeier on May 14, 2013 at 09:56 AM PDT #

1. I wait for one whole night once, I left my laptop open and went to bed, when I wake up it's still there.
2. I'm using Win 7 Enterprise 64bit, 8GB memory, i5 M520@2.40GHz.
3. I'm using Python 2.7.4.
4. Both 32bit and 64 bit JDK won't help.
5.
Log File: C:\Develop\Oracle\JDevUserHome\system11.1.1.6.39.63.37\o.j2ee.adrs\CreateDefaultDomain.log
Label: JDEVADF_11.1.1.6.3MLR_GENERIC_120709.1648.6337
Product Home: C:\Develop\Oracle\Fusion\jdeveloper\jdev\
Domain: C:\Develop\Oracle\JDevUserHome\system11.1.1.6.39.63.37\DefaultDomain

"C:\Develop\Oracle\Fusion\oracle_common\common\bin\wlst.cmd" "C:\Develop\Oracle\JDevUserHome\system11.1.1.6.39.63.37\o.j2ee.adrs\CreateDefaultDomain.py"
Process started
wlst >
wlst > CLASSPATH=C:\Develop\Oracle\Fusion\patch_wls1035\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Develop\Oracle\Fusion\patch_jdev1111\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Develop\Java\JDK16~1.0_4\lib\tools.jar;C:\Develop\Oracle\Fusion\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\Develop\Oracle\Fusion\WLSERV~1.3\server\lib\weblogic.jar;C:\Develop\Oracle\Fusion\modules\features\weblogic.server.modules_10.3.5.0.jar;C:\Develop\Oracle\Fusion\WLSERV~1.3\server\lib\webservices.jar;C:\Develop\Oracle\Fusion\modules\ORGAPA~1.1/lib/ant-all.jar;C:\Develop\Oracle\Fusion\modules\NETSFA~1.0_1/lib/ant-contrib.jar;;C:\Develop\Oracle\Fusion\ORACLE~1/modules/oracle.jrf_11.1.1/jrf-wlstman.jar;C:\Develop\Oracle\Fusion\ORACLE~1\common\wlst\lib\ADF-SH~1.JAR;C:\Develop\Oracle\Fusion\ORACLE~1\common\wlst\lib\ADFSCR~1.JAR;C:\Develop\Oracle\Fusion\ORACLE~1\common\wlst\lib\APPLCO~1.JAR;C:\Develop\Oracle\Fusion\ORACLE~1\common\wlst\lib\mdswlst.jar;C:\Develop\Oracle\Fusion\ORACLE~1\common\wlst\RESOUR~1\AUDITW~1.JAR;C:\Develop\Oracle\Fusion\ORACLE~1\common\wlst\RESOUR~1\IGFWLS~1.JAR;C:\Develop\Oracle\Fusion\ORACLE~1\common\wlst\RESOUR~1\jps-wlst.jar;C:\Develop\Oracle\Fusion\ORACLE~1\common\wlst\RESOUR~1\jrf-wlst.jar;C:\Develop\Oracle\Fusion\ORACLE~1\common\wlst\RESOUR~1\OAMAP_~1.JAR;C:\Develop\Oracle\Fusion\ORACLE~1\common\wlst\RESOUR~1\OAMAUT~1.JAR;C:\Develop\Oracle\Fusion\ORACLE~1\common\wlst\RESOUR~1\ossoiap.jar;C:\Develop\Oracle\Fusion\ORACLE~1\common\wlst\RESOUR~1\OSSOIA~1.JAR;C:\Develop\Oracle\Fusion\ORACLE~1\common\wlst\RESOUR~1\OVDWLS~1.JAR;C:\Develop\Oracle\Fusion\ORACLE~1\common\wlst\RESOUR~1\SSLCON~1.JAR;C:\Develop\Oracle\Fusion\ORACLE~1\common\wlst\RESOUR~1\wsm-wlst.jar
wlst >
wlst > PATH=C:\Develop\Oracle\Fusion\patch_wls1035\profiles\default\native;C:\Develop\Oracle\Fusion\patch_jdev1111\profiles\default\native;C:\Develop\Oracle\Fusion\WLSERV~1.3\server\native\win\32;C:\Develop\Oracle\Fusion\WLSERV~1.3\server\bin;C:\Develop\Oracle\Fusion\modules\ORGAPA~1.1\bin;C:\Develop\Java\JDK16~1.0_4\jre\bin;C:\Develop\Java\JDK16~1.0_4\bin;;C:\Develop\Oracle\Fusion\WLSERV~1.3\server\native\win\32\oci920_8
wlst >
wlst > Your environment has been set.
wlst >
wlst > CLASSPATH=C:\Develop\Oracle\Fusion\patch_wls1035\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Develop\Oracle\Fusion\patch_jdev1111\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Develop\Java\JDK16~1.0_4\lib\tools.jar;C:\Develop\Oracle\Fusion\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\Develop\Oracle\Fusion\WLSERV~1.3\server\lib\weblogic.jar;C:\Develop\Oracle\Fusion\modules\features\weblogic.server.modules_10.3.5.0.jar;C:\Develop\Oracle\Fusion\WLSERV~1.3\server\lib\webservices.jar;C:\Develop\Oracle\Fusion\modules\ORGAPA~1.1/lib/ant-all.jar;C:\Develop\Oracle\Fusion\modules\NETSFA~1.0_1/lib/ant-contrib.jar;;C:\Develop\Oracle\Fusion\ORACLE~1/modules/oracle.jrf_11.1.1/jrf-wlstman.jar;C:\Develop\Oracle\Fusion\ORACLE~1\common\wlst\lib\ADF-SH~1.JAR;C:\Develop\Oracle\Fusion\ORACLE~1\common\wlst\lib\ADFSCR~1.JAR;C:\Develop\Oracle\Fusion\ORACLE~1\common\wlst\lib\APPLCO~1.JAR;C:\Develop\Oracle\Fusion\ORACLE~1\common\wlst\lib\mdswlst.jar;C:\Develop\Oracle\Fusion\ORACLE~1\common\wlst\RESOUR~1\AUDITW~1.JAR;C:\Develop\Oracle\Fusion\ORACLE~1\common\wlst\RESOUR~1\IGFWLS~1.JAR;C:\Develop\Oracle\Fusion\ORACLE~1\common\wlst\RESOUR~1\jps-wlst.jar;C:\Develop\Oracle\Fusion\ORACLE~1\common\wlst\RESOUR~1\jrf-wlst.jar;C:\Develop\Oracle\Fusion\ORACLE~1\common\wlst\RESOUR~1\OAMAP_~1.JAR;C:\Develop\Oracle\Fusion\ORACLE~1\common\wlst\RESOUR~1\OAMAUT~1.JAR;C:\Develop\Oracle\Fusion\ORACLE~1\common\wlst\RESOUR~1\ossoiap.jar;C:\Develop\Oracle\Fusion\ORACLE~1\common\wlst\RESOUR~1\OSSOIA~1.JAR;C:\Develop\Oracle\Fusion\ORACLE~1\common\wlst\RESOUR~1\OVDWLS~1.JAR;C:\Develop\Oracle\Fusion\ORACLE~1\common\wlst\RESOUR~1\SSLCON~1.JAR;C:\Develop\Oracle\Fusion\ORACLE~1\common\wlst\RESOUR~1\wsm-wlst.jar;C:\Develop\Oracle\Fusion\utils\config\10.3\config-launch.jar;C:\Develop\Oracle\Fusion\WLSERV~1.3\common\derby\lib\derbynet.jar;C:\Develop\Oracle\Fusion\WLSERV~1.3\common\derby\lib\derbyclient.jar;C:\Develop\Oracle\Fusion\WLSERV~1.3\common\derby\lib\derbytools.jar;;
wlst >
wlst > Initializing WebLogic Scripting Tool (WLST) ...
wlst >

Posted by Orthon on May 14, 2013 at 11:50 PM PDT #

Can you confirm:
* Are you able to invoke the wlst outside JDeveloper ? If you start the wlst.cmd directly does it work as expected?
* What happens if you execute the script from command prompt ?
* If this works from command prompt can you add debug messages to the py script to identify whether the processing reaches the script when executed from JDeveloper and if so which line it fails / gets stuck with ?

Posted by guest on May 15, 2013 at 08:23 AM PDT #

1. I can invoke the wlst by enter in command line: "C:\Develop\Oracle\Fusion\oracle_common\common\bin\wlst.cmd" "C:\Develop\Oracle\JDevUserHome\system11.1.1.6.39.63.37\o.j2ee.adrs\CreateDefaultDomain.py".
2. Here is the output in command line, I igonre the classpath setting part:
Initializing WebLogic Scripting Tool (WLST) ...

Welcome to WebLogic Server Administration Scripting Shell

Type help() for help on available commands

Error: ADRS_DOMAIN_PASSWORD environment variable not set.
3. How to enable debug in CreateDefaultDomain.py or CreateDefaultDomain.py?

Posted by Orthon on May 15, 2013 at 07:54 PM PDT #

Unfortunately I think the ADRS_DOMAIN_PASSWORD error is caused by the fact that its run outside JDeveloper; i.e. the JDeveloper sets the value prior to calling the script so I don't think this is related to the original issue. The original issue is peculiar and since unable to reproduce difficult to debug. I don't think the processing ever reaches the py script given that the log does not contain "Creating Default Domain" which is printed immediately after the check for ADRS_DOMAIN_PASSWORD and if the processing failed for the password it would print another message which is not present in the log either.
The only thing I can think of is that the .py scripts are associated with some text editor or some other tool causing the processing to "send" the execution to wrong place. Can you check:

* Which program (if any) do you have the ".py" scripts associated with ? If you navigate in the Windows Explorer to the directory containing the "CreateDefaultDomain.py" is the file type "Python File" ? If the association is wrong you can fix it by running run registry editor (Press "<windows button>+r", enter "regedit" and click "OK"), navigate to "Computer->HKEY_CLASSES_ROOT->.py" remove the "value" for the "default" key.
* If association is correct try creating a simple test .py script in the same directory containing:
/Code Start - add the line after this to script/
import time
print("Extend Default Domain")
time.sleep(10) # delays for 10 seconds
exit()
/Code End - add the line before this to script/

If you double click it does it open a command prompt or some other tool. If the association is incorrectly set to e.g. text editor the JDeveloper processing would instead of executing the script with Python open the file in the text editor. In such scenario JDeveloper would be left waiting for processing to end, which would not happen since the processing was never started so based on the log the process would seem to be "stuck".
* To debug you can try adding debugging messages to the "CreateDefaultDomain.py" script using your preferred text editor to see whether the script is reached e.g. as the first line of execution add something like:
print("DEBUG: Start of script")
* To debug you can also try hard coding the ADRS_DOMAIN_PASSWORD in the "CreateDefaultDomain.py" script by adding following before the variable is validated:
os.putenv('ADRS_DOMAIN_PASSWORD', 'welcome1')

Posted by Jani Rautiainen on May 16, 2013 at 12:29 AM PDT #

Hi,
In my case I am trying to setup the domain but my FA instance is running over IDM so not sure what to put up in the "Step 3 of the Domain Creation Wizard".

Please provide any inputs here.
Thanks
Vips

Posted by guest on July 23, 2013 at 12:08 PM PDT #

Hello Vips, thanks for your comment. You'd need to get the correct values from whoever set up your IDM. There's no way I can suggest these values. Assuming you know the server credentials and lack the values for user and group base DNs, a tool like JXplorer might be helpful in finding those.

Posted by Oliver Steinmeier on July 23, 2013 at 02:11 PM PDT #

Hi Oliver,
Thanks for the quick response, I have worked over ldap so know where these entries should be weblogic, for a ldap server authentication. But my bad IDM is still a big ghost for me, so one question is the same place I get entries for the IDM also like ldap. I am asking to get console access from my the FA admin team, will this work or I need access to EM also to see this information.

My bad admin team can provide me access but they are not sure to give all these details, poor guys also learning on FA like me :-).

Thanks
Vips

Posted by vipin kumar on July 23, 2013 at 02:34 PM PDT #

Hi Vips, if you have access to the Weblogic Console of the Fusion Apps WLS servers, you can find the OID connection info there, under Security Realms.

Posted by Oliver Steinmeier on July 23, 2013 at 05:51 PM PDT #

Post a Comment:
  • HTML Syntax: NOT allowed
About

Follow us on twitter Fusion Applications Extensibility, Customizations and Integration forum Fusion Applications Dev Relations YouTube Channel
This blog offers news, tips and information for developers building extensions, customizations and integrations for Oracle Fusion Applications.

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
4
5
6
8
11
12
13
15
16
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today