Information on how to migrate JBoss to WebLogic

Hello all,
I just wanted to know whether there is a link you could provide me with a link or guidelines in which I could find how to migrate my application in JBoss to WebLogic. I have been reading in the forum but I haven't found it.
If not a tutorial like this exists, which should be changed?
Thanks a lot

I'm sorry you feel like the forums have not been helpful. One thing to keep in mind is that forums are all volunteer-only. There are no SLA's or people that have a dedicated job to respond to forum posts like you will find with Oracle Support Service Requests. Therefore the best way to benefit from the forums is to ask succinct clear questions with an appropriate subject line that shows you have done some research, but still need a little help. In addition to the forums, I put together a blog post that tried to assemble many of the WebLogic Server resources available:
http://blogs.oracle.com/jamesbayer/2008/12/weblogic_server_resources_my_c.html
One of the resources I also did not mention is your local Oracle account team. My day-job is to work with local customers as a sales consultant, so I am often asked by the customers I work with to help research questions or help guide them to the right process. I suggest that you contact your local Oracle account team that might be able to help you navigate the many resources available.
One last point, since the forums are community driven, they will only benefit when people give back and contribute back to the forums. So since you were able to find information about the JBoss migration, please respond with where you found the information and what you found helpful about it and help improve the forums for others.
Cheers,
James

Similar Messages

Migrating from BEA WebLogic 5.1 (Windows 2000) to iAS9

Hi!
I am looking for a step-by-step guide for migrating from BEA WebLogic 5.1 (Windows 2000) to iAS9. The guide should contain the detailed information on how to migrate servlets and EJBs.
Some of my questions are:
- What do I have to do when I have system startup files from WebLogic? Are there equivalent properties for iAS9?
# Register a startup class by giving it a virtual name and
# supplying its full pathname.
#weblogic.system.startupClass.[virtual_name]=[full_pathname]
# Add arguments for the startup class
#weblogic.system.startupArgs.[virtual_name]={argname]=[argvalue]
- How do I set the system properties?
Phuoc
null

This a response to the specific point of startup/shutdown classes, a whole Migration paper is underway
Since Servlet 2.2 and EJB containers in 9i AS run within the middle tier database instance,
the easier way to accompish what you want is to declare those classes as database startup/shutdown triggers (Java stored procedures).
You can also set session properties using the "modifyprops" command (cf Java Tools Reference)

How to migrate thunderbird email from pc to mac version

I have been unsuccessful in locating proper information on how to migrate a windows version of TB to the MAC version. Seems to be no clear cut way to do that.
Any suggestions?

Install TB on the Mac, but don't bother installing any accounts. Close TB. Overwrite its new empty profile with one copied from your Windows installation.
Speaking as someone who has successfully moved TB profiles between Windows and Linux, I can warn you that there may be some Windows-specific pathnames in your profile that will need to be fixed. Some add-ons are poorly behaved in that they store absolute pathnames, which do not work when transferred from one computer to another of the same kind, let alone when transferred between operating systems. If your profile has been tweaked to store its data on a separate drive, for instance, you'll need to adjust the path stored in ''profiles.ini''. either by direct hand-editing, or by use of the profile manager.
Profiles:
https://support.mozilla.org/en-US/kb/profiles-tb
http://kb.mozillazine.org/Profile_Manager

HT201250 How to migrate backup disk to new computer using mountain lion?

The page says it provides information about how to migrate a backup disk to a new mac, but it's not there. Does anyone know how to do this in Mountain Lion? When I simply chose the old disk on the new computer, it created an entirely new backup folder and was going to back up everything, not just add to the existing backups. The computer name, login name, and login password are not changed. It's just a new machine . Both old and new machines are mid-2011 iMacs. Thanks!

If it's a new machine, then Time Machine will make a new backup. This is how Time Machine works. A new computer always results in a new backup.
But your question seems to ask about how to use Migration Assistant to transfer your Time Machine backup to the new machine. Am I misunderstanding your question?
In any event: Please visit Pondini's Time Machine FAQ for help with all things Time Machine.

Error in deploying entity beans - migration from JBoss to Weblogic 10.3.4

Hi,
I am migrating EJB2.x code from JBoss to Weblogic 10.3.4. As a first step, I am tyring to deploy just Entity beans. I get following error when deploying to server.
'weblogic.application.ModuleException: Exception preparing module: EJBModule(myEJB.jar)
Unable to deploy EJB: CollMetaData from myEJB.jar:
[EJB:011017]Error while reading 'META-INF/weblogic-cmp-rdbms-jar.xml'. The error was:
There are 1 nested errors:
java.lang.NullPointerException
     at weblogic.ejb.container.cmp.rdbms.finders.EjbqlFinder.setMethods(EjbqlFinder.java:288)
     at weblogic.ejb.container.cmp.rdbms.Deployer.processFinders(Deployer.java:744)
     at weblogic.ejb.container.cmp.rdbms.Deployer.readTypeSpecificData(Deployer.java:446)
     at weblogic.ejb.container.persistence.PersistenceType.setTypeSpecificFile(PersistenceType.java:506)
     at weblogic.ejb.container.persistence.PersistenceType.setupDeployer(PersistenceType.java:455)
     at weblogic.ejb.container.deployer.CMPInfoImpl.setup(CMPInfoImpl.java:118)
     at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1214)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:442)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184)
     at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
Can someone help me fixing the issue?
I changed schema locations of descriptor files as suggested at http://download.oracle.com/docs/cd/E17904_01/web.1111/e13706/overview.htm#i1074199 (see the third category for '*Enterprise Bean 2.1*' in the listing Table 1-1). Alternatively, you may see the schema locations for EJB2.0 directly at http://download.oracle.com/docs/cd/E17904_01/web.1111/e13719/dd_reference.htm#EJBPG481

JRE version in JBoss is 1.6.0_16. JVM in web logic is pointing to jrockit_160_22_D1.1.1-3 which is come in the package. It doesn't seem to be related to JVM version mismatch.
I think it is an issue with definitions in weblogic-cmp-rdbms-jar.xml file. How should be the definition of entity-descriptor appear for entity bean which has finder methods in ejb-jar.xml?
Please see the snippets from corresponding descriptor files below.
ejb-jar.xml
=========
<entity>
<display-name>EmpBean</display-name>
<ejb-name>EmpBean</ejb-name>
<local-home>LocalEmpBeanHome</local-home>
<local>LocalEmpBean</local>
<ejb-class>EmpBeanBean</ejb-class>
<persistence-type>Container</persistence-type>
<prim-key-class>java.lang.String</prim-key-class>
<reentrant>False</reentrant>
<cmp-version>2.x</cmp-version>
<abstract-schema-name>EmpBean</abstract-schema-name>
<cmp-field>
<field-name>firstName</field-name>
</cmp-field>
<cmp-field>
<field-name>lastName</field-name>
</cmp-field>
<cmp-field>
<field-name>phone</field-name>
</cmp-field>
<cmp-field>
<field-name>address</field-name>
</cmp-field>
<primkey-field>lastName</primkey-field>
<query>
<query-method>
          <method-name>findByPrimaryKey</method-name>
               <method-params>
               <method-param>java.lang.String</method-param>
               </method-params>
          </query-method>
          <ejb-ql>SELECT Object(o) FROM EmpBean o WHERE o.lastName= ?1</ejb-ql>
     </query>
</entity>
weblogic-jar.xml
============
<weblogic-enterprise-bean>
<ejb-name>EmpBean</ejb-name>
<entity-descriptor>
     <pool>
          <max-beans-in-free-pool>20</max-beans-in-free-pool>
          <initial-beans-in-free-pool>5</initial-beans-in-free-pool>
     </pool>
<persistence>
<persistence-use>
<type-identifier>WebLogic_CMP_RDBMS</type-identifier>
<type-version>6.0</type-version>
<type-storage>meta-inf/weblogic-cmp-rdbms-jar.xml</type-storage>
</persistence-use>
<finders-load-bean>true</finders-load-bean>
</persistence>
</entity-descriptor>
<local-jndi-name>ejb/EmpBean</local-jndi-name>
</weblogic-enterprise-bean>
weblogic-cmp-rdbms-jar.xml
====================
<weblogic-rdbms-bean>
<ejb-name>EmpBean</ejb-name>
<data-source-jndi-name>mysqlDS</data-source-jndi-name>
<table-map>
<table-name>emp</table-name>
<field-map>
<cmp-field>firstName</cmp-field>
<dbms-column>first_namel</dbms-column>
</field-map>
<field-map>
<cmp-field>lastName</cmp-field>
<dbms-column>last_name</dbms-column>
</field-map>
<field-map>
<cmp-field>phone</cmp-field>
<dbms-column>phone</dbms-column>
</field-map>
<field-map>
<cmp-field>address</cmp-field>
<dbms-column>address</dbms-column>
</field-map>
</table-map>
<weblogic-rdbms-bean>
Please ignore any typos that you may notice in above sample descriptions (because I just typed it here changing original names).
When I try to deploy the application, I get error message as posted in my first post above in this thread. Please correct me if I am making any erros in descriptor files.
Edited by: 839281 on Feb 25, 2011 10:55 AM
Edited by: venkatp on Mar 1, 2011 9:31 AM

Urgent: JBOSS to Weblogic OIM applicaiton migration

Hello,
We've OIM 9102 BP15 on JBOSS non-clustered environment. There are customizations over the OIM UI to meet specific business requirement.
Now, we're planning to migrate the OIM application from JBOSS to Weblogic clustered environment (keeping OIM database intact). OIM documents says it supports weblogic release 10.3.0, 10.3.1 and later.
http://download.oracle.com/docs/cd/E14899_01/doc.9102/e14764/toc.htm#insertedID2
What should be the plan of migrating to WLS 11g application server keeping the OIM DB intact? Any document or metalink?
Thanks,
Edited by: oimuser007 on Sep 21, 2011 11:38 AM

Hello Experts,
One problem i see now is -
Few custom JSP are doing DB calls to show some data on the pages (see code snippet below):
============================================
import javax.naming.*;
Context ctx = null;
ctx = new InitialContext();
DataSource DriverManager = (DataSource)ctx.lookup("java:jdbc/xlDS");
conn = DriverManager.getConnection();
stmt = conn.prepareStatement(SQL);
rs = stmt.executeQuery();
while (rs.next()) {
=============================================
Now, in the new environment, an error message is showing instead of real data.
"While trying to look up /jdbc/xlDS in /app/webapp/xlWebApp/378768760".
When i check through Weblogic console for: services -> Data sources -> xlDS. Everything looks good here.
Any clue what is going wrong ?
Thanks,

How to migrate .war archived webservice to WebLogic 10.0.3

Hi everyone.
I have been requested to deploy a War file as Webservice on Weblogic Server 10.0.3 (installed on Redhat EL 5.0, I used Sun jdk 1.0.6 distributed along with installer bin file). This file
was run well on TOMCAT 5.0.28 server.When hacking into this WAR file I know it use Xfire(1.2.2) as a base to construct Webservice, hibernate(3.0) to mapping with database (it use only a
services.xml putting on META_INF to describe service as far as I know). Firstly, I use Adminstration Console, go to deployment link and deploy as this tool say, the result in Adminstration
Console tell me I had deployed succedfully but when I digged into exploded directory of WAR file, I can not see any .class file under WEB_INF directory and my client actually can not access provided services. I thought there is problem when use Application Console to deploy so I switch to use other tool like wlst or ant task but result is the same. Finally, I had to upload WAR file, use jar to extract WAR file to a directory and use Adminstration Console to deploy the whole directory as a Web Application. All class file are under WEB_INF directory. But when I use a client to access services I got exception as below on WebBrowser
Could not invoke service.. Nested exception is org.codehaus.xfire.fault.XFireFault: Fault: java.lang.NullPointerException
and no more detail (or I do not known where to get log file). Because I am just a system maintainer and do not know much a bout J2EE Webservice specification, I just read some materials
and know that WebLogic support Web Services 2.1 (JAX-WS) and XML-Based RPC 1.1 (JAX-RPC). So I desire to know some thing below:
1) What kind of Webservice in WAR file do I have (Web Services 2.1 (JAX-WS) and XML-Based RPC 1.1 (JAX-RPC) or something WebLogic do not support?
2) How to migrate my WAR file to Weblogic by a very common way?
3) How to get log to make more detail about exception above on WebLogic (does log4j archive this work?) ?
Thank you so much
Edited by: user10407314 on Oct 30, 2008 1:41 AM

Hi all,
May be I found the problem. The compatibility between Weblogic and hibernate 3.0 relating to antlr-2.7.5H3.jar library. Although I include all application's jar file in CLASSPATH when start server
but Weblogic seem not to see my antlr-2.7.5H3.jar and use its default antlr library instead. So I set my antlr-2.7.5H3.jar directly into PRE_CLASSPATH variable on $DOMAIN_HOME/lib/setDomainEnv.sh
file like below:
PRE_CLASSPATH="$DOMAIN_HOME/lib/antlr-2.7.5H3.jar"
export PRE_CLASSPATH
By now my application use the desired lib and Webservice work fine.
But I wonder if this is a good solution, is there any other good practice to set CLASSPATH for this situation? setting PRE_CLASSPATH is correct point and having no affection to the whole domain
in the case there are more application reside in the domain?
Thank all.
Edited by: user10407314 on Oct 30, 2008 9:56 PM
Edited by: user10407314 on Oct 30, 2008 9:57 PM

I'm using migration assistant to transfer files from my wife old net book to new mac air and the pc dropped out during transfer. Pc now says waiting for mac to connect and has is stuck at transferring information. How do I get the process to continue?

I'm using migration assistant to transfer files from my wife old net book to new mac air and the pc dropped out during transfer. I started up migration assistant on the Pc again and now says waiting for mac to connect! New MacBook Air is stuck at transferring information. How do I get the process to reconnect and continue?

Whew, good luck!
What version of OSX is on the older one?

Migrate EJB 3.0 from JBoss to Weblogic 10.3.5

Hi all,
I need help in deploying my ear file from Jboss to Weblogic, got this error relates to EJB module:
####<Dec 26, 2012 10:45:03 PM PST> <Warning> <Deployer> <localhost.localdomain> <AdminServer> <[ACTIVE] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1356590703830> <BEA-149004> <Failures were detected while initiating deploy task for application 'MyScheduler'.>
####<Dec 26, 2012 10:45:03 PM PST> <Error> <Console> <localhost.localdomain> <AdminServer> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <tungpl> <> <> <1356590703869> <BEA-240003> <Console encountered the following error weblogic.application.ModuleException: Could not setup environment
     at weblogic.servlet.internal.WebAppModule.activateContexts(WebAppModule.java:1495)
     at weblogic.servlet.internal.WebAppModule.activate(WebAppModule.java:438)
     at weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:375)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.flow.ModuleStateDriver.activate(ModuleStateDriver.java:95)
     at weblogic.application.internal.flow.ScopedModuleDriver.activate(ScopedModuleDriver.java:194)
     at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:541)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:175)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:167)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
     at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
     at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused by: javax.naming.NameNotFoundException: While trying to look up ejb-info in /app/ejb/myEjb.jar#myEjb.; remaining name 'ejb-info'
     at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
     at weblogic.jndi.internal.ApplicationNamingNode.lookup(ApplicationNamingNode.java:144)
     at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
     at weblogic.deployment.BaseEnvironmentBuilder.autowireEJBRef(BaseEnvironmentBuilder.java:408)
     at weblogic.deployment.EnvironmentBuilder.addEJBReferences(EnvironmentBuilder.java:513)
     at weblogic.servlet.internal.CompEnv.activate(CompEnv.java:157)
     at weblogic.servlet.internal.WebAppServletContext.activate(WebAppServletContext.java:3144)
     at weblogic.servlet.internal.WebAppModule.activateContexts(WebAppModule.java:1493)
>
I have tried some solution in this thread https://kr.forums.oracle.com/forums/thread.jspa?threadID=2174802 but it doesn't help at all.
Could sb give me any idea?
Pretty thanks!
Edited by: user12925202 on Jan 20, 2013 11:33 PM

Frank,
Thanks. The @LOB annotations are missing.
Create table with:
CREATE TABLE TestBlob (id number PRIMARY KEY, xmlCol BLOB);
INSERT INTO TestBlob VALUES(1, EMPTY_BLOB());
The following is the complete listing for the EJB 3 class generated from table TestBlob.
package ejb3;
import java.io.Serializable;
import javax.persistence.Column;
import javax.persistence.Entity;
import javax.persistence.Id;
import javax.persistence.NamedQueries;
import javax.persistence.NamedQuery;
@Entity
@NamedQueries({
@NamedQuery(name = "Testblob.findAll", query = "select o from Testblob o")
public class Testblob implements Serializable {
@Id
@Column(nullable = false)
private Long id;
private byte[] xmlCol;
public Testblob() {
public Testblob(Long id) {
this.id = id;
public Long getId() {
return id;
public void setId(Long id) {
this.id = id;
public byte[] getXmlCol() {
return xmlCol;
public void setXmlCol(byte[] xmlCol) {
this.xmlCol = xmlCol;
}

How to install TopLink_CMP_2_0 for Weblogic 10.3.4 (11g Release 1)

Hi
I am trying to migrate EJB2.x code from JBoss to Weblogic 10.3.4.
The entity bean description in my weblogic-ejb.jar looks like below.
<weblogic-enterprise-bean>
<ejb-name>UserProfile</ejb-name>
<entity-descriptor>
<persistence>
<persistence-use>
<type-identifier>WebLogic_CMP_RDBMS</type-identifier>
<type-version>7.0</type-version>
<type-storage>META-INF/weblogic-cmp-rdbms-jar.xml</type-storage>
</persistence-use>
</persistence>
</entity-descriptor>
<local-jndi-name>ejb/LocalUserProfile</local-jndi-name>
</weblogic-enterprise-bean>
I get error Error while reading 'META-INF/weblogic-cmp-rdbms-jar.xml' when deploying to server as I posted in another thread at Error in deploying entity beans - migration from JBoss to Weblogic 10.3.4
The information on the page http://download.oracle.com/docs/cd/B25221_05/web.1013/b13593/depcr008.htm tells that the supported persistent type for EJB2.0 is TopLink_CMP_2_0.
When I modify above entity description accordingly, the deployment throws exception that "*TopLink_CMP_2_0*" is not installed.
Can someone suggest me how to install the persistent type? Also please let me know if my approach to migration is correct.

See if these help:
http://java2go.blogspot.com/2008/01/jaxb-10-vs-20-in-jdeveloper-10g.html
http://biemond.blogspot.com/2008/02/jaxb-20-in-jdeveloper-10g-and-11g.html

How to implement JAAS With Weblogic 10.3

I am working on a migration project. A project is to be migrated from JBOSS to Weblogic 10.3. JAAS has been used in JBOSS for security purpose.
Required classess like LoginModule, CallBackHandler are customized and put into a jar file. Next a Login page has been created with action=”j_security_check”, which is supposed to be called whenever protected resource has been requested. In web.xml Roles and Policies are defined. There is a jboss-web.xml in which roles are mentioned. In web.xml
There is a login-config.xml that has been put into Jboss server classpath. In this file, some sql queries are there.
In weblogic I am not able to understand that how to configure this login-config, how to map roles and policies. Exactly I am not able to find what are the steps needed to implement this JAAS in weblogic10.3. I also tried using the Read-Only SQL Authenticator Provider under security Realms but not sure how to use groups, because I have no Group related tables in my DB.
Kindly anyone share the knowledge.

Hi,
I also want to do the same thing. Did you get any solution for this problem. If yes then please share it with me. I am struggling with this.
Thanks,
Sanjay

How to find out Integrated weblogic server version

hi experts,
am using jdev11.1.1.5.0
i h'd big doubt ;)
how to find out Integrated weblogic server version
i think am using weblogic10.1.3. but am not sure?
so how can i found out.
this my log. but i dont see any info about version.
*** Using port 7101 ***
"C:\Documents and Settings\Administrator\Application Data\JDeveloper\system11.1.1.5.37.60.13\DefaultDomain\bin\startWebLogic.cmd"
[waiting for the server to complete its initialization...]
JAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m
WLS Start Mode=Development
CLASSPATH=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jdbc_11.1.1\ojdbc6dms.jar;C:\Oracle\MIDDLE~1\patch_wls1035\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\JDK160~1\lib\tools.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.jar;C:\Oracle\MIDDLE~1\modules\features\weblogic.server.modules_10.3.5.0.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\webservices.jar;C:\Oracle\MIDDLE~1\modules\ORGAPA~1.1/lib/ant-all.jar;C:\Oracle\MIDDLE~1\modules\NETSFA~1.0_1/lib/ant-contrib.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrf.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\common\derby\lib\derbyclient.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\xqrl.jar
PATH=C:\Oracle\MIDDLE~1\patch_wls1035\profiles\default\native;C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\native;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\native\win\32;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\bin;C:\Oracle\MIDDLE~1\modules\ORGAPA~1.1\bin;C:\Oracle\MIDDLE~1\JDK160~1\jre\bin;C:\Oracle\MIDDLE~1\JDK160~1\bin;C:\DevSuiteHome_1\jdk\jre\bin\classic;C:\DevSuiteHome_1\jdk\jre\bin;C:\DevSuiteHome_1\jdk\jre\bin\client;C:\DevSuiteHome_1\jlib;C:\DevSuiteHome_1\bin;C:\DevSuiteHome_1\jre\1.4.2\bin\client;C:\DevSuiteHome_1\jre\1.4.2\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\native\win\32\oci920_8
* 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_24"
Java(TM) SE Runtime Environment (build 1.6.0_24-b50)
Java HotSpot(TM) Client VM (build 19.1-b02, mixed mode)
Starting WLS with line:
C:\Oracle\MIDDLE~1\JDK160~1\bin\java -client   -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m -Dweblogic.Name=DefaultServer -Djava.security.policy=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Djavax.net.ssl.trustStore=C:\Oracle\Middleware\wlserver_10.3\server\lib\DemoTrust.jks -Duser.timezone="+05:30" -Dweblogic.nodemanager.ServiceEnabled=true -Xverify:none -da -Dplatform.home=C:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Djps.app.credential.overwrite.allowed=true -Dcommon.components.home=C:\Oracle\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=C:\DOCUME~1\ADMINI~1\APPLIC~1\JDEVEL~1\SYSTEM~1.13\DEFAUL~1 -Djrockit.optfile=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=C:\DOCUME~1\ADMINI~1\APPLIC~1\JDEVEL~1\SYSTEM~1.13\DEFAUL~1\config\FMWCON~1\servers\DefaultServer -Doracle.domain.config.dir=C:\DOCUME~1\ADMINI~1\APPLIC~1\JDEVEL~1\SYSTEM~1.13\DEFAUL~1\config\FMWCON~1 -Digf.arisidbeans.carmlloc=C:\DOCUME~1\ADMINI~1\APPLIC~1\JDEVEL~1\SYSTEM~1.13\DEFAUL~1\config\FMWCON~1\carml -Digf.arisidstack.home=C:\DOCUME~1\ADMINI~1\APPLIC~1\JDEVEL~1\SYSTEM~1.13\DEFAUL~1\config\FMWCON~1\arisidprovider -Doracle.security.jps.config=C:\DOCUME~1\ADMINI~1\APPLIC~1\JDEVEL~1\SYSTEM~1.13\DEFAUL~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=C:\DOCUME~1\ADMINI~1\APPLIC~1\JDEVEL~1\SYSTEM~1.13\DEFAUL~1\servers\DefaultServer\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Dwsm.repository.path=C:\DOCUME~1\ADMINI~1\APPLIC~1\JDEVEL~1\SYSTEM~1.13\DEFAUL~1\oracle\store\gmds   -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~1\patch_wls1035\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\sysext_manifest_classpath weblogic.Server
<Feb 17, 2012 5:50:39 AM GMT> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
<Feb 17, 2012 5:50:39 AM GMT> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
<Feb 17, 2012 5:50:39 AM GMT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 19.1-b02 from Sun Microsystems Inc.>
<Feb 17, 2012 5:50:40 AM GMT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 >
<Feb 17, 2012 5:50:42 AM GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Feb 17, 2012 5:50:42 AM GMT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Feb 17, 2012 5:50:42 AM GMT> <Notice> <LoggingService> <BEA-320400> <The log file C:\Documents and Settings\Administrator\Application Data\JDeveloper\system11.1.1.5.37.60.13\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<Feb 17, 2012 5:50:42 AM GMT> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\Documents and Settings\Administrator\Application Data\JDeveloper\system11.1.1.5.37.60.13\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log00220. Log messages will continue to be logged in C:\Documents and Settings\Administrator\Application Data\JDeveloper\system11.1.1.5.37.60.13\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log.>
<Feb 17, 2012 5:50:42 AM GMT> <Notice> <Log Management> <BEA-170019> <The server log file C:\Documents and Settings\Administrator\Application Data\JDeveloper\system11.1.1.5.37.60.13\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log is opened. All server side log events will be written to this file.>
<Feb 17, 2012 5:50:48 AM GMT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Feb 17, 2012 5:50:50 AM GMT> <Notice> <LoggingService> <BEA-320400> <The log file C:\Documents and Settings\Administrator\Application Data\JDeveloper\system11.1.1.5.37.60.13\DefaultDomain\servers\DefaultServer\logs\access.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<Feb 17, 2012 5:50:50 AM GMT> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\Documents and Settings\Administrator\Application Data\JDeveloper\system11.1.1.5.37.60.13\DefaultDomain\servers\DefaultServer\logs\access.log00102. Log messages will continue to be logged in C:\Documents and Settings\Administrator\Application Data\JDeveloper\system11.1.1.5.37.60.13\DefaultDomain\servers\DefaultServer\logs\access.log.>
<Feb 17, 2012 5:50:56 AM GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<Feb 17, 2012 5:50:56 AM GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<MessageLocalizationHelper> <getLocalizedMessage> The resource for bundle "oracle.jrf.i18n.MBeanMessageBundle" with key "oracle.jrf.JRFServiceMBean.checkIfJRFAppliedOnMutipleTargets" cannot be found.
<Feb 17, 2012 5:51:02 AM GMT> <Warning> <J2EE> <BEA-160195> <The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application GeneralLedger is not versioned.>
<Feb 17, 2012 5:51:07 AM GMT> <Warning> <J2EE> <BEA-160195> <The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application Rapppdf is not versioned.>
<Feb 17, 2012 5:51:27 AM GMT> <Notice> <LoggingService> <BEA-320400> <The log file C:\Documents and Settings\Administrator\Application Data\JDeveloper\system11.1.1.5.37.60.13\DefaultDomain\servers\DefaultServer\logs\DefaultDomain.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<Feb 17, 2012 5:51:27 AM GMT> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\Documents and Settings\Administrator\Application Data\JDeveloper\system11.1.1.5.37.60.13\DefaultDomain\servers\DefaultServer\logs\DefaultDomain.log00208. Log messages will continue to be logged in C:\Documents and Settings\Administrator\Application Data\JDeveloper\system11.1.1.5.37.60.13\DefaultDomain\servers\DefaultServer\logs\DefaultDomain.log.>
<Feb 17, 2012 5:51:27 AM GMT> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
<Feb 17, 2012 5:51:27 AM GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Feb 17, 2012 5:51:27 AM GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<Feb 17, 2012 5:51:27 AM GMT> <Warning> <Server> <BEA-002611> <Hostname "rmsys0061", maps to multiple IP addresses: 192.168.0.161, 192.168.2.161>
<Feb 17, 2012 5:51:27 AM GMT> <Notice> <Server> <BEA-002613> <Channel "Default[2]" is now listening on 127.0.0.1:7101 for protocols iiop, t3, ldap, snmp, http.>
<Feb 17, 2012 5:51:27 AM GMT> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on 192.168.2.161:7101 for protocols iiop, t3, ldap, snmp, http.>
<Feb 17, 2012 5:51:27 AM GMT> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 192.168.0.161:7101 for protocols iiop, t3, ldap, snmp, http.>
<Feb 17, 2012 5:51:27 AM GMT> <Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server "DefaultServer" for domain "DefaultDomain" running in Development Mode>
<Feb 17, 2012 5:51:27 AM GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<Feb 17, 2012 5:51:27 AM GMT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
IntegratedWebLogicServer startup time: 51640 ms.
IntegratedWebLogicServer started.
[Running application frmtesting on Server Instance IntegratedWebLogicServer...]
[11:21:30 AM] ---- Deployment started. ----
[11:21:30 AM] Target platform is (Weblogic 10.3).
[11:21:31 AM] Retrieving existing application information
[11:21:31 AM] Running dependency analysis...
[11:21:31 AM] Deploying 2 profiles...
[11:21:32 AM] Wrote Web Application Module to C:\Documents and Settings\Administrator\Application Data\JDeveloper\system11.1.1.5.37.60.13\o.j2ee\drs\frmtesting\ViewControllerWebApp.war
[11:21:32 AM] Wrote Enterprise Application Module to C:\Documents and Settings\Administrator\Application Data\JDeveloper\system11.1.1.5.37.60.13\o.j2ee\drs\frmtesting
[11:21:32 AM] Deploying Application...
<Feb 17, 2012 5:51:33 AM GMT> <Warning> <J2EE> <BEA-160195> <The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application frmtesting is not versioned.>
[11:21:40 AM] Application Deployed Successfully.
[11:21:40 AM] The following URL context root(s) were defined and can be used as a starting point to test your application:
[11:21:40 AM] http://192.168.0.161:7101/frmtesting-ViewController-context-root
[11:21:40 AM] Elapsed time for deployment: 11 seconds
[11:21:40 AM] ---- Deployment finished. ----
Run startup time: 10812 ms.
[Application frmtesting deployed to Server Instance IntegratedWebLogicServer]
Target URL -- http://127.0.0.1:7101/frmtesting-ViewController-context-root/faces/untitled6.jspxhttp://127.0.0.1:7101/console/login/LoginForm.jsp. it stated as weblogicserver 11g admin console
At the botton(copy right section) 10.3.5.0

Hi,
There is one more method,i know
Set the JAVA_HOME and PATH
then execute the
$WL_HOME\wlserver_10.3\server\bin>setWLSEnv.cmd
Go to directory which contains weblogic.jar ($WL_HOME\server\lib) and run below command
$WL_HOME\wlserver_10.3\server\lib>java -cp weblogic.jar weblogic.version
WebLogic Server 10.3.4.0 Fri Dec 17 20:47:33 PST 2010 1384255
Hope this will be helpful,
Regards
Fabian

How to migrate ADE content to a new computer

At some point, everybody needs to upgrade to a new computer.
After reading a great many postings in this forum, it seems obvious to me that many of us would greatly benefit from some specific guidance on how to install Adobe Digital Editions and Sony Reader Library Software (and reader device) or some other e-book application on the new computer, and then move the previously purchased e-book content from the old to new computer in a way that will ensure that the e-books can still be read.
Specifically, I think that some/better guidance needs to be provided on the sequence of steps that must be taken, and the options that should (or should not) be selected to accomplish these actions. For example, does ADE software get installed on the new PC first, or after installing the Sony reader library (or other reader) software? Should we authorize the new computer? How about the portable reader devices (Sony P600), do we leave the content on these or will we need to reload it? Is there a way to ensure the Adobe ID for both SW applications (ADE & Sony Library) are the same so we don't get new or different ID assigned? Will a reader device (which may already contain ebook content) be recognized and automatically resynch with the new computer? and can it move its content from reader to PC, or must the purchased content first be loaded onto the new PC from the old PC, and then be moved (again) to the reader device?
I can't help but think that answers to these (and many other) questions could be far more easily communicated by proactively publishing some basic (if general) procedures for accomplishing common actions like these, rather than repeatedly providing help to each of us after we have already done the wrong thing. While technical help is always greatly appreciated, and it may be easier to address a specific problem, it is more effective to provide information that will help us avoid the problem in the first place, and thus reduce the case load and improve response time.
If I were sufficiently knowledgable to be capable of providing this general guidance myself, I would certainly do so, but count me among the ignorant masses that are simply trying to buy, download, and read their e-books without rendering all their purchased content inaccesible. I certainly wouldn't want to inadvertently provide misinformation that might cause even greater problems.
In short, I think that all of us (forum readers) would greatly like to have some simple instructions presented on what to do, (or not to do), to initially set up our computers and to accomplish other basic functions once this has been done.
Won't somebody with the needed expertise undertake to provide some instructions in this forum?
Thanks (in advance) for you support.
P.S. - Keeping purchased content on original (old) and new computers is NOT an option.

How to migrate ADE from one computer to another:
1.) Ensure that your current content is authorized to an AdobeID
In ADE select "Authorize Computer" from the "Library" menu if it shows you your AdobeID you are good to go.
2.) Copy files - the files are the .epub and .pdf files in your Digital Editions folder in your Documents directory. Alternatively you can simply copy the whole Digital Editions folder. If you copy the whole folder make sure you place it into your Documents directory.
Note: on Windows the folder names are "My Digital Editions" and "My Documents"
3.) Install ADE on the new computer, make sure you enter in the AdobeID from step 1 and the password when asked
The AdobeID that registred and shown (in step1) above is the same for ADE as it is for Sony EBL (the Sony desktop software) - they both pull from the same place.
Unfortunately I don't know the steps for migrating Sony EBL.
For the content on the reader device, you can leave them alone.

How to Migrate Oracle Forms 10g 9.0.4 to 10.1.2

Hi I would like to find information on what is necessary to do in order to migrate Forms 10g 9.0.4 to 10.1.2.
Do I need to use Oracle Migration assistant ?
Is it enough only compile forms ?
Where I find documentation on how to execute this migration. I am only find documentatio to migrate from 6i to 10g, but I need documentation to migrate from Forms 10g 9.0.4 to 10.1.2.

Hi,
Thank you for the answer about Oracle forms.
Now I would like ask another question but this time for Oracle Application Server. As we have Oracle forms 10g 9.0.4 we also use the Application Server with this same version.
Do you have any recommendations on how to Migrate the Oracle Application Server from 10g 9.0.4 to 10.1.2 ?
Thank you .

How to migrate the Objects from 3.1c to BI7

Hi,
We are in Functional Upgradation.
How to Migrate the Objects( Infocubes,DSO,Datasources,Rules...etc...) from 3.1C to BI 7.0
Please help me to doing this....
regards,
anil

BW Upgrade tasks (BW 3.1C to BI 7.0)
Prepare Phase:
Task     How-To     Who
Review BI 7.0 feature lists     Review BI 7.0 feature lists for possible inclusion in developments.     Basis/BW
Obtain the BI 7.0 upgrade guide     Download the upgrade guide from http://service.sap.com/inst-guides -> SAP NetWeaver -> Upgrade
     Basis/BW
Review all upgrade SAP notes     In addition to the upgrade guide, check, download, and review all SAP notes for your upgrade
     BI 7.0 Upgrade notes
     SAP Web Application Server 6.40 upgrade notes
     OS and DB specific upgrade notes
     SAP BW Add-on upgrade notes
(e.g. SAP SEM, ST-PI, etc)
     Plug-In upgrade SAP notes
     Other notes identified in above notes and/or upgrade guides.
     Basis/BW
Check DB and OS requirements for the target SAP BW release     Check DB version/patch level and OS version/patch level required for upgrade
     First check the most current information from the SAP BW homepage http://Service.sap.com/BW -> <SAP BW release> -> Availability
     Additionally, the u201CPlatformsu201D link will take you to the main DB/OS page for BI 7.0 and SAP Web AS 6.40.
     Note: In some cases there are differing requirements for SAP BW 3.0B/SAP BW 3.1 Content and BI 7.0
     Basis
Check SAP BW Add-on upgrade requirements     Do you have SAP BW add-ons installed that require additional handling (e.g. SAP SEM, Enterprise Portal Plug-in, etc)?
     SAP SEM (SAP BW based components) requires SAP SEM 4.0 which is part of the mySAP ERP 2004 suite.
     WP-PI release must be at 6.00 before the upgrade begins. As mentioned before this add-on is merged with PI_Basis after the upgrade.
     Basis
Check SAP BW upgrade requirements          Minimum Support Package and kernel levels for upgrade
     SAP BW Frontend requirements for new SAPGUI, SAP BW BEx Frontend and SAP BW Web applications.
     Source system Plug-In requirements     Basis
Check compatibility requirements with 3rd party software          3rd Party Reporting tools (example: Crystal)
     ETL Tools (example: Ascential, DataStage, etc)
     Scheduling tools (example. Control-M, Maestro, etc)
     Monitoring tools (example: HP OpenView, Patrol, etc)
     Other OS or DB related tools     Basis
Check new component requirements for BI 7.0          If SAP BW web reports were developed in SAP BW 2.x, a windows version of IGS 6.40 (Internet Graphics Service) is required for conversion and future rendering of web graphics (i.e. Charts and GIS Maps).
The IGS chart migration will also be required after the SAP BW web report conversion.
     If you used or activated any SAP BW Web Applications in SAP BW 3.x, or if you have used charts in SAP BW 2.x web reports, you will need a windows version of IGS 6.40 (Internet Graphics Service) to execute the IGS chart migration after the upgrade.
     If ESRI GIS software is in use, a different version of ESRI software maybe required for BI 7.0. (ArcView 8.2?).
     If you plan to use Information Broadcasting, please review the requirement for additional infrastructure components such as EP, KMC, Workbook pre-calculation service, and Web AS connectivity to your mail servers.
Detailed information is available in the SAP NetWeaver u201904 master planning guide (http://service.sap.com/instguides -> SAP NetWeaver).
     Basis
Test and distribute new SAP BW Frontend
          Install and test the new BI 7.0 Frontend (including the new version of SAPGUI for Windows if applicable).
     A detailed FAQ on the new BI 7.0 Frontend is available on the SAP service marketplace alias BWFAQ (http://service.sap.com/BWFAQ).
     After successful testing, the new SAPGUI for Windows and SAP BW Frontend can be distributed to the BW teams and end users.
     Basis
Alpha Conversion:
Ensure that your InfoObject data is consistent from a u201Cconversionu201D perspective (Alpha Converter tool)      Check that you have executed the Alpha Converter tool to check the consistency of your InfoObject definitions and data for InfoObjects that utilize the ALPHA, NUMCV and GJAHR conversion exits.
Note: The Alpha conversion is not part of the SAP BW upgrade itself, but the upgrade simply checks to ensure you have successfully executed the check tool.
Transaction RSMDCNVEXIT
Check the system status:
     u201CAll Characteristics Have Correct Internal Valuesu201D: The Alpha converter has been successful executed. The upgrade preparation can continue.
     u201CNo Check yet/Inconsistent Internal Vales existu201D:
The Alpha converter check has not been executed.
     u201CCharacteristics have Inconsistent Internal Valuesu201D:
The Alpha converter tool check has been executed and data problems have been detected. The InfoObject and data must be processed before the upgrade can be started.
     BW
Upgrade SAP Note updates     Check for newer versions of your SAP notes for the Upgrade.
Tip: The SAP service marketplace offers an option to subscribe to OSS notes so you can be notified of changes when you log on.
     Basis/BW
Confirm SAP BW support package, kernel and DB/OS configuration     Analyze current Support Package and DB/OS/Kernel configurations in your SAP BW landscape in relation to the SAP BW 3.x upgrade requirements.
     Apply necessary support packages, kernel patches, and DB and OS patches to meet upgrade requirements
     Basis
Alignment of SAP BW objects within your SAP BW system landscape     Check and, where required, re-align SAP BW Objects and developments in your SAP BW system landscape (Development, Quality Assurance and Production).
SAP BW Object differences can impact the quality of testing in the Development and Test environment and can lead to change management issues.
     This check is to minimize risk and ensure productive objects are being tested prior to the Production upgrade.
Where alignment issues exist and realignment is not possible, alternative testing plans should be devised.
     Basis/BW
Confirm all developments are deployed.     Ensure that all SAP BW developments are deployed or they are to be re-developed/tested after the upgrade.
     In the DEV system, all SAP BW development transports should be released (i.e. transport created and released) and imported to all downstream systems (i.e. QAS and PRD systems).
For SAP BW developments not already collected in the transport collector, a decision must be made:
Deploy the developments or wait until the upgrade has completed to deploy.
o     Development to be deployed should be collected, released, and imported into the QAS and PRD systems.
o     Developments that should be deployed after the upgrade should be re-tested/re-developed after the upgrade.
     In the QAS or PRD systems, ensure that all SAP BW development transports have been imported prior to the upgrade.
     BW
Implement BI 7.0 Business Explorer Frontend     Install, evaluate, test and distribute the new BI 7.0 Business Explorer Frontend.
     Basis/BW
Pre-upgrade Process:
Download required BI 7.0 support package Stack for inclusion in the upgrade     Determine the equivalent support package level of the source SAP BW release and the target SAP BW release.
     There is a minimum requirement that you upgrade to at least the equivalent support package level on the target SAP BW release so that you do not lose functionality, corrections, and data.
     It is recommended to upgrade to the latest version of all support packages during the upgrade via the upgradeu2019s support package binding functionality.
     BI 7.0 Support Packages are delivered via SAP NetWeaver u201904 Support Package stacks (SP-Stacks). It is not recommended to partially apply some of the SP-Stacksu2019 individual support packages. You should apply all of the SP-Stacks support packages at once.
For more information on the SP-Stacks and SAP NetWeaver SP-Stacks, please see the SAP service marketplace alias SP-Stacks (http://service.sap.com/sp-stacks)
     You should also review, download, and bind in support packages for all add-on components that are installed on SAP BW and will be upgraded during the SAP BW upgrade (e.g. SEM-BW, ST-PI, etc)
     Basis
Apply latest Support Package tool patch     Apply latest SPAM patch before executing PREPARE     Basis
Validate the SAP BW (ABAP) Data Dictionary and the Database Data Dictionary for consistency     Check Database consistency
     Transaction DB02:
o     Execute ABAP SAP_UPDATE_DBDIFF and re-execute DB02 check. This gives a truer view of the SAP BW objects in DB02.
o     Check missing database objects (indices, tables, etc)
o     Missing indices may identify erred data loads or process problems
Tip: Missing indices on InfoCubes can be restored by RSRV or ABAP SAP_INFOCUBE_INDEXES_REPAIR
Note: check for running data loads before executing a repair!
o     Check DDIC/DB consistency
     Verify database objects and consistency
(e.g. SAPDBA check for offline data files)
     BW
Remove unnecessary SAP BW temporary database objects     Delete all SAP BW temporary database objects:
     Execute routine housekeeping ABAP SAP_DROP_TMPTABLES.
     This reduces the numbers of database objects that need to be copied during the upgrade.
     Note: take care not to delete objects that are in use as this will cause queries, compressions, etc to terminate.
     BW
Validate your SAP BW Objects for correctness prior to your upgrade     Using the SAP BW Analysis Tool (transaction RSRV), perform extensive tests on all important SAP BW Objects to ensure their correctness prior to the upgrade.
Note: this test should be repeatable so you can re-validate after the upgrade!
     Ensure that any inconsistencies are identified and corrected
     RSRV has a number of extensive tests and if all checks are executed will consume a large amount of time. Multiple tests can be performed in parallel.
     Tip: Some corrections in development can be deployed to other systems via transport in advance of the next upgrade.
     BW
Ensure DB Statistics are up to date prior to the upgrade          Check DB statistics for all tables.
Tables without statistics, especially system tables, can seriously impact upgrade runtimes.
     Check DB statistics for missing Indexes for InfoCubes and Aggregates
o     User transaction RSRV to check      BW
Check SAP BW Support Package status     Check the status of all support packages (via transaction SPAM)
     Ensure the Support Package queue is empty
     Confirm all applied Support Packages     Basis
Check all u2018Repairsu2019     Check for unreleased repair transports
     Release all unreleased transports
In your QAS and PRD system, check if all repair transports have been imported (i.e. systems are aligned)
     Import missing repair transports into down stream systems. This will avoid differing message and/or errors during the upgrade.
     BW
Check InfoObject status          Check for revised (modified) InfoObjects that have not been activated.
All InfoObjects should be active or saved (not activate):
o     Check all inactive InfoObjects:
Transaction RSD1 (Edit InfoObjects),
click on u201CAll InfoObjectsu201D radio button and click the u201CDisplayu201D button.
Modified InfoObjects are denoted by yellow triangles!
o     Determine if revision should be activated or removed.
     'Reorgu2019 or u2018Repairu2019 all InfoObjects
This checks and repairs any discrepancies in the InfoObject definition and structures. It is common to have obsolete DDIC and table entries for InfoObjects after multiple upgrades and definition changes. These obsolete entries normally do not effect normal SAP BW operations.
     Transaction RSD1 (Edit InfoObjects), Select u201CExecute Repairu201D or u201CExecute Reorgu201D Use expert mode for selective executions.
     BW
All ODS data loads must be activated.          Activate all inactivated ODS Object requests.
All ODS u2018Mu2019 tables must be emptied prior to the upgrade as a new activate process is implemented
o     Inactivated ODS request can be located via the Admin workbench -> u2018Monitoringu201D button -> u2018ODS Status Overviewu201D
     BW
All Transfer and Update rules should be active          Check for inactive Update and Transfer Rules
o     All update rules and transfer rules should be active or deleted.
o     Look into the table RSUPDINFO for update rules and search for the version "not equal" to "A". Likewise use the table RSTS for Transfer rules/structure.     BW
All InfoCubes should be active          Check for inactive InfoCubes and Aggregates (Aggregates are InfoCubes too!)
o     All InfoCubes should be activated or deleted.
o     Execute ABAP RSUPGRCHECK to locate any inactive InfoCubes. See SAP note 449160.
     BW
All Web Report objects should be consistent prior the upgrade.          Check the consistency of your SAP BW web objects (web reports, web templates, URLs, roles, etc). All objects should be consistent prior to web object conversion after the upgrade. It is recommended to ensure consistency before the upgrade.
o     For Original release SAP BW 3.x:
A SAP BW web reporting objects check can be executed via a new check in RSRV. This is provided via a SAP BW support package.
Please see SAP note 484519 for details.
     BW
Backup your system before starting PREPARE     Before execution PREPARE, perform a full database backup (including File system). Ensure you can recover to the point in time before PREPARE was executed.
     Database admin
Address any instructions/errors generated by PREPARE          Address any issues listed in log files Checks. Log generated by PREPARE.
o     Repeat PREPARE until all checks are successful.     Basis
Complete any Logistic V3 data extractions and suspend V3 collection processes          Extract and empty Logistics V3 extractor queues on SAP R/3 source systems.
o     The V3 extraction delta queues must be emptied prior to the upgrade to avoid any possible data loss. V3 collector jobs should be suspended for the duration of the upgrade.
They can be rescheduled after re-activation of the source systems upon completion of the upgrade.
     Note: If you perform any data loads after executing PREPARE, re-check the status of all delta queues in SAP BW and the source systems(s).
     BW
Complete any data mart data extractions and suspend any data mart extractors          Load and Empty all Data mart Delta Queues in SAP BW. (e.g. for all export DataSources)
o     The SAP BW Service SAPI, which is used for internal and u2018BW to BWu2019 data mart extraction, is upgraded during the SAP BW upgrade. Therefore, the delta queues must be emptied prior to the upgrade to avoid any possibility of data loss.
     Note: If you perform any data loads after executing PREPARE, re-check the status of all delta queues in SAP BW and the source systems(s).
     BW
Check that your customer defined data class definitions conform to SAP standards          Check all customer created Data classes used by SAP BW Objects (i.e. InfoCubes, ODS Objects, Aggregates, InfoObjects, and PSAs) to ensure they conform to SAP standards.
o     Check your data class definitions as detailed in SAP Notes 46272 and 500252.
o     Incorrect data classes could create activation errors during the upgrade.
     BW
Remove unnecessary SAP BW temporary database objects     Delete all SAP BW temporary database objects:
     Execute routine housekeeping ABAP SAP_DROP_TMPTABLES.
For more information see SAP note 308533 (2.x) and 449891 (3.x).
     This reduces the numbers of database objects that need to be copied during the upgrade.
     Note: take care not to delete objects that are in use as this will cause queries, compressions, etc to terminate.
     Basis/BW
Backups!     Before executing the upgrade, ensure that you have a backup strategy in place so you can return to the point where loading was completed and the upgrade started.
Ensuring you can return to a consistent point in time (without having to handle rollback or repeats of data loads) is key to having a successful fallback plan.
     Database Admin
Before Execution:
All SAP BW administration tasks should have ceased          Cease all SAP BW administration tasks such as Object maintenance, query/web template maintenance, data loads, transports, etc at the beginning of the upgrade.
The Administrators Workbench and the Data Dictionary are locked in the early phases of the upgrade.
     Reminder: Users can execute queries until the time that the upgrade determines that the SAP BW System should be closed*
- timing depends on the type of upgrade selected
     Basis/Admin
Remove unnecessary SAP BW temporary database objects     Repeat the deletion of all SAP BW temporary database objects after you have stopped using the SAP BW Admin workbench*
     Execute routine housekeeping ABAP SAP_DROP_TMPTABLES.
For more information see SAP note 308533 (2.x) and 449891 (3.x).
- timing depends on the type of upgrade selected
     BW
Check system parameters     Check OS, DB, and Instance profile parameters.
     Check System Instance parameters for new BI 7.0 specific parameters. See SAP note 192658 for details
     Check for any DB specific parameters for BI 7.0
     Check for any new OS parameters     Basis
Check Database archiving mode     Turn database archive log mode back on if it was disabled during the upgrade!
     Database Admin
After Execution:
Check the systemu2019s installation consistency     Execute Transaction SICK to check installation consistency
     BW
Check the system logs     Perform a technical systems check.
     Example: Check system and all dispatcher logs (inc. ICM logs)
     Basis
Apply latest executable binaries     Apply the latest 6.40 Basis Kernel for all executables
     Tip: use the SAP NetWeaver u201904 SP-Stack selection tool to find all binaries. (http://service.sap.com/swdc)
     Basis
Review BI 7.0 Support Packages for follow-up actions.          Review SAP Notes for all SAP BW Support packages applied during (bound into the upgrade) and applied after the upgrade:
o      Search for Note with the keyword u201CBWu201D, u201CSAPBWNEWSu201D, and u201C<BW release>u201D
o     Follow any required instructions identified in the SAP Notes
     Basis
Apply latest patches          Apply the latest SPAM patch
     Apply any required support packages that were not bound into the upgrade.
     Basis
Apply additional BI 7.0 Support Packages
(if required)          SAP recommends that customer remain current on SAP Support Packages.
     Review SAP Notes for all SAP BW Support packages applied in previous task.
o      Search for Notes with the keyword u201CBWu201D, u201CSAPBWNEWSu201D, and u201C<BW release>u201D
o     Follow any required instructions identified in the SAP Notes
     Basis
Resolve any modified SAP delivered Role issues      If SAP delivered Roles were modified, then these modifications may incorrectly appear in the upgrade modification adjustment tool (SPAU).
     Review and implement SAP note 569128 as required     Basis
Configuring Information Broadcasting EP/KMC Connections
     If you plan to use the EP integration functionality of Information broadcasting (Broadcast to the EPu2019s PCD, Broadcast to KMC, or Broadcast to Collaboration Rooms):
     Ensure the SAP EP is at the same SP-Stack level as your SAP BW system.
     Follow the online help documentation to configure and connect the SAP BW system and the SAP EP system. (http://help.sap.com).
     For broadcasting to KMC, ensure that KM has the u2018BEx Portfoliou2019 content available.
     Basis
Re-check SAP BW Object and consistency     Execute RSRV to check SAP BW Object consistency
     Repeat tests that we executed prior to the upgrade.
     Validate results      BW
Check InfoCube views for consistency     Check consistency of InfoCube fact table views
     It is possible that fact table view /BIC/V<InfoCube>F is missing if a number of SAP BW upgrades have been performed before. See SAP Note 525988 for instructions for the check and repair program.
     BW
Perform SAP BW Plug-in (SAPI) upgrade follow-up tasks          If required, Re-activate the SAP BW u201CMyselfu201D source system in SAP BW.
     The SAP BW internal plug-in (SAPI), which is used for internal data mart extraction and u2018BW to BWu2019 communication, is upgraded during the SAP BW upgrade. The source system is de-activated to prevent extractions and loading during the upgrade.
     It may be required to replicate export DataSources and reactivate transfer structures/rules for internal data loads (i.e. ODS Object to InfoCube objects).
o     Tip: It is advised to do this step for all export DataSources to avoid possible errors during execution of InfoPackages
     Check that all other Source Systems are active.
o     Activate as required.     Basis/BW
Check SAP BW Personalization is implemented     (SAP BW 2.X upgrades will have performed this in the previous task).
Validate that personalization has been activated in your SAP BW system.
Note: It has been observed that in some cases, BEx Personalization has to be re-activated after an upgrade from SAP BW 3.x to BI 7.0. It is advised to check the status of personalization after the upgrade.
     Enter the IMG (transaction SPRO), select SAP Business Warehouse -> Reporting relevant settings -> General Reporting Settings -> Activate Personalization in BEx
Check the status of the Personalization settings. All entries should be active u2013 highlighted by an unchecked check box.
     To activate highlighted Personalization, click Execute.     BW
For SAP BW 2.0B/2.1C -> BI 7.0 Upgrades:
Convert ODS secondary indexes to new standard     For SAP BW 2.0B/2.1C -> BI 7.0 Upgrades:
Convert any customer created ODS Object secondary indexes to the new ODS Object index maintenance process.
     Re-create all indexes in the ODS Object definition screen in transaction RSA1.
     ODS indexes must conform to the new naming convention
     BW
Converting IGS chart settings
     Convert you existing IGS chart settings (converts IGS chart settings from BLOB to new XML storage format)
     Ensure you have the latest SAP Web AS 6.40 IGS (stand alone windows version) installed and working
o      Test via transaction RSRT
     Execute the conversion process as directed the BI 7.0 upgrade guide.
     Note: This step is required for all BI 7.0 upgrades     Basis
Backup your SAP BW system     Perform a full database backup (including the File system)
Remember to adjust your backup scripts to include new components such as the J2EE engine, pre-calculation service, etc.
     Database Admin

Information on how to migrate JBoss to WebLogic

Similar Messages

Maybe you are looking for