Whole server migration
Hi,
I am setting up a cluster with two managed serves on different machines. In order to setup whole server migration, do I need to have third machine? In many of the examples i have seen they say when MACHINE1 is down, it can be migrated to MACHINE2..how is this possible if both managed servers listening on the same port? can you please let me know if I need to have third machine? if so, do I need to transfer the domain data via pack and unpack to third machine as well?
Thanks.
Hi
Since your 2 managed servers are on 2 different physical machines, yes, they can share the same port number. Remember they had different host numbers. If they are on same physical machine, naturally you will have 2 different unique port numbers. Now coming to failover, generally for any Cluster Domain, in the front you will have some sort of Load Balancer. The typical example is Apache HTTP Server as Load Balancer. We install and configure apache and edit httpd.conf file to give backend weblogic servers. For example one line could be like this:
ClusterAddress: host1:port1,host2:port2 (Ex: host1:8001,host2:8001). So it is Apache that takes care of Failover and load balancing. If host is dead or server1 on host1 is crashed, apache will remove this server from its internal list (till it is back and up and running. So all next requiests will go to host2:8001.
This has nothing to do with same or diff port numbers. All that matters is, port numbers are unique if servers are on same physical machine.
This means, there is no need for any other 3rd machine.
If your question is something else, please give more details.
Thanks
Ravi Jegga
Similar Messages
-
10.3 Whole Server Migration
Hi,
I need some enlightenments from all. Here is my setup (in Windows 2003 R2)
2 physical Server, PS A, PS B (PS: physical server)
PS A contains, 1 Admin Server, 1 Managed server
PS B contains, 1 Managed Server
I've done the necessary clustering setup and tested its working, using node manager (nmenroll, conseus, etc). now what I'm trying to perform is to try out whole sever migration.
I've found out the script, wlsifconfig.cmd (found under %wls_home%\user_projects\domains\abc\bin\server_migration\, contains some linux command such as grep and rm. Workaround installed grep command for windows and replace rm with del.
I've shut down all managed servers and configure the managed servers to be whole server migration ready, set the node manager properties etc. I start the managed server 1 in PS A, PS A contains the floating IP upon starting. I checked using ipconfig, the floating IP is added. Then I tried to start managed server 2 through the admin console in PS A. Here comes the problem, managed server 2 also add in the floating IP which resulted in windows IP conflict. I'm not sure what went wrong, as of now i suspect is the wlsifconfig.cmd is the root of the problem. Therefore writing in to ask help from all. (Could it be im using 10.3 which does not support whole server migration?)
Best RegardsThis appears to be working on Windows using 10.0.3 Server. For the lack of step-by-step tutorial, my best suggestion is to read Node Manager Administrator's Guide chapter 1,2,3,4,6 and "Using Clusters" chapter 7. I ran into many error messages and had to apply several hacks from google results.
The whole server migration design does not appear to be too useful though.
I have the whole server migration configured on two hosts.
1. Machine A has AdminServer and M1 (runs a pinned application and happens to be assigned a cluster master)
2. Machine B has node manager and M2.
3. M1 is set up to be migratable to A and B
I shutdown Machine A, but nothing is migrated. From the document, it seems both cluster master and AdminServer need to be running in order for migration to happen. This is still a single point of failure. -
Whole Server Migration working on Windows?
Does anyone have experience successfully configure whole server migration on windows? Is it possible to get some step by step guide?
This appears to be working on Windows using 10.0.3 Server. For the lack of step-by-step tutorial, my best suggestion is to read Node Manager Administrator's Guide chapter 1,2,3,4,6 and "Using Clusters" chapter 7. I ran into many error messages and had to apply several hacks from google results.
The whole server migration design does not appear to be too useful though.
I have the whole server migration configured on two hosts.
1. Machine A has AdminServer and M1 (runs a pinned application and happens to be assigned a cluster master)
2. Machine B has node manager and M2.
3. M1 is set up to be migratable to A and B
I shutdown Machine A, but nothing is migrated. From the document, it seems both cluster master and AdminServer need to be running in order for migration to happen. This is still a single point of failure. -
BAM Cluster setup - issue with whole server migration configuration
HI,
We are working on a SOA , BAM , BPM Cluster setup on OEL VMs
With Admin server running on Host1 and Soa_server1, BAM_server1 , Host2 - Soa_server2 , Bam_server2.
We were successfully able to setup clustering for Soa without using the webTier utilities in our environment, Just by adding entries in the /etc/hosts file.
Followed the document - except for web tier setup
http://www.namredlek.nl/orasoa/InstallSOASuite11gOnCluster_v1.pdf
1) Installed Weblogic 11g.
2) Soa 11g.
3) Domain creation
4) Configured Node manager
5) Soa Clustering completed successfully.
6) Domain up and running with SOA_Cluster up and running.
7) Extended the domain with BAM
The issue revolves when we are doing teh Migration configurations from the console for BAM and we restart BAM server we get an error -
Apr 14, 2011 2:30:35 AM weblogic.nodemanager.server.Handler handleStart
WARNING: Exception while starting server 'bam_server1'
java.io.IOException: Command '/oracle/Shared_MWHome/user_projects/domains/SOA_Domain/bin/server_migration/wlsifconfig.sh -addif eth0 192.168.1.6 255.255.255.0 ' returned an unsuccessful exit code '1'. Check NM logs for script output.
and Bam server goes to Failed Not Restartable state.The error is clearly out there
java.io.IOException: Command '/oracle/Shared_MWHome/user_projects/domains/SOA_Domain/bin/server_migration/wlsifconfig.sh -addif eth0 192.168.1.6 255.255.255.0 ' returned an unsuccessful exit code '1'. Check NM logs for script output.
This error occurs due to a failure in adding the virtual IP of BAM server to the network interface you have specified in nodemanager.properties.
You need to check whether you have specified the correct interface and subnet mask in node manager.properties as below :
The fourth step is to edit the Node Manager's properties file. This file is called nodemanager.properties
and is located in the ORACLE_BASE/product/osbmw/wlserver_10.3/common/nodemanager directory.
For server migration to work properly, you need to add the properties listed below:
Interface=eth0
NetMask=255.255.255.0
UseMACBroadcast=true
· Interface
This property specifies the interface name for the floating IP (for example, eth0).
· NetMask
This property specifies the net mask for the interface for the floating IP. The net mask should the
same as the net mask on the interface; 255.255.255.0 is used as an example in this document.
· UseMACBroadcast
This property specifies whether or not to use a node's MAC address when sending ARP packets,
that is, whether or not to use the -b flag in the arping command. -
Whole server migarion issue in weblogic
I have configured the Script Based node manager. Through admin console i am able to start the remote managed servers psMS1 , psMS2.
192.168.9.11 –> Adminserver , psMS1
192.168.9.22 –> psMS2
We have create Two unix machine Unix1 , Unix1.
Unix1 –> assign servers Adminserver , psMS1.
Unix2 –> assing server psMS2.
The Two manager servers (psMS1,psMS2) is configured with Cluster (CLUST).
But If i configure the Whole server migration option in the weblogic Admin console. I am unable to start Two managed servers. I mentioned the Two managed severs errors logs.
psMS1 Error log :- ( 192.168.9.11 ) –> Unix1 machine
<Fri Dec 3 15:14:09 IST 2010)> <Info> <NodeManager> <Starting WLS with command line: /prosun/Middleware_1033/user_projects/domains/clustdomain/bin/startManagedWebLogic.sh >
JAVA Memory arguments: -Xms256m -Xmx512m
WLS Start Mode=Production
CLASSPATH=/prosun/Middleware_1033/wlserver_10.3/server/ext/jdbc/oracle/11g/ojdbc6dms.jar:/prosun/Middleware_1033/patch_wls1033/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/prosun/Middleware_1033/patch_ocp353/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/prosun/Middleware_1033/patch_jdev1111/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/prosun/Middleware_1033/jrockit_160_17_R28.0.0-679/lib/tools.jar:/prosun/Middleware_1033/wlserver_10.3/server/lib/weblogic_sp.jar:/prosun/Middleware_1033/wlserver_10.3/server/lib/weblogic.jar:/prosun/Middleware_1033/modules/features/weblogic.server.modules_10.3.3.0.jar:/prosun/Middleware_1033/wlserver_10.3/server/lib/webservices.jar:/prosun/Middleware_1033/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/prosun/Middleware_1033/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:/prosun/Middleware_1033/oracle_common/modules/oracle.jrf_11.1.1/jrf.jar:/prosun/Middleware_1033/wlserver_10.3/common/derby/lib/derbyclient.jar:/prosun/Middleware_1033/wlserver_10.3/server/lib/xqrl.jar
PATH=/prosun/Middleware_1033/wlserver_10.3/server/bin:/prosun/Middleware_1033/modules/org.apache.ant_1.7.1/bin:/prosun/Middleware_1033/jrockit_160_17_R28.0.0-679/jre/bin:/prosun/Middleware_1033/jrockit_160_17_R28.0.0-679/bin:/usr/lib64/qt-3.3/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/prosun/Middleware_1033/wlserver_10.3/common/bin
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://hostname:port/console *
starting weblogic with Java version:
java version "1.6.0_17"
Java(TM) SE Runtime Environment (build 1.6.0_17-b04)
Oracle JRockit(R) (build R28.0.0-679-130297-1.6.0_17-20100312-2128-linux-ia32, compiled mode)
Starting WLS with line:
/prosun/Middleware_1033/jrockit_160_17_R28.0.0-679/bin/java -jrockit -Xms256m -Xmx512m -Dweblogic.Name=psMS1 -Djava.security.policy=/prosun/Middleware_1033/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.ProductionModeEnabled=true -Dweblogic.security.SSL.trustedCAKeyStore=/prosun/Middleware_1033/wlserver_10.3/server/lib/cacerts -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.system.BootIdentityFile=servers/psMS1/data/nodemanager/boot.properties -da -Dplatform.home=/prosun/Middleware_1033/wlserver_10.3 -Dwls.home=/prosun/Middleware_1033/wlserver_10.3/server -Dweblogic.home=/prosun/Middleware_1033/wlserver_10.3/server -Ddomain.home=/prosun/Middleware_1033/user_projects/domains/clustdomain -Dcommon.components.home=/prosun/Middleware_1033/oracle_common -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Djrockit.optfile=/prosun/Middleware_1033/oracle_common/modules/oracle.jrf_11.1.1/jrocket_optfile.txt -Doracle.domain.config.dir=/prosun/Middleware_1033/user_projects/domains/clustdomain/config/fmwconfig -Doracle.server.config.dir=/prosun/Middleware_1033/user_projects/domains/clustdomain/config/fmwconfig/servers/psMS1 -Doracle.security.jps.config=/prosun/Middleware_1033/user_projects/domains/clustdomain/config/fmwconfig/jps-config.xml -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Digf.arisidbeans.carmlloc=/prosun/Middleware_1033/user_projects/domains/clustdomain/config/fmwconfig/carml -Digf.arisidstack.home=/prosun/Middleware_1033/user_projects/domains/clustdomain/config/fmwconfig/arisidprovider -Dweblogic.alternateTypesDirectory=/prosun/Middleware_1033/oracle_common/modules/oracle.ossoiap_11.1.1,/prosun/Middleware_1033/oracle_common/modules/oracle.oamprovider_11.1.1 -Dweblogic.jdbc.remoteEnabled=false -Dweblogic.management.discover=false -Dweblogic.management.server=http://sis-prosun02.sis.ad:5001 -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=/prosun/Middleware_1033/patch_wls1033/profiles/default/sysext_manifest_classpath:/prosun/Middleware_1033/patch_ocp353/profiles/default/sysext_manifest_classpath:/prosun/Middleware_1033/patch_jdev1111/profiles/default/sysext_manifest_classpath weblogic.Server
[WARN ] Use of -Djrockit.optfile is deprecated and discouraged.
<Dec 3, 2010 3:14:11 PM IST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Oracle JRockit(R) Version R28.0.0-679-130297-1.6.0_17-20100312-2128-linux-ia32 from Oracle Corporation>
<Dec 3, 2010 3:14:13 PM IST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.3.0 Fri Apr 9 00:05:28 PDT 2010 1321401 >
<Dec 3, 2010 3:14:15 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Dec 3, 2010 3:14:15 PM IST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Dec 3, 2010 3:14:16 PM IST> <Notice> <Log Management> <BEA-170019> <The server log file /prosun/Middleware_1033/user_projects/domains/clustdomain/servers/psMS1/logs/psMS1.log is opened. All server side log events will be written to this file.>
<Dec 3, 2010 3:14:22 PM IST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Dec 3, 2010 3:14:27 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<Dec 3, 2010 3:14:27 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Dec 3, 2010 3:14:31 PM IST> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
<Dec 3, 2010 3:14:31 PM IST> <Notice> <Cluster> <BEA-000197> <Listening for announcements from cluster using unicast cluster messaging>
<Dec 3, 2010 3:14:31 PM IST> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of CLUST.>
<Dec 3, 2010 3:15:01 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Dec 3, 2010 3:15:01 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<Dec 3, 2010 3:15:01 PM IST> <Notice> <Cluster> <BEA-000162> <Starting "async" replication service with remote cluster address "null">
<Dec 3, 2010 3:15:01 PM IST> <Warning> <Server> <BEA-002611> <Hostname "localhost", maps to multiple IP addresses: 127.0.0.1, 0:0:0:0:0:0:0:1>
<Dec 3, 2010 3:15:01 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default[3]" is now listening on 0:0:0:0:0:0:0:1:5003 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Dec 3, 2010 3:15:01 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 192.168.9.11:5003 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Dec 3, 2010 3:15:01 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default[2]" is now listening on 127.0.0.1:5003 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Dec 3, 2010 3:15:01 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on fe80:0:0:0:250:56ff:feaf:649a:5003 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Dec 3, 2010 3:15:01 PM IST> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "psMS1" for domain "clustdomain" running in Production Mode>
<Dec 3, 2010 3:15:04 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<Dec 3, 2010 3:15:04 PM IST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<Dec 3, 2010 4:07:19 PM IST> <Alert> <WebLogicServer> <BEA-000396> <Server shutdown has been requested by weblogic>
<Dec 3, 2010 4:07:19 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SUSPENDING>
<Dec 3, 2010 4:07:19 PM IST> <Notice> <Cluster> <BEA-000163> <Stopping "async" replication service>
<Dec 3, 2010 4:07:19 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Dec 3, 2010 4:07:19 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
<Dec 3, 2010 4:07:19 PM IST> <Notice> <Server> <BEA-002607> <Channel "Default[3]" listening on 0:0:0:0:0:0:0:1:5003 was shutdown.>
<Dec 3, 2010 4:07:19 PM IST> <Notice> <Server> <BEA-002607> <Channel "Default[1]" listening on fe80:0:0:0:250:56ff:feaf:649a:5003 was shutdown.>
<Dec 3, 2010 4:07:19 PM IST> <Notice> <Server> <BEA-002607> <Channel "Default[2]" listening on 127.0.0.1:5003 was shutdown.>
<Dec 3, 2010 4:07:19 PM IST> <Notice> <Server> <BEA-002607> <Channel "Default" listening on 192.168.9.11:5003 was shutdown.>
<Fri Dec 3 16:07:25 IST 2010)> <Info> <NodeManager> <Server start script exited>
<Fri Dec 3 16:07:25 IST 2010)> <Info> <NodeManager> <Server was shut down normally>
psMS2 Error log :- ( 192.168.9.22 ) –> Unix2 machine
<Fri Dec 3 15:32:35 IST 2010)> <Info> <NodeManager> <Starting WLS with command line: /prosun/Middleware_1033/user_projects/domains/clustdomain/bin/startManagedWebLogic.sh >
JAVA Memory arguments: -Xms256m -Xmx512m
WLS Start Mode=Production
CLASSPATH=/prosun/Middleware_1033/wlserver_10.3/server/ext/jdbc/oracle/11g/ojdbc6dms.jar:/prosun/Middleware_1033/patch_wls1033/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/prosun/Middleware_1033/patch_ocp353/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/prosun/Middleware_1033/patch_jdev1111/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/prosun/Middleware_1033/jrockit_160_17_R28.0.0-679/lib/tools.jar:/prosun/Middleware_1033/wlserver_10.3/server/lib/weblogic_sp.jar:/prosun/Middleware_1033/wlserver_10.3/server/lib/weblogic.jar:/prosun/Middleware_1033/modules/features/weblogic.server.modules_10.3.3.0.jar:/prosun/Middleware_1033/wlserver_10.3/server/lib/webservices.jar:/prosun/Middleware_1033/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/prosun/Middleware_1033/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:/prosun/Middleware_1033/oracle_common/modules/oracle.jrf_11.1.1/jrf.jar:/prosun/Middleware_1033/wlserver_10.3/common/derby/lib/derbyclient.jar:/prosun/Middleware_1033/wlserver_10.3/server/lib/xqrl.jar
PATH=/prosun/Middleware_1033/wlserver_10.3/server/bin:/prosun/Middleware_1033/modules/org.apache.ant_1.7.1/bin:/prosun/Middleware_1033/jrockit_160_17_R28.0.0-679/jre/bin:/prosun/Middleware_1033/jrockit_160_17_R28.0.0-679/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/prosun/Middleware_1033/wlserver_10.3/common/bin
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://hostname:port/console *
starting weblogic with Java version:
java version "1.6.0_17"
Java(TM) SE Runtime Environment (build 1.6.0_17-b04)
Oracle JRockit(R) (build R28.0.0-679-130297-1.6.0_17-20100312-2128-linux-ia32, compiled mode)
Starting WLS with line:
/prosun/Middleware_1033/jrockit_160_17_R28.0.0-679/bin/java -jrockit -Xms256m -Xmx512m -Dweblogic.Name=psMS2 -Djava.security.policy=/prosun/Middleware_1033/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.ProductionModeEnabled=true -Dweblogic.security.SSL.trustedCAKeyStore=/prosun/Middleware_1033/wlserver_10.3/server/lib/cacerts -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.system.BootIdentityFile=servers/psMS2/data/nodemanager/boot.properties -da -Dplatform.home=/prosun/Middleware_1033/wlserver_10.3 -Dwls.home=/prosun/Middleware_1033/wlserver_10.3/server -Dweblogic.home=/prosun/Middleware_1033/wlserver_10.3/server -Ddomain.home=/prosun/Middleware_1033/user_projects/domains/clustdomain -Dcommon.components.home=/prosun/Middleware_1033/oracle_common -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Djrockit.optfile=/prosun/Middleware_1033/oracle_common/modules/oracle.jrf_11.1.1/jrocket_optfile.txt -Doracle.domain.config.dir=/prosun/Middleware_1033/user_projects/domains/clustdomain/config/fmwconfig -Doracle.server.config.dir=/prosun/Middleware_1033/user_projects/domains/clustdomain/config/fmwconfig/servers/psMS2 -Doracle.security.jps.config=/prosun/Middleware_1033/user_projects/domains/clustdomain/config/fmwconfig/jps-config.xml -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Digf.arisidbeans.carmlloc=/prosun/Middleware_1033/user_projects/domains/clustdomain/config/fmwconfig/carml -Digf.arisidstack.home=/prosun/Middleware_1033/user_projects/domains/clustdomain/config/fmwconfig/arisidprovider -Dweblogic.alternateTypesDirectory=/prosun/Middleware_1033/oracle_common/modules/oracle.ossoiap_11.1.1,/prosun/Middleware_1033/oracle_common/modules/oracle.oamprovider_11.1.1 -Dweblogic.jdbc.remoteEnabled=false -Dweblogic.management.discover=false -Dweblogic.management.server=http://sis-prosun02.sis.ad:5001 -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=/prosun/Middleware_1033/patch_wls1033/profiles/default/sysext_manifest_classpath:/prosun/Middleware_1033/patch_ocp353/profiles/default/sysext_manifest_classpath:/prosun/Middleware_1033/patch_jdev1111/profiles/default/sysext_manifest_classpath weblogic.Server
[WARN ] Use of -Djrockit.optfile is deprecated and discouraged.
<Dec 3, 2010 3:32:38 PM IST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Oracle JRockit(R) Version R28.0.0-679-130297-1.6.0_17-20100312-2128-linux-ia32 from Oracle Corporation>
<Dec 3, 2010 3:32:40 PM IST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.3.0 Fri Apr 9 00:05:28 PDT 2010 1321401 >
<Dec 3, 2010 3:32:43 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Dec 3, 2010 3:32:43 PM IST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Dec 3, 2010 3:32:44 PM IST> <Notice> <Log Management> <BEA-170019> <The server log file /prosun/Middleware_1033/user_projects/domains/clustdomain/servers/psMS2/logs/psMS2.log is opened. All server side log events will be written to this file.>
<Dec 3, 2010 3:32:50 PM IST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Dec 3, 2010 3:32:53 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<Dec 3, 2010 3:32:53 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Dec 3, 2010 3:33:01 PM IST> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
<Dec 3, 2010 3:33:01 PM IST> <Notice> <Cluster> <BEA-000197> <Listening for announcements from cluster using unicast cluster messaging>
<Dec 3, 2010 3:33:01 PM IST> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of CLUST.>
<Dec 3, 2010 3:33:07 PM IST> <Notice> <Cluster> <BEA-000142> <Trying to download cluster JNDI tree from server psMS1.>
<Dec 3, 2010 3:33:07 PM IST> <Notice> <Cluster> <BEA-000164> <Synchronized cluster JNDI tree from server psMS1.>
<Dec 3, 2010 3:33:07 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Dec 3, 2010 3:33:07 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<Dec 3, 2010 3:33:08 PM IST> <Notice> <Cluster> <BEA-000162> <Starting "async" replication service with remote cluster address "null">
<Dec 3, 2010 3:33:08 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default[3]" is now listening on 0:0:0:0:0:0:0:1:5005 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Dec 3, 2010 3:33:08 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on fe80:0:0:0:225:11ff:feca:8710:5005 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Dec 3, 2010 3:33:08 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 192.168.9.22:5005 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Dec 3, 2010 3:33:08 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default[2]" is now listening on 127.0.0.1:5005 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Dec 3, 2010 3:33:08 PM IST> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "psMS2" for domain "clustdomain" running in Production Mode>
<Dec 3, 2010 3:33:10 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<Dec 3, 2010 3:33:10 PM IST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<Dec 3, 2010 4:00:32 PM IST> <Alert> <WebLogicServer> <BEA-000396> <Server shutdown has been requested by weblogic>
<Dec 3, 2010 4:00:32 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SUSPENDING>
<Dec 3, 2010 4:00:32 PM IST> <Notice> <Cluster> <BEA-000163> <Stopping "async" replication service>
<Dec 3, 2010 4:00:32 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Dec 3, 2010 4:00:32 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
<Dec 3, 2010 4:00:32 PM IST> <Notice> <Server> <BEA-002607> <Channel "Default[3]" listening on 0:0:0:0:0:0:0:1:5005 was shutdown.>
<Dec 3, 2010 4:00:32 PM IST> <Notice> <Server> <BEA-002607> <Channel "Default[1]" listening on fe80:0:0:0:225:11ff:feca:8710:5005 was shutdown.>
<Dec 3, 2010 4:00:32 PM IST> <Notice> <Server> <BEA-002607> <Channel "Default" listening on 192.168.9.22:5005 was shutdown.>
<Dec 3, 2010 4:00:32 PM IST> <Notice> <Server> <BEA-002607> <Channel "Default[2]" listening on 127.0.0.1:5005 was shutdown.>
<Fri Dec 3 16:00:38 IST 2010)> <Info> <NodeManager> <Server start script exited>
<Fri Dec 3 16:00:38 IST 2010)> <Info> <NodeManager> <Server was shut down normally>
How to resolve the problem during the Script based node manager during the Whole Server Migration in Clustered Environment(CLUST).
In my knowledge the main reason is " <Cluster> <BEA-000163> <Stopping "async" replication service> "
Regards,
S.Vinoth Babu
Edited by: Vinoth Babu on Dec 9, 2010 2:05 AMMaybe this helps, there are some system requirements before you can use whole server migration
- WSM uses a floating IP address, for each migratable server. This means that the migratable server candidate machines have to be in the same subnet
(because the virtual IP address must be valid on all candidate machines).
- WSM requires the use of the node manager. You must make sure the node manager on each candidate machine is properly initialized with the security-related
files it need to authenticate and accept commands from the admin server.
- WSM uses the node manager to migrate the floating IP address and assign it to the target machine. As such, the default configuration assumes that the
machines are similar; specifically, it assumes the following:
1 The netmask associated with the virtual IP is the same on all machines.
2 The network device name is the same on all machines.
3 The functional behavior of the platform-specific OS command used to add and remove the virtual IP is the same.
- WSM only supports migration of a single virtual IP address for each migratable server. Therefore, a migratable server cannot define any network channels
that use a Listen Address different from the virtual IP address associated with the server. If you need your servers to use multiple network channels associated
with multiple IP addresses, you cannot use the WSM framework.
- WSM assumes that any server-specific state is already shared through some highly available sharing mechanism. For example, the server’s default persistent store
where it keeps its XA transaction logs must be accessible on all candidate machines using the exact same path.
The configuration steps are as follows:
- Create your domain. Make sure that you set up each managed server's to Listen Address to its virtual IP address and assign it to a machine.
- Set up the node manager for each candidate machine. For each machine, edit the nodemanager.properties file to set the NetMask property to the netmask
associated with the virtual IP addresses being used and Interface to the network device name with which to associate the virtual IP address.
- Verify the domain and node manager configuration. Start up the domain and each clustered managed server via its node manager. This not only ensures that the
node managers and servers are properly configured but also initializes the node managers with the password files they need to accept commands from the admin server.
Do not forget to start managed servers on all candidate machines to ensure that the node manager and domain directory are properly initialized.
- Choose and configure your leasing mechanism. Like automatic service migration, automatic whole server migration relies on leasing. Use the cluster's Migration Configuration
tab to select the appropriate Migration Basis.
- If you choose database leasing, be sure to create and configure your nontransactional data source, create the leasing table, and use the cluster's Migration Configuration tab
to set the Data Source for Automatic Migration and Auto Migration Table Name appropriately.
- Grant superuser privileges to the wlsifconfig script. Node managers use the ${WL_HOME}/common/bin/wlsifconfig.sh script to add and remove virtual IP addresses from the
machines. By default, the file is set up to use sudo; sudo typically prompts you for your password the first time you run it and periodically after that. To do this without needing
to input your password, you need to add the NOPASSWD option to the relevant entry in your /etc/sudoers file. Do not forget to add the wlsifconfig script to your PATH so that
the node managers can locate it. (weblogic machine1 = NOPASSWD: /wlserver_10.3/common/bin/wlsifconfig.sh)
- Enable automatic server migration. The last step is to use each managed server's Migration Configuration tab to select the Automatic Server Migration Enabled checkbox
and restart the servers.
Debugging problems with whole server migration can be tricky so you will probably want to add -Dweblogic.debug.DebugServerMigration=true to the Java command line
used to start your servers. -
BW Steps before and after R3 server migration
Hi Friends,
We are using ECC6 and BW 3.5.
My client is going for R3 server migration, yes it's just a migration of server and not any upgrade. This server is quite old so migrating to a higher end server.
BASIS will do a system copy during downtime i.e. a homogeneous client copy where they would just copy the DB tables. As per them all data will remain same and only the IP will change i.e. i will have to make a change in R3-BW RFC connection.
I need to know what other pre and post migration steps are involved in this case?
Thanks,
BJHi,
I dont think that there would be any impact on queues etc due to server migration. We flush out data from queues only in cases of upgrade/ patch application etc. because there is a chance that after the upgrade the structure of datasource may change. In that case, any data lying in queue beforehand would get corrupted and cannot be loaded.
in your case, there is no such change going to happen, therefore no need to worry about queues. You can go ahead without worrying about any dataloss due to queues. -
Calendar Server Migration from iplanet5.2 to Sunjava messaging server
Hi
Can any one help me on Calendar server migration.
How can i migrate the calendar server from iplanet 5.2 to sunjava messaging server
Users
Calendar resources
Groups
AttributesHi,
I assume you mean iplanet calendar server 5.1.1 to the latest calendar server (6.3). If so, I suggest you start by reading through the calendar server admin guide which goes through the steps involved and tools to use to migrate from 5.1.1 onto calendar server 6.3.
http://www.sun.com/bigadmin/hubs/comms/library/manuals.calendar.jsp
Regards,
Shane. -
I'm having a problem setfing up migration on my Managed Servers on Welbogic 9.2 mp2. First, My problem.
When I try to manually migrate ManagedServer1 from MachineA to MachineB:
Nodemanger shutdowns ManagedServer1
Nodemanager removes the interface with the floating IP (so far so good)
(here is where the problem starts)
Nodemanager brings up the interface back on MachineA
Nodemanager starts ManagesServer1 on MachineA (all this is suppose to happen on MachineB).
This doesn't help me if it migrates it to the same machine!!!
I quick overview of how things are set up.
1) I have two machines, MachineA and MachineB running Solaris 10
2) I have the admin server running on MachineA listening on the static ip of 139 and ManagedServer1 listening on the floating IP of 169 (fyi, don't want give out IP, so I made a number up)
3) I have ManagedServer2 running on MachineB with the floating IP of 170.
4) I created a weblogic user that has ssh trust config between the two machines and has the proper authority to create and bring down an interface.
5) Created 2 Unix machines, Type SSH with the shell command ssh -l legalint -o PasswordAuthentication=no -p %P %H /opt/bea/weblogic92/common/bin/wlscontrol.sh -d %D -n /legalint/mtdom/ndmgr -c -f startManagedWebLogic.sh -s %S %C
6) Network Time Protocal Config is set
7) Lease database schema is created with corresponding data source and has two tables ACTIVE and ACTIVE_MT
8) Server migration progerties configured: cluster datasource is set (In my directions it tells me to leave the Canidate machines blank). Managed servers auto migration set to true and primary and back-up machine set and auto-restart set to true.
Any help is appreciated.
Tom.The best way to deal with certificates and FQDN's in ZESM is to use commercial issued certificates or from the company's internal CA. Don't use the built-in product self-signed certificates under any reason for production deployments. The reason behind that, is that the internal ZESM certificate has its private key marked as non-exportable. So you'll not be able to export it from one server and move to another.
For the server FQDN, create an A or Alias record in DNS to something like: "zesm.company.com", and point it to the actual ZESM server, that way, once you need to move all users from server, all that you need to do is to import the commercial certificate and point the DNS record to the new server IP Address.
I did a couple of deployments in that way, with no issues.
Hope this helps.
>>>
From: mauro vaccari<[email protected]>
To:novell.support.zenworks.endpoint-security-management
Date: 1/19/2010 7:36 AM
Subject: Server Migration
Hi,
planning the upgrade to the imminent release of ZESM 4.1 we would like
to reinstall the server because it has undergone many installations.
For security reason and for don't stop production we want to install
ZESM 4.1 in a new server with the same ip and name of the actual then we
want try It in a test VLAN.
My question is:
when we want to pass the new server in production or before ZESM
instalation could we migrate the IIS certificate from the old server to
new one? so the client should not be involved.
Thank you for help
mauro_vaccari
mauro_vaccari's Profile: http://forums.novell.com/member.php?userid=16902
View this thread: http://forums.novell.com/showthread.php?t=398639 -
File server migration with Offline files involved
Hi,
We are planning a file server migration in following weeks.
This morning, our customer came with the good old "Ow, and I just thought about something else"
Here's the scenario :
-They are using 1 network drive
-That network drive is made offline available for all laptop users
-Those users are spread out in several country's. No VPN connection
-They are working for months on their offline network drive, right in the middle of the wood, no internet connection, it was already short for them to find power supply for their laptop ...
...nevermind
-The day they come back to the office, the file server to which points the network drives will be offline.
Now the 1 Million question : What happens with their "dirty" files ?
yep exactly. those they changed 6 months ago, have no clue about if you ask them but certainly will the day I will clear the damn cache.
My first analysis :
-The new file server will have another name, no alias or re-using the old name is possible (the customer don't want to)
-I can't tell to those laptops "hey for that offline cache, please use this new network drive"
So :
>> Those users have to identify manually files they changed while being offline, copy them locally on their machine and work that way the time they come back to the main office.
>> When they finally show up, clear the cache, offline the new network drive and replace file copied locally
>> If no internet connexion available in the branch office, let them work locally, it's still better than this hybrid-non-sense 6month offline folder "solution". If internet connexion is mainly available remotely, propose some Citrix/View/RDS
Setup which is, for me, a more professional looking solution
Someone has another (better?) idea/solution ?Hi,
I suggest you ask users to collect their laptop to internet, then start offline files synchronization on the old file server. After that, use
Robocopy to copy the date from the old server to the new server. As the offline files cache cannot be recognized by the new file server, so we need to synchronize data first.
If the older server cannot be enabled, as you mentioned, you might need to ask users to copy their changed files to the new file servers.
Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
Hi All,
I m installing SOA suite in high availability environment (cluster) and I want to understand why I do need to configure Server Migration for SOA and OSB managed servers, what will happened if one of the managed serves fails and I didn't migrate it to the node? Does this affect the running BPEL instance by any mean? And how the users will be affected?
Any helpful answers will be appreciated
Regrads,
Ahmed SaberThank you Robert for your reply.
I still want to understand what will happen for the BPEL process and oracle service bus if server migration is not configured and one of the node get down.
I understood from the link you sent that there are some singleton services that can only run on one node that's fine but I still want to understand from the business point of view how this might affect BPEL process and oracle service bus?
Regards,
Ahmed -
Bam Server migration - need info
Hi All,
SOA 11.1.1.7
I have a question regarding bam server migration. As BAM Server is singleton, I just want to confirm if my understanding is correct.
Example
- bam_server1 & bam_server2 in BAM_CLUSTER.
- bam_server1 is configured to be singleton.
Scenario 1 - All 2 Server is up and running in BAM_CLUSTER.
Request1 goes to bam_server1 which gets processed
Request2 goes to bam_server2 which internally routes to bam_server1(which is hosting the singleton service)
Scenario 2 - bam_server1(singleton) is killed, only bam_server2 is running
Request 1 goes to bam_server2 which holds the request as there is no singleton service available.
Request 2 goes to bam_server2 which is also held without getting processed.
bam_Server1(singleton) is migrated to new machine and restarted.
all the request waiting on bam_server2 is routed to bam_server1 which processes the request.
Am i right in saying the request going to bam_server2 will be held and not lost while bam_server1(singleton) is migrated completely.?
Thanks in advance.
/SRHi All,
SOA 11.1.1.7
I have a question regarding bam server migration. As BAM Server is singleton, I just want to confirm if my understanding is correct.
Example
- bam_server1 & bam_server2 in BAM_CLUSTER.
- bam_server1 is configured to be singleton.
Scenario 1 - All 2 Server is up and running in BAM_CLUSTER.
Request1 goes to bam_server1 which gets processed
Request2 goes to bam_server2 which internally routes to bam_server1(which is hosting the singleton service)
Scenario 2 - bam_server1(singleton) is killed, only bam_server2 is running
Request 1 goes to bam_server2 which holds the request as there is no singleton service available.
Request 2 goes to bam_server2 which is also held without getting processed.
bam_Server1(singleton) is migrated to new machine and restarted.
all the request waiting on bam_server2 is routed to bam_server1 which processes the request.
Am i right in saying the request going to bam_server2 will be held and not lost while bam_server1(singleton) is migrated completely.?
Thanks in advance.
/SR -
File Server Migration Source and Target Data Validation
Does anyone know of a power shell script/CLI command or some other way to verify source and target data after a file server migration? I want to make sure that the shares that are migrated from the source and target are an exact match. Thank
you.Hi,
An example is provided in this article:
http://blogs.technet.com/b/heyscriptingguy/archive/2011/10/08/easily-compare-two-folders-by-using-powershell.aspx
$fso = Get-ChildItem -Recurse -path C:\fso
$fsoBU = Get-ChildItem -Recurse -path C:\fso_BackUp
Compare-Object -ReferenceObject $fso -DifferenceObject $fsoBU
And actually Robocopy could also do this job with /L and /log:file parameter.
If you have any feedback on our support, please send to [email protected] -
How to disable the Directory listing for the whole server or a particular a
Please let me know how to disable the Directory listing for the whole server or a particular application.
Thank YouI want to disable the tab focusing( tab index) for a JTextField objectsLook through the API and find methods with the word "focus" in the method name.
Also can u tell me about how to change the tab index orders for JTextFields."How to Use the Focus Sub System":
http://java.sun.com/docs/books/tutorial/uiswing/misc/focus.html -
Source system server migration (new ip address)
Hi Experts
We are moving our servers (source systems) to new boxes. The source systems will be copied to the new ones and the only thing changing will be the IP addresses. BW server will not be touched.
Do I need to create new source systems? I am hoping not to do this and, Are the deltas will be ok? Or do I need to reinitialize all the delta loads?
Thanks!
DanielHi Daniel
No need to create new source system...In fact without deleting the existing one, you wont be able to create same source again.
And do not delete , because that means you will lose all the DataSource.
Need to adjust RFC to point to different hostname /IP address.
In case any inconsistency happens , need to restore the source system connection from BW side.
RSA1-->Source System--->Resotre ...this will automatically adjust RFC connection. Search Forum to know the process of restore in detail if needed.
Delta might need to be re-initialized. Are you planning to clear all the queue before ( LBWQ) server migration? Else you might end in some problems during migration if you are doing it by database restore method.
Regards
Anindya
Edited by: Anindya Bose on Feb 10, 2012 6:38 AM -
I'm trying to migrate a Windows 2003 SP2 (R1) to Server 2012 Essentials. It won't allow migration until the Server Migration Tool is run on the old server. However, it stops at the beginning of the process with an error that the DFS Replication
service is not running. But as far as I know, the DFS Replication service did not exist until Server 2003 R2. How can I get around this?
Thanks for any help.
Ron Volkman
Aurora Technology SolutionsThe SourceTool log file looks like this:
01/06/2013 22:14:22 Failed to get the value of the key OperatingSystemSKU. Error: System.Management.ManagementException: Not found
at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.PropertyData.RefreshPropertyInfo()
at System.Management.PropertyDataCollection.get_Item(String propertyName)
at Microsoft.WindowsServerSolutions.SmallBusinessServer.Tools.MigrationPrep.Wizard.TaskPrerequisiteProvider.GetProperty(ManagementBaseObject obj, String keyName).
01/06/2013 22:14:22 Current Server type: Windows2003
01/06/2013 22:14:22 Failed to get the value of the key OperatingSystemSKU. Error: System.Management.ManagementException: Not found
at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.PropertyData.RefreshPropertyInfo()
at System.Management.PropertyDataCollection.get_Item(String propertyName)
at Microsoft.WindowsServerSolutions.SmallBusinessServer.Tools.MigrationPrep.Wizard.TaskPrerequisiteProvider.GetProperty(ManagementBaseObject obj, String keyName).
01/06/2013 22:14:22 Current Server type: Windows2003
01/06/2013 22:14:22 Failed to get the value of the key OperatingSystemSKU. Error: System.Management.ManagementException: Not found
at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.PropertyData.RefreshPropertyInfo()
at System.Management.PropertyDataCollection.get_Item(String propertyName)
at Microsoft.WindowsServerSolutions.SmallBusinessServer.Tools.MigrationPrep.Wizard.TaskPrerequisiteProvider.GetProperty(ManagementBaseObject obj, String keyName).
01/06/2013 22:14:22 Current Server type: Windows2003
01/06/2013 22:14:22 Failed to get the value of the key OperatingSystemSKU. Error: System.Management.ManagementException: Not found
at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.PropertyData.RefreshPropertyInfo()
at System.Management.PropertyDataCollection.get_Item(String propertyName)
at Microsoft.WindowsServerSolutions.SmallBusinessServer.Tools.MigrationPrep.Wizard.TaskPrerequisiteProvider.GetProperty(ManagementBaseObject obj, String keyName).
01/06/2013 22:14:22 Current Server type: Windows2003
01/06/2013 22:14:27 Starting task Raise the functional level of the domain and forest
01/06/2013 22:14:27 Starting Task: Raising domain and forrest functional level.
01/06/2013 22:14:27 Domain name is: DC=asg,DC=local
01/06/2013 22:14:27 current domain functional level is: 2
01/06/2013 22:14:27 No need to change.
01/06/2013 22:14:27 current forrest functional level is: 2
01/06/2013 22:14:27 No need to change.
01/06/2013 22:14:27 Task finished successfully
01/06/2013 22:14:27 Starting health scan using MBCA engine..
01/06/2013 22:14:33 Health scan: MBCA model has been imported.
01/06/2013 22:14:35 Health scan: SBSMigrationPrep model is in the mbca model list.
01/06/2013 22:14:35 Health scan: Invoking SBSMigrationPrep model at 01/06/2013 22:14:35
01/06/2013 22:14:46 Health scan: invoke result: True
01/06/2013 22:14:46 Health scan: scan end time: 01/06/2013 22:14:46, duration: 00:00:11.5937500
01/06/2013 22:14:47 Health scan: 1 issues found.
01/06/2013 22:14:47 1: id=1, title=DFS Replication Service is not running, description=DFS Replication Service is not running on this server. By default, this service is running and startup type is set to
Automatic., severity=Error
01/06/2013 22:14:47 1 error(s) and 0 warning(s) found during BPA scan
01/06/2013 22:14:55 Writing migration ready flag to False
01/06/2013 22:14:55 Writing time stamp to registry
01/06/2013 22:14:55 Writing Errors and warnings count to registry
Maybe you are looking for
-
How to create a document folder using ListData.svc
Hi All, I've recently been put on a project where I need to use the REST services (ListData.svc) to retrieve and add documents to the document library. It all has been smooth sailing until I hit the point where I want to save a document in a path tha
-
Touble with TV out from my Ipod Touch
Here's the deal. I am out of the states for a while, and I only get three english channels. So I bought some shows on itunes and I bought the A/V cable so i can watch them on my tv in my apartment. The only problem is, they start playing and about 30
-
BUG OJVM does not work with tag files
Hello, A. 1. Create tag file 2. Create JSP that uses tag file <x:xy /> 3. Deploy to OC4J 10.1.3.2. 4. Start OC4J. 4. Access JSP - OK. B. 1. Create tag file 2. Create JSP that uses tag file <x:xy /> 3. Deploy to OC4J 10.1.3.2. 4. Start OC4J with OJVM.
-
PDF form in mac and macbook pro
Hello, Are there any known issues opening and filling a PDF form created in Windows 7 on a MAC or Macbook Pro? I occasionally get users who cannot open the form. Not sure of the exact OS they are using but they have advised they have updated to the l
-
Webapp - where to store user files?
Hi All, My app is packaged in a WAR file, which gets expanded by servlet container during deployment. The app operates with folders containing user data (files uploaded by users, email templates, etc). Where should I create these user data folders -