2 WLS Instances :relationship in JNDI

I have 2 instances of WLS. One is my own instance on NT and the other is an instance
running on a unix server. Can the NT instance get a initial context for the unix
instance and
lookup an ejb in the unix instance's jndi tree ? Do I need to do anything special
to enable this.
thanks

"DK" <[email protected]> wrote in message
news:[email protected]..
>
I have 2 instances of WLS. One is my own instance on NT and the other isan instance
running on a unix server. Can the NT instance get a initial context forthe unix
instance and
lookup an ejb in the unix instance's jndi tree ? Do I need to do anythingspecial
to enable this.
thanks
Yes, you can have the WLS instance on NT access the jndi tree on the unix
server and access EJB's on teh unix server. You do so by specifying the
provider_url of the target server when creating your InitialContext.
EG (from the weblogic docs):
Hashtable env = new Hashtable(5);
env.put(Context.INITIAL_CONTEXT_FACTORY,
"weblogic.jndi.WLInitialContextFactory");
env.put(Context.PROVIDER_URL,
"t3://weblogicServer:7001");
Context ctx = new InitialContext(env);
Brett

Similar Messages

Managing Internet facing WLS instances

Does the new Administration server replace the need for the administration port on WLS
(the use of the port is not mentioned in the documentation).
Would a standard internet deployment of WLS include running an administrative WLS
(with no application code) running on a separate IP address from a managed application WLS instance?

Does the new Administration server replace the need for the administration port on WLS
(the use of the port is not mentioned in the documentation).
Would a standard internet deployment of WLS include running an administrative WLS
(with no application code) running on a separate IP address from a managed application WLS instance?

WLS http access logs not written to when starting WLS instance using nodemanager

When starting managed WLS instances using node manager the HTTP access logs are
not written to (the WLS log in the same directory is written to). All other functionality
of the WLS instances seem to operate just fine when started using node manager.
When we start the same managed WLS instances using a start-up script the HTTP
access logs are written to.
===
How can we get HTTP access logs to be written to when starting a WLS instance
using node manager?

I think I know the answer to this one!
I got bitten by the same bug (at least I think it is a bug). Check the location
specified for the HTTP-access log for your server instance. It is probably a relative
location, right?
According to the docs, relative paths should start from the Root Directory (see
your Remote Start config), but it seems like the BEA-programmers forgot to retrieve
the Root Directory and instead blindly writes to the process' current working
directory (CWD).
And when started by the Node Managet, the CWD = WL_HOME/common/nodemanager.
If you are as paronoid as I am (and you should be too), that directory should
not be writeable by anyone. Because my BEA installation was owned by 'bin', and
the processes run by 'beawls', I got an error message in my NM-logs pointing to
the problem. In your case, you are probably running NM as a user that has write-access
to your NM-home, and all your missing HTTP-access logs are deep, down there.
Jan Bruun Andersen

(261680070) Q WWO-13 How can I link workshop to a different WLS instance?

Q<WWO-13> How can I link workshop to a different WLS instance?
A<WWO-13> Use the Workshop menus. Select the Tools menu, then choose Preferences.
Select the Paths tab and then specify the domain and server that you wish to connect
to.

Additional Information supplied by John Methot:
Unfortunately, that's not all there is to it. You also have to make sure
both the Workshop IDE and the WLS instance are looking at the same project
filesystem. This means you have to share the filesystem from the WLS
machine (typically) and mount it (or, in windows, map it) on the IDE
machine. Specifically, you want to share/mount/map the directory that is
the parent of the domain directory (so, be default,
c:\bea\weblogic700\samples). Then, in the preferences dialog, you have set
the "config directory path" that that mount point and then select the domain
("workshop"). Now you're set.
If you don't do this, things might sort of seem to work but won't. You'll
be editing happily away on the IDE machine, but running unmodified files on
the WLS machine (the real files).
Bottom line: there is no file transfer feature between the two machine in a
remote configuration. Both machines have to see the same file system.
"Adam FitzGerald" <[email protected]> wrote:
>
Q<WWO-13> How can I link workshop to a different WLS instance?
A<WWO-13> Use the Workshop menus. Select the Tools menu, then choose Preferences.
Select the Paths tab and then specify the domain and server that you wish
to connect
to.

WLS Instances don`t refresh when getting New content

          Hi there,
          We´re using wls6.0sp2 for testing purposes and we have problems when we're loading
          new HTML and JSP content in a already deployed web directory, i.e. a client is
          only able to access the old stuff.
          The Clients are communicating via an Apache PlugIn with the WLS Instances (we`ve
          got a small cluster with 2 instances). Is it possible that either the apache webserver
          or the WLS Admin Server have cached the old content ?
          Is hot Deploymewnt of new content not possible on WLS 6.0 ?
          Thanks for any help.
          sincerely,
          Marcus Kreher


WebAppComponents can be hot deployed, i.e. refreshed without having to
          redeploy the whole application. This will work for any static content (html,
          gif, jpeg, etc.) as well as jsp files.
          In 6.1, use the weblogic.deploy command to refresh. In 6.0, there is a
          separate command-line tool
          (weblogic.management.tools.WebAppComponentRefreshTool) which is in a rolling
          patch for Service Pack 2.
          Please contact WebLogic Support to request the Rolling Patch.
          Regards,
          -- Ian
          "Marcus Kreher" <[email protected]> wrote in message
          news:[email protected]..
          >
          > Hi there,
          >
          > We´re using wls6.0sp2 for testing purposes and we have problems when we're
          loading
          > new HTML and JSP content in a already deployed web directory, i.e. a
          client is
          > only able to access the old stuff.
          > The Clients are communicating via an Apache PlugIn with the WLS Instances
          (we`ve
          > got a small cluster with 2 instances). Is it possible that either the
          apache webserver
          > or the WLS Admin Server have cached the old content ?
          > Is hot Deploymewnt of new content not possible on WLS 6.0 ?
          >
          > Thanks for any help.
          >
          > sincerely,
          > Marcus Kreher
          >

Does WLS 7.0 support JNDI Events ?

I am wondering if WLS 7.0 supports JNDI events. If so, how do i access the EventContext from the JNDI tree ? do i need to configure somethign to enable it ? Please help !

Is Weblogic 7.0 supported on Windows XP ? Is it reliable, etc. ? I was          planning to use it on a laptop running windows XP.
          If you're just developing, then I think you'll be fine.
          Peace,
          Cameron Purdy
          Tangosol, Inc.
          http://www.tangosol.com/coherence.jsp
          Tangosol Coherence: Clustered Replicated Cache for Weblogic
          "Amit Pradhan" <[email protected]> wrote in message
          news:3d93920d$[email protected]..
          >

Accessing two different wls instances in Apache

Hi!
Does anyone know if it is possible to connect to two different instances of wls
5.1 sp 6 (same IP, different ports) from an apache front-end under the same <VirtualHost>-instance,
using mod_wl_ssl.so?

Thanks for your reply.
It's not the CuCo being initial but my attribute and the collection wrapper of the value node has only one entry, the empty one which is added in the INIT-method of the context node. So it feels like a second instance of my CuCo as inside the other view I have my collection, attribute etc.
This is my coding to get the CuCo:
DATA: lr_cucosearch TYPE REF TO zl_iccmp_bp_cucosearch_impl.
lr_cucosearch ?= get_custom_controller( 'ICCMP_BP_SEARCH/CuCoSearch' ).
This coding I use in both views. This is wrong? I debugged and it looked like it would search for an instance and then return it instead of creating a second one.
Am I mistaken?
Thanks.

WLS/OSB DB Adapter - JNDI lookup failed

Hello all.
I've got a DB adapter service set up in a clustered environment, and it all works (and I've built proxy services, transformations etc around it), but I've just noticed that the log shows a warning regarding the JNDI lookup of the ConnectionFactory, as below.
It's working, and the error is only a warning, but could this cause problems going forward, particularly with regards performance?
Given that the ConnectionFactory name is 'com.whatever.myServiceDB', and the Endpoint URI of the service is 'jca://com.whatever.myServiceDB', what could be wrong? Has anyone seen/fixed this before? It's almost like the managed servers don't know about the JNDI name...but the DbAdapter deployent has 'All servers in the cluster' selected in its 'Targets' tab, so I'm not sure.
Any pointers would be appreciated, I'm probably missing something obvious.
Cheers.
####<Apr 15, 2010 10:53:10 AM BST> <Warning> <JCA_FRAMEWORK_AND_ADAPTER> <servername> <managed3_domainname> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1271325190453> <BEA-000000> <servicebus:/WSDL/MyProject/MyService [ MyService_ptt::merge(MessagesCollection) ] - JNDI lookup of 'com.whatever.myServiceDB' failed due to: String index out of range: -1>

Thanks again.
In case anyone runs into a similar problem and is wondering: a bit of mucking about reveals that the WLS ConnectionFactory config is fine with dots or slashes, and it seems to treat both the same when creating the JNDI tree.
However, the WSDL (that you probably created in JDeveloper) has to have slashes for doing its lookup. So, for example, always use slashes rather than dots when setting your DB Adapter JNDI name in JDeveloper. I guess this is a bit different from usual class/package naming standards, so may catch someone else out too.
Cheers.

App. Module and Instances, relationship, need help.

Hi,
Let me explain my situation. I created two instances, one from "APasesDati" VO and another from "LVAIKolekcijaDati" VO. Each of these instances have subinstances. So. One day needed to connect these instances with relationship, one to one, so that I can navigate between these instances in my jspx pages. For example, I see one instances third record, and when I navigate to another page, I need to see second instances third record. So I created ViewLink "APasesDati via LVAIKolekcijaDati_APasesDati". My task You, can see in the following picture, it is better to illustrate my situation, pleas see:
http://my.jetscreenshot.com/2677/20110407-lkvs-94kb
If something is not clear, please let me know and I will explain You.
Hope for Your help. Best regards, Debuger!
Edited by: Debuger on Apr 7, 2011 10:22 PM
Edited by: Debuger on Apr 8, 2011 3:30 AM

In principle, there are only one way to do my task!? I can add LVAIKolekcijaDati via APasesDati as instance and move APasesDati child elements under that. Am I right? And if my jspx page is created from APasesDati instance and now I want to use my new - LVAIKolekcijaDati via APasesDati then I need to reecreate my jspx page from begining, or I can change something in my jspx page or somewhere else something that way I do not to recreate my jspx page and use LVAIKolekcijaDati via APasesDati in my page?
Best regards, Debuger!

How can I connect to multiple WLS instances from a single Apache virtual host

Configuration : WebLogic 5.1 SP8 & Apache
I need to be able to have a configuration that looks something like this.
www.company.com/x -> WL cluster01
www.company.com/y -> WL cluster02
In all the examples that I have been able to find they alway defines the the WL
connection for the entire virtual host, but I need to be able to do it on a location
basis is that possible?
Thanks
Jens Schutt

httpd.conf:
<VirtualHost 172.17.9.24:443>
DocumentRoot "/www/X"
ServerName qawebivesta.qa.livecapital.com
ErrorLog /usr/local/apache/logs/qaweb1.error_log
TransferLog /usr/local/apache/logs/qaweb1.access_log
SSLEngine on
SSLCipherSuite
ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL
SSLCertificateFile /usr/local/apache/conf/ssl.crt/server.crt
SSLCertificateKeyFile /usr/local/apache/conf/ssl.key/server.key
<Files ~ "\.(cgi|shtml|phtml|php3?)$">
SSLOptions +StdEnvVars
</Files>
<Directory "/usr/local/apache/cgi-bin">
SSLOptions +StdEnvVars
</Directory>
SetEnvIf User-Agent ".*MSIE.*" \
nokeepalive ssl-unclean-shutdown \
downgrade-1.0 force-response-1.0
Debug ON
DebugConfigInfo ON
<Location /ivesta/>
SetHandler weblogic-handler
WebLogicHost qawlgc1
WebLogicPort 7001
</Location>
<Location /TMPPhase2>
SetHandler weblogic-handler
WebLogicHost qawlgc1
WebLogicPort 11001
</Location>
</VirtualHost>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/TMPPhase2 works fine, but when I try to access /ivesta I get a 404 from WebLogic
"https://qawebtmp.qa.livecapital.com/ivesta/index.jsp?__WebLogicBridgeConfig
Weblogic Apache Bridge Configuration parameters:
     WebLogic Cluster List:
          General Server List:
               Host: 'qawlgc1' Port: 11001
          DefaultFileName: ''
          PathTrim: ''
          PathPrepend: ''
          ConnectTimeoutSecs: '10'
          ConnectRetrySecs: '2'
          HungServerRecoverSecs: '300'
          MaxPostSize: '-1'
          DynamicServerList: ON
          StatPath: false
          CookieName: WebLogicSession
          Idempotent: ON
          FileCaching: ON
          DisableCookie2Server: OFF
          QueryFromRequest: OFF
          Build date/time: Jun 25 2001 15:09:34
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This should have been connecting to my 7001 instance not the 11001.
Thanks
Jens
"Eric Gross" <[email protected]> wrote:
What do you mean the wrong port? Post the complete output from
WebLogicBridgeConfig as well as the URL you used.
Also, paste the weblogic relative portions from your httpd.conf
Thanks,
Eric
"jens" <[email protected]> wrote in message
news:[email protected]...
I also used ?__WebLogicBridgeConfig to verify that it did pick up thewrong port.
Here is my build date for mod_wl.so in SP10
Build date/time: Jun 25 2001 15:09:34
Thanks
Jens
"Eric Gross" <[email protected]> wrote:
Make sure you are using the latest plugin. As well, add parameter:
DebugConfigInfo=ON and make a request with a query paramater of
?__WebLogicBridgeConfig and you should then see the build date/time.
We can
then see if you are indeed using the latest plugin.
It is not a possibility to get the source.
Regards,
Eric
"jens" <[email protected]> wrote in message
news:[email protected]...
And the solution where you put the WebLogic parm under location
the
last
location
over rule the previous.
I have also tried to upgrade my plug-in from SP8 to SP10 but that
didn't
make
any difference either.
Is it possible to get the source code for the plug-in, I'm afraid
that
it
don't
follow put's all it's parm's a the vhost level no matter where in
the
conf
file
they are placed.
HELP
Jens
"Eric Gross" <[email protected]> wrote:
Yu is correct.
Here is another way to do it as well:
MatchExpression /x
WebLogicCluster=server1:port,server2:port|PathTrim=/x
MatchExpression /yWebLogicCluster=server3:port,server4:port|PathTrim=/y
The general syntax for this would be:
MatchExpression exp name=value|name=value
Where exp=Mime type(*.jsp) or exp=/x(path)
The next argument in the list is a pipe(|) delimited list ofname=value
pairs (ie: WebLogicHost, WebLogicPort, WebLogicCluster, PathTrim,
PathPrepend, etc..).
Hope this helps.
Regards,
Eric
"Yu Tian" <[email protected]> wrote in message
news:[email protected]...
Hi Jens,
I think you can proxy by ppath.
<Location /x>
SetHandler weblogic-handler
WebLogicCluster cluster1
</Location>
<Location /y>
SetHandler weblogic-handler
WebLogicCluster cluster2
</Location>
thanks
Yu
"Jens" <[email protected]> wrote in message
news:[email protected]...
Configuration : WebLogic 5.1 SP8 & Apache
I need to be able to have a configuration that looks something
like
this.
www.company.com/x -> WL cluster01
www.company.com/y -> WL cluster02
In all the examples that I have been able to find they alway
defines
the
the WL
connection for the entire virtual host, but I need to be able
to
do it
on
a location
basis is that possible?
Thanks
Jens Schutt

Installing another WLS 6.0 instance in same root /bea directory

I have a running WLS 6x instance in /bea/wls6***. I want to put another
instance in /bea directory as a totally separate instance (/bea/wls6trn
e.g.) Is this a valid way to do this or do I need to go ahead and install to
another separate filesystem.
daryl

Daryl,
What is it you are trying to accomplish? You do not need to install the software
multiple times to have multiple instances running on the same machine. In fact, I
always recommend to our customers that they never use the BEA-HOME directory
structure to store ther application-specific data. If all you want to do is create
two separate domains on the same machine, do the following:
1.) Install the WebLogic Server 6.1 (or 6.0) software (it will go under
$BEA_HOME/wlserver6.1).
2.) Create some other directory somewhere outside of the $BEA_HOME directory
structure (e.g., /usr/myApp1).
3.) Copy the $BEA_HOME/wlserver6.1/config directory to /usr/myApp1 (you can delete
the examples and PetStore directories under /usr/myApp1/config directory).
4.) Edit the /usr/myApp1/config/mydomain/startWebLogic.sh script to reflect the
fact that the WebLogic software is installed elsewhere.
5.) Repeat steps 2 through 4 as many times as you want to create as many instances
as you want...
Hope this helps,
Robert
BEA Weblogic Support wrote:
Hi Daryl
That is a weblogic 6.x design constraint. Weblogic 6.x keeps the history of
versions under BEA-HOME, in the registry.xml file. So, if you have already
installed same weblogic version with same service pack level then the installer
won't allow you to install it second time. You should have different bea-homes.
I hope this clarifies your query.
Thanks & Regards
BEA Customer Support
Daryl Davis wrote:
I believe you. But I do have a question. If two different versions work,
why won't two of the same?
daryl
"BEA Weblogic Support" <[email protected]> wrote in message
news:[email protected]...
Hi Daryl
Greetings...!
How are you doing?.
You can have different versions under same BEA-HOME. For example
BEA-HOME is /bea
----/wlserver6.1(weblogic6.1 build)
----/wlserver6.1sp1 (weblogic 6.1 with sp1build)
----/wlserver6.0sp2 (weblogic6.0 with sp2 build)
But you can't have more than one wls instance of same version under one
BEA-HOME. You have to choose different BEA-HOME, /beatrans
Thanks & Regards
BEA Customer Suppot
Daryl Davis wrote:
I have a running WLS 6x instance in /bea/wls6***. I want to put
another
instance in /bea directory as a totally separate instance (/bea/wls6trn
e.g.) Is this a valid way to do this or do I need to go ahead andinstall to
another separate filesystem.
daryl

Configure WLS for BI Publisher 11g

Hello all.
We have same problem with configure WLS for BI publisher on Lunix x64. We do this:
1. We have WLS instance with ADF apps on server.
2. We need install BI Publisher on that server too
3. We install OBIEE 11 in "Software only" mode
4. We start config.sh in silent mode (we have only ssh access to server)
5. in our HOSTS file first is record like this 10.64.125.11 ccx_weblogic.spb.ru
6. And we have error on create domain phase:
Error while starting the domain.
Cause:
Starting the Admin_Server timed out.
Action:
See logs for more details.
     at oracle.as.provisioning.util.ConfigException.createConfigException(ConfigException.java:123)
     at oracle.as.provisioning.weblogic.ASDomain.startDomain(ASDomain.java:3149)
     at oracle.as.provisioning.weblogic.ASDomain.startDomain(ASDomain.java:3039)
     at oracle.as.provisioning.engine.WorkFlowExecutor._startAdminServer(WorkFlowExecutor.java:1645)
     at oracle.as.provisioning.engine.WorkFlowExecutor._createDomain(WorkFlowExecutor.java:635)
     at oracle.as.provisioning.engine.WorkFlowExecutor.executeWLSWorkFlow(WorkFlowExecutor.java:391)
     at oracle.as.provisioning.engine.Config.executeConfigWorkflow_WLS(Config.java:866)
     at oracle.as.install.bi.biconfig.standard.StandardWorkFlowExecutor.executeHelper(StandardWorkFlowExecutor.java:31)
     at oracle.as.install.bi.biconfig.standard.DomainProvisioningTask.doExecute(DomainProvisioningTask.java:48)
     at oracle.as.install.bi.biconfig.standard.AbstractProvisioningTask.execute(AbstractProvisioningTask.java:70)
     at oracle.as.install.bi.biconfig.standard.StandardProvisionTaskList.execute(StandardProvisionTaskList.java:61)
     at oracle.as.install.bi.biconfig.BIConfigMain.doExecute(BIConfigMain.java:112)
     at oracle.as.install.engine.modules.configuration.client.ConfigAction.execute(ConfigAction.java:335)
     at oracle.as.install.engine.modules.configuration.action.TaskPerformer.run(TaskPerformer.java:87)
     at oracle.as.install.engine.modules.configuration.action.TaskPerformer.startConfigAction(TaskPerformer.java:104)
     at oracle.as.install.engine.modules.configuration.action.ActionRequest.perform(ActionRequest.java:15)
     at oracle.as.install.engine.modules.configuration.action.RequestQueue.perform(RequestQueue.java:63)
     at oracle.as.install.engine.modules.configuration.standard.StandardConfigActionManager.start(StandardConfigActionManager.java:158)
[2012-11-21T19:55:36.984+03:00] [as] [ERROR] [] [oracle.as.provisioning] [tid: 15] [ecid: 0000JgZduXmFw02_vp_AiX1GfFUl000006,0] [[
java.net.MalformedURLException: Bad host: "ccx_weblogic.spb.ru"
     at javax.management.remote.JMXServiceURL.validateHost(JMXServiceURL.java:459)
     at javax.management.remote.JMXServiceURL.validateHost(JMXServiceURL.java:361)
     at javax.management.remote.JMXServiceURL.validate(JMXServiceURL.java:337)
     at javax.management.remote.JMXServiceURL.<init>(JMXServiceURL.java:321)
     at oracle.as.provisioning.weblogic.AdminServer.connect(AdminServer.java:89)
     at oracle.as.provisioning.weblogic.ASDomain._connectToAdminServer(ASDomain.java:405)
     at oracle.as.provisioning.weblogic.ASDomain.connectToAdminServer(ASDomain.java:359)
     at oracle.as.provisioning.engine.WorkFlowExecutor.executeWLSWorkFlow(WorkFlowExecutor.java:411)
     at oracle.as.provisioning.engine.Config.executeConfigWorkflow_WLS(Config.java:866)
     at oracle.as.install.bi.biconfig.standard.StandardWorkFlowExecutor.executeHelper(StandardWorkFlowExecutor.java:31)
     at oracle.as.install.bi.biconfig.standard.ConfigTemplateTask.doExecute(ConfigTemplateTask.java:34)
     at oracle.as.install.bi.biconfig.standard.AbstractProvisioningTask.execute(AbstractProvisioningTask.java:70)
     at oracle.as.install.bi.biconfig.standard.StandardProvisionTaskList.execute(StandardProvisionTaskList.java:61)
     at oracle.as.install.bi.biconfig.BIConfigMain.doExecute(BIConfigMain.java:112)
     at oracle.as.install.engine.modules.configuration.client.ConfigAction.execute(ConfigAction.java:335)
     at oracle.as.install.engine.modules.configuration.action.TaskPerformer.run(TaskPerformer.java:87)
     at oracle.as.install.engine.modules.configuration.action.TaskPerformer.startConfigAction(TaskPerformer.java:104)
     at oracle.as.install.engine.modules.configuration.action.ActionRequest.perform(ActionRequest.java:15)
     at oracle.as.install.engine.modules.configuration.action.RequestQueue.perform(RequestQueue.java:63)
     at oracle.as.install.engine.modules.configuration.standard.StandardConfigActionManager.start(StandardConfigActionManager.java:158)
     at oracle.as.install.engine.modules.configuration.boot.ConfigurationExtension.kickstart(ConfigurationExtension.java:81)
     at oracle.as.install.engine.modules.configuration.ConfigurationModule.run(ConfigurationModule.java:83)
     at java.lang.Thread.run(Thread.java:662)
[2012-11-21T19:55:36.985+03:00] [as] [NOTIFICATION] [] [oracle.as.provisioning] [tid: 15] [ecid: 0000JgZduXmFw02_vp_AiX1GfFUl000006,0] RETURN: _connectToAdminServer
[2012-11-21T19:55:36.986+03:00] [as] [ERROR] [] [oracle.as.provisioning] [tid: 15] [ecid: 0000JgZduXmFw02_vp_AiX1GfFUl000006,0] [[
oracle.as.provisioning.engine.CfgWorkflowException
     at oracle.as.provisioning.engine.Engine.processEventResponse(Engine.java:596)
     at oracle.as.provisioning.weblogic.ASDomain.connectToAdminServer(ASDomain.java:369)
     at oracle.as.provisioning.engine.WorkFlowExecutor.executeWLSWorkFlow(WorkFlowExecutor.java:411)
     at oracle.as.provisioning.engine.Config.executeConfigWorkflow_WLS(Config.java:866)
     at oracle.as.install.bi.biconfig.standard.StandardWorkFlowExecutor.executeHelper(StandardWorkFlowExecutor.java:31)
     at oracle.as.install.bi.biconfig.standard.ConfigTemplateTask.doExecute(ConfigTemplateTask.java:34)
     at oracle.as.install.bi.biconfig.standard.AbstractProvisioningTask.execute(AbstractProvisioningTask.java:70)
     at oracle.as.install.bi.biconfig.standard.StandardProvisionTaskList.execute(StandardProvisionTaskList.java:61)
     at oracle.as.install.bi.biconfig.BIConfigMain.doExecute(BIConfigMain.java:112)
     at oracle.as.install.engine.modules.configuration.client.ConfigAction.execute(ConfigAction.java:335)
     at oracle.as.install.engine.modules.configuration.action.TaskPerformer.run(TaskPerformer.java:87)
     at oracle.as.install.engine.modules.configuration.action.TaskPerformer.startConfigAction(TaskPerformer.java:104)
     at oracle.as.install.engine.modules.configuration.action.ActionRequest.perform(ActionRequest.java:15)
     at oracle.as.install.engine.modules.configuration.action.RequestQueue.perform(RequestQueue.java:63)
     at oracle.as.install.engine.modules.configuration.standard.StandardConfigActionManager.start(StandardConfigActionManager.java:158)
     at oracle.as.install.engine.modules.configuration.boot.ConfigurationExtension.kickstart(ConfigurationExtension.java:81)
     at oracle.as.install.engine.modules.configuration.ConfigurationModule.run(ConfigurationModule.java:83)
     at java.lang.Thread.run(Thread.java:662)
Caused by: oracle.as.provisioning.util.ConfigException:
Unable to connect to the AdminServer.
Cause:
An internal operation has failed:Bad host: " ccx_weblogic.spb.ru"
Action:
See logs for more details.
     at oracle.as.provisioning.util.ConfigException.createConfigException(ConfigException.java:123)
     at oracle.as.provisioning.weblogic.ASDomain._connectToAdminServer(ASDomain.java:438)
     at oracle.as.provisioning.weblogic.ASDomain.connectToAdminServer(ASDomain.java:359)
     ... 16 more
Caused by: java.net.MalformedURLException: Bad host: " ccx_weblogic.spb.ru"
     at javax.management.remote.JMXServiceURL.validateHost(JMXServiceURL.java:459)
     at javax.management.remote.JMXServiceURL.validateHost(JMXServiceURL.java:361)
     at javax.management.remote.JMXServiceURL.validate(JMXServiceURL.java:337)
     at javax.management.remote.JMXServiceURL.<init>(JMXServiceURL.java:321)
     at oracle.as.provisioning.weblogic.AdminServer.connect(AdminServer.java:89)
     at oracle.as.provisioning.weblogic.ASDomain._connectToAdminServer(ASDomain.java:405)
     ... 17 more
[2012-11-21T19:55:36.989+03:00] [as] [NOTIFICATION] [] [oracle.as.install.engine.modules.silent] [tid: 15] [ecid: 0000JgZduXmFw02_vp_AiX1GfFUl000006,0] [CONFIG] STEP: Deploying Base Setup : RETURN STATUS [FAILED]null
[2012-11-21T19:55:36.996+03:00] [as] [NOTIFICATION] [] [oracle.as.install.bi] [tid: 15] [ecid: 0000JgZduXmFw02_vp_AiX1GfFUl000006,0] Connecting to JMX URL: [service:jmx:t3://ccx_weblogic.spb.ru:7003/jndi/weblogic.management.mbeanservers.domainruntime] with userid: weblogic
[2012-11-21T19:55:36.996+03:00] [as] [ERROR] [] [oracle.as.install.bi] [tid: 15] [ecid: 0000JgZduXmFw02_vp_AiX1GfFUl000006,0] Failed to connect to Web Logic MBean Server. The following URL is invalid: service:jmx:t3://ccx_weblogic.spb.ru:7003/jndi/weblogic.management.mbeanservers.domainruntime[[
*java.net.MalformedURLException: Bad URL path: _weblogic.spb.ru:7003/jndi/weblogic.management.mbeanservers.domainruntime*
     at javax.management.remote.JMXServiceURL.validate(JMXServiceURL.java:348)
     at javax.management.remote.JMXServiceURL.<init>(JMXServiceURL.java:208)
     at oracle.as.install.bi.util.JMXUtils._getMBeanServerConnection(JMXUtils.java:109)
     at oracle.as.install.bi.util.JMXUtils.getDomainRuntimeMBeanServerConnection(JMXUtils.java:33)
     at oracle.as.install.bi.biconfig.util.MBeanServerConnectionFromDataStore.getDomainRuntime(MBeanServerConnectionFromDataStore.java:17)
     at oracle.as.install.bi.biconfig.standard.UpdateJDBCDetailsTask.getRealServerNameLookup(UpdateJDBCDetailsTask.java:27)
     at oracle.as.install.bi.biconfig.standard.UpdateJDBCDetailsTask.getWLSTCmdArgs(UpdateJDBCDetailsTask.java:53)
     at oracle.as.install.bi.biconfig.standard.WLSTScriptTask.initializeScriptParameters(WLSTScriptTask.java:130)
     at oracle.as.install.bi.biconfig.standard.WLSTScriptTask.doExecute(WLSTScriptTask.java:93)
     at oracle.as.install.bi.biconfig.standard.AbstractProvisioningTask.execute(AbstractProvisioningTask.java:70)
     at oracle.as.install.bi.biconfig.standard.StandardProvisionTaskList.execute(StandardProvisionTaskList.java:61)
     at oracle.as.install.bi.biconfig.BIConfigMain.doExecute(BIConfigMain.java:112)
     at oracle.as.install.engine.modules.configuration.client.ConfigAction.execute(ConfigAction.java:335)
     at oracle.as.install.engine.modules.configuration.action.TaskPerformer.run(TaskPerformer.java:87)
     at oracle.as.install.engine.modules.configuration.action.TaskPerformer.startConfigAction(TaskPerformer.java:104)
     at oracle.as.install.engine.modules.configuration.action.ActionRequest.perform(ActionRequest.java:15)
     at oracle.as.install.engine.modules.configuration.action.RequestQueue.perform(RequestQueue.java:63)
     at oracle.as.install.engine.modules.configuration.standard.StandardConfigActionManager.start(StandardConfigActionManager.java:158)
     at oracle.as.install.engine.modules.configuration.boot.ConfigurationExtension.kickstart(ConfigurationExtension.java:81)
     at oracle.as.install.engine.modules.configuration.ConfigurationModule.run(ConfigurationModule.java:83)
     at java.lang.Thread.run(Thread.java:662)
     at oracle.as.install.engine.modules.configuration.boot.ConfigurationExtension.kickstart(ConfigurationExtension.java:81)
     at oracle.as.install.engine.modules.configuration.ConfigurationModule.run(ConfigurationModule.java:83)
     at java.lang.Thread.run(Thread.java:662)
[2012-11-21T19:55:36.732+03:00] [as] [ERROR] [] [oracle.as.provisioning] [tid: 15] [ecid: 0000JgZduXmFw02_vp_AiX1GfFUl000006,0] [[
oracle.as.provisioning.exception.ASProvWorkflowException: Error Executing workflow.
     at oracle.as.provisioning.engine.WorkFlowExecutor._createDomain(WorkFlowExecutor.java:686)
     at oracle.as.provisioning.engine.WorkFlowExecutor.executeWLSWorkFlow(WorkFlowExecutor.java:391)
     at oracle.as.provisioning.engine.Config.executeConfigWorkflow_WLS(Config.java:866)
     at oracle.as.install.bi.biconfig.standard.StandardWorkFlowExecutor.executeHelper(StandardWorkFlowExecutor.java:31)
     at oracle.as.install.bi.biconfig.standard.DomainProvisioningTask.doExecute(DomainProvisioningTask.java:48)
     at oracle.as.install.bi.biconfig.standard.AbstractProvisioningTask.execute(AbstractProvisioningTask.java:70)
     at oracle.as.install.bi.biconfig.standard.StandardProvisionTaskList.execute(StandardProvisionTaskList.java:61)
     at oracle.as.install.bi.biconfig.BIConfigMain.doExecute(BIConfigMain.java:112)
     at oracle.as.install.engine.modules.configuration.client.ConfigAction.execute(ConfigAction.java:335)
     at oracle.as.install.engine.modules.configuration.action.TaskPerformer.run(TaskPerformer.java:87)
     at oracle.as.install.engine.modules.configuration.action.TaskPerformer.startConfigAction(TaskPerformer.java:104)
     at oracle.as.install.engine.modules.configuration.action.ActionRequest.perform(ActionRequest.java:15)
     at oracle.as.install.engine.modules.configuration.action.RequestQueue.perform(RequestQueue.java:63)
     at oracle.as.install.engine.modules.configuration.standard.StandardConfigActionManager.start(StandardConfigActionManager.java:158)
     at oracle.as.install.engine.modules.configuration.boot.ConfigurationExtension.kickstart(ConfigurationExtension.java:81)
     at oracle.as.install.engine.modules.configuration.ConfigurationModule.run(ConfigurationModule.java:83)
     at java.lang.Thread.run(Thread.java:662)
Please help us.
P.S. We cann't understand why in logs we see that string
java.net.MalformedURLException: Bad URL path: _weblogic.spb.ru:7003/jndi/weblogic.management.mbeanservers.domainruntime*

Hello,
You need to make sure you have right entries on /etc/hosts on your linux -x64 environment.
Follow this blog : http://blog.chain-sys.com/obiee-11g-installation-on-linux-64-bit-oel/
Hope this helps. Pls mark if it does.
-SVS

Dynamic jndi-name in weblogic-ejb-jar.xml

Is there a way to create dynamic (i.e. runtime) jndi-names for EJBs instead of
(or in addition to) "hard coding" them in the weblogic-ejb-jar.xml file? What
I'm trying to do is have one WebLogic instance (JVM) host multiple environments
(our Beta and Training environments) and I simply want to deploy the same .ear
file twice but have each environment (application - .ear) reference a different
database schema (jdbc connection pool). I have everything working just fine for
this scenario except when I define jndi-names for our ejbs. The problem is that
I am really deploying the same ejbs (jndi-names and actually code base) in each
applicatoin instance and I get an exception when the WebLogic is trying to deploy
the second application (.ear) because the jndi-names in it have already been deployed
by the first application instance. I recieve a jndi error stating that the name
is already deployed.
Or is there a better path to go down for what I am trying to do to have one WebLogic
instance support our beta and training environments? Usually (but not always)
our code base is the for same for both of these environments, I simply need to
have each environment use a different database schema.
Thanks

A little birdie tells me that BEA does this very thing. Looking at the
descriptors for WebLogic Portal I see:
<weblogic-enterprise-bean>
<ejb-name>LoaderEJB</ejb-name>
<enable-call-by-reference>True</enable-call-by-reference>
<jndi-name>${APPNAME}.BEA_content.LoaderHome</jndi-name>
</weblogic-enterprise-bean>
Yes, the ${APPNAME} token really is expanded into the J2EE application
name at deployment time!
Sincerely,
Daniel Selman
Bryan Dixon wrote:
Rewriting our build process isn't really much of an option for me. Our current
build process is too complex and time consuming right now to convert to Ant (we
eventually will do this but not for a while). So are there any other ideas that
aren't build related?
Thanks
"Eric Ma" <[email protected]> wrote:
You don't need run-time dynamism in JDNI names and it can't be done anyways.
You
need token substitution in XML configuration files when building the
app. If
you are using Ant for building, then it is a breeze. If not, first convert
your
build process to use Ant.
Also, a single WLS instance hosting multiple environments sounds really
INTRIGUING
to me.
Eric Ma
"Bryan Dixon" <[email protected]> wrote:
Is there a way to create dynamic (i.e. runtime) jndi-names for EJBsinstead
of
(or in addition to) "hard coding" them in the weblogic-ejb-jar.xml file?
What
I'm trying to do is have one WebLogic instance (JVM) host multiple environments
(our Beta and Training environments) and I simply want to deploy the
same .ear
file twice but have each environment (application - .ear) referencea
different
database schema (jdbc connection pool). I have everything working just
fine for
this scenario except when I define jndi-names for our ejbs. The problem
is that
I am really deploying the same ejbs (jndi-names and actually code base)
in each
applicatoin instance and I get an exception when the WebLogic is trying
to deploy
the second application (.ear) because the jndi-names in it have already
been deployed
by the first application instance. I recieve a jndi error stating that
the name
is already deployed.
Or is there a better path to go down for what I am trying to do to have
one WebLogic
instance support our beta and training environments? Usually (but not
always)
our code base is the for same for both of these environments, I simply
need to
have each environment use a different database schema.
Thanks

WTC8.1 cannot lookup TuxedoConnection in JNDI for a Tuxedo8.1 service

Hi,
I have Weblogic WTC configured to use a Tuxedo service and the ejb cannot lookup the TuxedoConnection object.
The error from the client is shown below:
java tperrno encountered: TPENOENT(6):0:0:TPED_MINVAL(0):QMNONE(0):0:Could not get TuxedoConnectionFactory : javax.naming.NameNotFoundException: Unable to resolve 'tuxedo.services.TuxedoConnection' Resolved tuxedo.services; remaining name 'TuxedoConnection'
I confirmed that the Tuxedo service is listening on port 9001 on machine 15.8.156.143
Here is the wtc server config:
<WTCServer Name="mySimpapp">
<WTCRemoteTuxDom AccessPoint="myRemoteAp" AccessPointId="TDOM1
LocalAccessPoint="myLocalAp" NWAddr="//15.8.156.143:9001"
Name="WTCRemoteTuxDom-1251829072487"/>
<WTCImport LocalAccessPoint="myLocalAp"
Name="WTCImport-1251829191287"
RemoteAccessPointList="myRemoteAp" RemoteName="TOUPPER" Re
sourceName="TOUPPER"/>
</WTCServer>
and here is the tuxedo service config:
*DM_RESOURCES
VERSION=U22
*DM_LOCAL_DOMAINS
TDOM1 GWGRP=GROUP2
TYPE=TDOMAIN
DOMAINID="TDOM1"
BLOCKTIME=20
MAXDATALEN=56
MAXRDOM=89
DMTLOGDEV="/opt/beatux/tuxedo8.1/samples/wtc/simpserv/tlog"
DMTLOGNAME="log1"
*DM_REMOTE_DOMAINS
*DM_TDOMAIN
TDOM1 NWADDR="//15.8.156.143:9001"
*DM_REMOTE_SERVICES
I looked at the JNDI tree in Weblogic console and there is no tuxedo.services.TuxedoConnection object in the JNDI tree.
regards
-Sarab

Hi Sarab,
Did you target the WTC Server to one of your WLS instances? As for something listening on "//15.8.156.143:9001", you appear to have both WTC and Tuxedo trying to use that port to listen on. That's not going to work. If WLS and Tuxedo are on the same machine, the local domain (local access point) for each needs to listen on a unique port. So at a minimum you need to have WTC listen on one port and the Tuxedo domain gateway listen on a different port. Also, whether Tuxedo is up or not will not affect your ability to get the JNDI name.
Also, you should see in the WLS startup log indications that WTC started if it has been targeted to a WLS instance.
Regards,
Todd Little
Oracle Tuxedo Chief Architect

Why in jndi tree I find the remote interface to String is so strange?

          when I view the jndi tree in weblogic server 61sp1
          I found such information:
          Bind Name: Enterprise1
          Class: class $Proxy94
          to String: ClusterableRemoteRef(10.132.0.161 [10.132.0.161])/275
          hash Code: 4568198
          Why the Class and to String like such? my license.bea
          is not a cluster version.


          Thanks you very much
          "Kumar Allamraju" <[email protected]> wrote:
          >EJB's are compiled with clustering options "ON". that's why you are seeing
          >a
          >ClusterableRemoteRef.
          >Don't worry, you will not be able to run WLS instances in cluster mode
          >without having a cluster license.
          >
          >--
          >--
          >Kumar
          >
          >"Eric nie" <[email protected]> wrote in message
          >news:3ca8238a$[email protected]..
          >>
          >> when I view the jndi tree in weblogic server 61sp1
          >> I found such information:
          >>
          >> Bind Name: Enterprise1
          >> Class: class $Proxy94
          >> to String: ClusterableRemoteRef(10.132.0.161 [10.132.0.161])/275
          >> hash Code: 4568198
          >>
          >> Why the Class and to String like such? my license.bea
          >> is not a cluster version.
          >>
          >
          >

2 WLS Instances :relationship in JNDI

Similar Messages

Maybe you are looking for