Migrating BW-BPS to 2004s
We are planning to upgrade from BW 3.5 to NW 2004s. Our main concern is with the BW-BPS object migration. Per my understanding, there are two provisions BW-BPS and BI-IP - for planning in 2004s (both can run in parallel!!).
http://help.sap.com/saphelp_nw04s/helpdata/en/44/05829c6ef7025be10000000a1553f7/content.htm
Is there any support strategy for BW-BPS vs BI-IP from SAP; like BI-IP will be supported in future upgrades whereas BW-BPS will be terminated?
Also it looks like if one prefers to go with BI-IP, only certain BW-BPS objects can be migrated to BI-IP and requires new development for other objects. I have looked at the following link and it is confusing.
http://help.sap.com/saphelp_nw04s/helpdata/en/44/059baf6ef7025be10000000a1553f7/content.htm
My specific questions include:
1. If we decide to stick with BW-BPS in 2004s, then we do not need any new development after the upgrade to continue operating the way we were. Is this a correct statement?
2. If we choose to go with BI-IP, the link says Objects that you created in the planning workbench (transaction BPS0) for BW-BPS must be migrated to the new objects in the planning modeler. Once any necessary remodeling is complete, you have to create the objects as new objects in the planning modeler. You can use the old objects as templates. Does it mean that all the objects created using BPS0 transaction have to be re-created in the planning modeler of BI-IP? Why does it say You can use the old objects as templates.? Some one who have migrated from BW-BPS to BI-IP, please comment.
3. Looks like the whole authorization concept has changed, how smooth is the migration of authorizations from BW 3.5 to NW 2004s?
4. We use SEM_BPS_NO_LOCK. Is this supported in NW 2004s?
5. Whats your take on BW-BPS vs BI-IP in 2004s? Which one is recommended and how smooth is the transition to BI-IP provided we have 3 basic planning areas and 2 multi-planning areas with 100 planning levels? Please comment.
All the helpful information will be rewarded. Please also provide me with the links/documents where I can learn more about the migration from BW-BPS to BI-IP.
Hi Sean,
Here are some thoughts on your questions below:
A) you should be able to go directly from 3.2 (BW 3.1) directly to 6.0 (NW04s BI). An intermediate step is not necessary.
b) not sure exactly what you are suggesting with this. If you mean stop using SEM-BPS and use BW-BPS this can't really be done. Once you've installed SEM on your BW box it's there forever. Therefore you'd have to upgrade to SEM 6.0. I believe the only way you could avoid SEM 6.0 is a fresh install of BW. (not sure if I'm understanding your question correctly)
c) This option would allow you to enhance the frontend experience for the end users and allow you to leverage the BW frontend components (queries, structures, variables, etc.) in planning. The drawbacks are that there isn't currently a migration tool so you'll have to do some rework to get there. In addition if you're using some of the SEM only functions (allocations, etc.) thost functions don't yet exist in IP so they'd have to still be executed via SEM-BPS or rebuilt in fox.
Similar Messages
-
Migrate reports to netweaver 2004s automatiquely
Hi guys !
Is there any program to migrate BW3.5 Queries and Workbooks to Netweaver 2004s automatiquely, I mean without opening them one by one and save them on the new Bex Analyser.
Thanks for your helpUnfortunately no - as of now. Has to be a manual way.
-
hi,
Recently we migrated BW 3.5 to BI 7.0 can we migrate that BPS objects to IP . what are the steps to migrate BPS to IP.
please help me,
Thanks,
Jhon.Hi Sam,
In addition to above:
http://help.sap.com/saphelp_nw70/helpdata/EN/44/05829c6ef7025be10000000a1553f7/frameset.htm
Regards,
Priyanka
Edited by: Priyanka Turlapaty on Apr 3, 2008 7:07 AM -
Formula variable in 2004s displays '?No/Value'
Hi,
I have created a formula variable to display characteristic value in a query. it works fine in 3.5 version but when i migrated this query in 2004s. It displays "?No/Value" in report. I tried to look at couple of settings but i didnt find anything. Is there any setting i missed out in 2004s?
Thanks
Abhijit<FONT FACE = "Tahoma", Font Color = "Blue">
My Dear Friend<br>
<u>Please try the below code:</u><br><br>
Case vnam.<br>
When 'Z_OPT1'.<br>
check i_step = 2.<br>
<br>
read table I_T_VAR_RANGE INTO loc_var_range with key vnam = 'Z_OPTSEL'.<br>
<br>
if sy-subrc = 0.<br>
Clear l_s_range.<br>
if loc_var_range-low = '1'. <br>
l_s_range-low = '2'.<br>
endif.<br>
if loc_var_range-low = '2'.<br>
l_s_range-low = '0'.<br>
endif.<br>
endif.<br>
l_s_range--sign = 'I'.<br>
l_s_range-opt = 'EQ'.<br>
APPEND l_s_range TO e_t_range.<br>
endcase.<br>
<br><br>
Hope it helps.<br><br>
Cheers Abhijit<br>
</FONT><FONT FACE = "Verdana", Font Color = "Red">
Removed
</FONT> -
Web Template Migration Error in Chart
Hi All,
I have a 3x web template 'TEST_3X'
It is derived from the SAP default 3x template 0QUERY_TEMPLATE with no
major changes/customizing. Only a picture and a data provider has been
assigned. It works fine.
Now I tried to migrate 'TEST_3X' to a 2004s template using the Migration tool.
Before doing this I migrated all items using the report
<b>'RSZW_ITEM_MIGRATION_3X_TO_70'</b>.
At the end of the process there is this error message "Make sure that the
3x library item <b>0ADHOC_COLUMN_CHART</b> is migrated to 2004s via the report.
See note 832712."
However I cross checked the item '0ADHOC_COLUMN_CHART' in table
<b>RSZWBITMHEAD</b> (target table for migration). It exists and is active.
It also exists in table '<b>RSZWITEM</b>' (source table for migration) and is active.
Any suggestions. Am I missing anything?
Thanks
VishnoYes.
See path below.
https://websmp208.sap-ag.de/patches
Entry by Application Group -->
Support Packages and Patches" --> SAP Frontend Components" --> BI ADDON FOR SAP GUI" --> BI 7.0 ADDON FOR SAP GUI 7.10 -
Help with WDScopeUtil in 2004s - Urgent please
Hi,
We are currently migrating our code from 2004 SP16 to 2004s. From the forum, I understood that we have to use WDScopeUtil in 2004s to pass data between pages and WDScopeUtil supports only Strings but We want to pass objects also.
We came up with another approach - Convert object to Bytes array, wrap it in a String object and put them in Session. Here are the methods used for the conversion.
public static String convertHashMapToString(HashMap p) throws Exception {
String errMsg = null;
try {
byte[] bArray = SessionUtils.getBytes(p);
String pAsString = new String(bArray);
} catch (Exception e) {
throw e;
return pAsString;
public static HashMap convertStringToHashMap(byte[] bArray) throws Exception {
HashMap hm = null;
try {
ByteArrayInputStream bis = new ByteArrayInputStream(bArray);
ObjectInputStream ois = new ObjectInputStream(bis);
hm = (HashMap) ois.readObject();
} catch (Exception e) {
throw e;
return hm;
private static byte[] getBytes(Object obj) throws java.io.IOException {
ByteArrayOutputStream bos = new ByteArrayOutputStream();
ObjectOutputStream oos = new ObjectOutputStream(bos);
oos.writeObject(obj);
oos.flush();
oos.close();
bos.close();
byte[] data = bos.toByteArray();
return data;
We have 2 2004s environments (Sandbox and Dev portal). When I first migrated this code to Sandbox, it just works great but when I deployed the code to Dev portal, I am getting the exception "invalid stream header" from convertStringToHashMap method.
I am really confused about how it can work in one environment and not in another. Can there be any difference in lib files in both environments by patch level. Our webadmin says that they have the same set of libs in both environments.
Any help is greatly appreciated.
Thanks,
KalyanI have attached a file below to show that i am just getting noWHERE with this apparent help to sign in. in the second to last picture you will notice it says reset microsoft password. BUT I DONT NEED TO. the very last photo showes that there is a distinct individual option to reset just the skype password and i cannot do that using the code that they have emailed me. i just want to reset my skype account.
PLEASE SOMEONE HELP.
i have been asking help since thrusday.
Attachments:
skype help.pdf 501 KB -
Merge an SEM-BPS System to BW System
Hi,
actual SEM-BSP is installed on an own system and the planning area is linked via a rfc-connection to the BW System. Now we want to update the BW to 3.5 and migrate the BPS System to the BW system.
Can I transport the BPS customizing from the SEM system to the BW system and the change from rfc-connection to an InfoCube? How?
Does anyone have any experience with this.
Thanks in advance,
MatthiasHello Matthias,
well, in general Alberto is right. However, also he says that he has done it several times, he was a bit lucky
There are limitations. SEM-BPS has 10 more planning functions than BW-BPS. If you used any of those 10, then you the application will not work on BW-BPS. You can implement them using FOX or exit functions.
Have you implemented any exits in SEM-BPS? If yes, you will have to transport the ABAP things as well. How about custom tables? There could be conflicts and/or differences between the two systems.
Are the global customizing settings the same on both systems? Exchange rates? Fiscal year variants?
Have you thought about authorizations and roles?
Are you using STS?
That's probably not all... In summary, it's just not as easy as it sounds.
Regards
Marc
SAP NetWeaver RIG
PS: We are working on a consolidated list in the RIG. Please send me any feedback about the merge process. -
Dear experts,
we face the following problem: We want to migrate from BPS to IP, but have trouble with our BPS variables. We have user-defined variables and variables which are centrally maintained (e.g. 2 versions which shall be available for planning). When the user executes an input-ready query, F4-help should be restricted to the centrally maintained values.
I know there are two ways, which are recommended:
.) user-exit variable, which reads information from some table; problem with that, all values, which are read from the table are proposed in the variable screen (shown in the input line); so if you have 10 values, all of them will be preselected; if the user doesn't delete them from the input line all 10 values will be locked on the server; moreover F4-help is not restricted
.) use authorizations; unfortunately we have different authorizations for planning and reporting; e.g. 2 versions for planning, but all for reporting; so in the F4-help we have all values available not just the 2 versions for planning
Does anybody have an idea how to solve this issue?
Best regards
MichaelHello,
Only way to restrict the values in F4 help in IP is via authorization. However, in BW7.3 we would be able to do so using BAdI.
Regards
Deepti -
HI All,
We are planning to migrate from BPS to Integrated Planning. I heard there are many bottlenecks. Can somebody please guide me through , I need help from both from functional and if possible from BASIS point. <Removed>.
regards
sumeth
Edited by: Arun Varadarajan on Feb 6, 2009 12:09 PMHi ,
if you are not the architect who created the previous BPS planning and the project is quite complicate, it 's better to take most of your time to understand deeply how the previous model work. Make a DEEP DEEP work on documentation before to touch anything .
If the project in BPS had also deep use of abap, exits, and whatever, make absolutely sure that in your team you have really SERIOUS abapers and serious bex/vba/java experts.
I have seen projects with over 100 levels and I don't know how many other things and the migration in this case is not a joke.
Even if the model is "easy", make very very sure that the customer will keep going in case of delay to use the previous BPS. This is not a dummy thing. In some cases, to touch and touch some colleagues have "ruined" both systems !!! So for example if they have to make the BDG, let them to make this year with the old system and prepare the new one for next year.
Anyhow, after this I do not see big jobs from the basis team. As other people said, it's matter to almost rebuild everything again using the previous BPS as a guideline and just having the BI (cube and whatever already available). If I have to touch the projects I did myself I usually estimate 40 days of job, this includes also ABAP testing , not less if you want a really tested system and probably 20 of a good bex/vba/java expert.
Kind regards
Walter -
Documentation for new Planning function types in 2004s
Hello,
We are analyzing the impact of migrating former BPS exit planning funtions to the new BI Planning function types. In fact, we are checking the SAP procedure for reusing the BPS exits from BI Planning, although I would like to know if there is some kind of procedure or documentation (I have already read the documentation in Business planning developer guide) for a quick reimplementation in BIP.
Thank you for your help.
Regards.
Message was edited by: Ignacio Arroyo
Message was edited by: Ignacio Arroyo
Message was edited by: Ignacio ArroyoHi
Please check below URL for the BI IP planning function types.
<a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/43/37d8c2af4c1bcbe10000000a1553f7/content.htm">http://help.sap.com/saphelp_nw2004s/helpdata/en/43/37d8c2af4c1bcbe10000000a1553f7/content.htm</a>
Hope it Helps
Chetan
@CP -
WLI 8.1SP2 Cluster over 2 Physical Machines Errs on Managed Svrs on 2nd mac
I set up WLI Clustering 8.1sp2 with 4 total managed servers, 2 colocated with the admin server, and 2 on a vanilla installation of WLP 8.1sp2.
While the colocated servers boot up correctly (and are able to be recovered by the node manager), I cannot seem to get the remote managed servers to come up properly. The node manager on the remote machine reports the following error:
####<Sep 23, 2004 5:49:50 PM EDT> <Notice> <Log Management> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-170019> <The server log file C:\bea\user_projects\domains\myClusterTest08\new_managedServer_3\new_managedServer_3.log is opened. All server side log events will be written to this file.>
####<Sep 23, 2004 5:49:51 PM EDT> <Info> <Socket> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000406> <NTSocketMuxer was built on Jun 19 2003 15:39:24
>
####<Sep 23, 2004 5:49:51 PM EDT> <Info> <Socket> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000436> <Allocating 2 reader threads.>
####<Sep 23, 2004 5:50:05 PM EDT> <Info> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090093> <No pre-WLS 8.1 Keystore providers are configured for server new_managedServer_3 for security realm myrealm.>
####<Sep 23, 2004 5:50:05 PM EDT> <Notice> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090082> <Security initializing using security realm myrealm.>
####<Sep 23, 2004 5:50:06 PM EDT> <Notice> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090170> <Loading the private key stored under the alias DemoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
####<Sep 23, 2004 5:50:07 PM EDT> <Notice> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090171> <Loading the identity certificate stored under the alias DemoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
####<Sep 23, 2004 5:50:07 PM EDT> <Notice> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\bea\weblogic81\server\lib\DemoTrust.jks.>
####<Sep 23, 2004 5:50:07 PM EDT> <Notice> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\bea\jrockit81sp2_141_05\jre\lib\security\cacerts.>
####<Sep 23, 2004 5:50:08 PM EDT> <Notice> <WebLogicServer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000328> <Starting WebLogic Managed Server "new_managedServer_3" for domain "myClusterTest08">
####<Sep 23, 2004 5:50:08 PM EDT> <Info> <WebLogicServer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000214> <WebLogic Server "new_managedServer_3" version:
WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic XMLX Module 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic Integration 8.1 SP2 Thu Dec 11 22:07:14 PST 2003 148883 (c) 1995, 1996, 1997, 1998 WebLogic, Inc.
(c) 1999, 2000, 2001 BEA Systems, Inc.>
####<Sep 23, 2004 5:50:08 PM EDT> <Info> <WebLogicServer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000215> <Loaded License : C:\bea\license.bea>
####<Sep 23, 2004 5:50:08 PM EDT> <Info> <RJVM> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000570> <Network Configuration for Channel "new_managedServer_3"
Listen Address informatica-svr:7001
Public Address N/A
Http Enabled true
Tunneling Enabled false
Outbound Enabled false
Admin Traffic Enabled true>
####<Sep 23, 2004 5:50:08 PM EDT> <Debug> <RJVM> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000571> <Network Configuration Detail for Channel "new_managedServer_3"
Channel Weight 50
Accept Backlog 50
Login Timeout 5000ms
Max Message Size 10000000
Message Timeout 60s
Idle Timeout 65s
Tunneling Timeout 40s
Tunneling Ping 45s>
####<Sep 23, 2004 5:50:08 PM EDT> <Info> <XML> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-130036> <Initializing XMLRegistry.>
####<Sep 23, 2004 5:50:08 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001135> <Initializing the JDBC service.>
####<Sep 23, 2004 5:50:09 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001137> <Initialization complete.>
####<Sep 23, 2004 5:50:09 PM EDT> <Info> <Connector> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-190000> <Initializing J2EE Connector Service>
####<Sep 23, 2004 5:50:09 PM EDT> <Info> <Connector> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-190001> <J2EE Connector Service initialized successfully>
####<Sep 23, 2004 5:50:09 PM EDT> <Info> <IIOP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-002014> <IIOP subsystem enabled.>
####<Sep 23, 2004 5:50:10 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040090> <Deployed 5 default connection factories.>
####<Sep 23, 2004 5:50:10 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040305> <JMS service is initialized and in standby mode.>
####<Sep 23, 2004 5:50:10 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101128> <Initializing HTTP services.>
####<Sep 23, 2004 5:50:10 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101133> <Initializing Web server new_managedServer_3.>
####<Sep 23, 2004 5:50:10 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101052> <[HTTP new_managedServer_3] Initialized>
####<Sep 23, 2004 5:50:10 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101135> <new_managedServer_3 is the default Web server.>
####<Sep 23, 2004 5:50:11 PM EDT> <Info> <J2EE> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-160037> <J2EE service initializing.>
####<Sep 23, 2004 5:50:11 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149207> <Initializing.>
####<Sep 23, 2004 5:50:13 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module uddiexplorer of application uddiexplorer is transitioning from unprepared to prepared on server new_managedServer_3.>
####<Sep 23, 2004 5:50:13 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module uddiexplorer of application uddiexplorer successfully transitioned from unprepared to prepared on server new_managedServer_3.>
####<Sep 23, 2004 5:50:13 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module uddi of application uddi is transitioning from unprepared to prepared on server new_managedServer_3.>
####<Sep 23, 2004 5:50:13 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module uddi of application uddi successfully transitioned from unprepared to prepared on server new_managedServer_3.>
####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module wl_management_internal1 of application wl_management_internal1 is transitioning from unprepared to prepared on server new_managedServer_3.>
####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module wl_management_internal1 of application wl_management_internal1 successfully transitioned from unprepared to prepared on server new_managedServer_3.>
####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module uddiexplorer of application uddiexplorer is transitioning from prepared to active on server new_managedServer_3.>
####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module uddiexplorer of application uddiexplorer successfully transitioned from prepared to active on server new_managedServer_3.>
####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module uddi of application uddi is transitioning from prepared to active on server new_managedServer_3.>
####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module uddi of application uddi successfully transitioned from prepared to active on server new_managedServer_3.>
####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module wl_management_internal1 of application wl_management_internal1 is transitioning from prepared to active on server new_managedServer_3.>
####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module wl_management_internal1 of application wl_management_internal1 successfully transitioned from prepared to active on server new_managedServer_3.>
####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149208> <Initialization Complete.>
####<Sep 23, 2004 5:50:17 PM EDT> <Notice> <Cluster> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000138> <Listening for announcements from cluster new_cluster_1 on 237.0.0.1:7001.>
####<Sep 23, 2004 5:50:17 PM EDT> <Notice> <Cluster> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000133> <Waiting to synchronize with other running members of new_cluster_1.>
####<Sep 23, 2004 5:50:48 PM EDT> <Info> <JTA> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-110441> <Opening transaction log with driver version "j1.0" and synchronous write policy "Cache-Flush". For information on synchronous write policies, refer to the weblogic.management.configuration.ServerMBean javadoc or console online help.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001138> <Resuming the JDBC service.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001140> <Resume complete.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "DefaultXAConnectionFactory" is started.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "QueueConnectionFactory" is started.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "MessageDrivenBeanConnectionFactory" is started.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "DefaultConnectionFactory" is started.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "TopicConnectionFactory" is started.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040306> <JMS service is active now.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101129> <Initializing the Web application container.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101238> <HTTP log rotation is size based for the Web server: new_managedServer_3.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101051> <[HTTP new_managedServer_3] started>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <WebService> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-220031> <The server does not support reliable SOAP messaging.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <WebService> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-220027> <Web Service reliable agents are started on the server.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149209> <Resuming.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <Common> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000625> <The application has disabled periodic testing of free resources in pool "cgPool".>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "cgPool" created.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "cgPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "cgPool" created.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "cgPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "cgPool" created.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "cgPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "cgPool" created.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "cgPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "cgPool" created.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "cgPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <Common> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000628> <Created "5" resources for pool "cgPool", out of which "5" are available and "0" are unavailable.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001124> <Created Connection Pool named cgPool.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <Common> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000625> <The application has disabled periodic testing of free resources in pool "bpmArchPool".>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "bpmArchPool" created.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "bpmArchPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "bpmArchPool" created.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "bpmArchPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "bpmArchPool" created.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "bpmArchPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "bpmArchPool" created.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "bpmArchPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "bpmArchPool" created.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "bpmArchPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <Common> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000628> <Created "5" resources for pool "bpmArchPool", out of which "5" are available and "0" are unavailable.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001124> <Created Connection Pool named bpmArchPool.>
####<Sep 23, 2004 5:50:51 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001121> <Created TX Data Source named cgDataSource for Pool cgPool.>
####<Sep 23, 2004 5:50:51 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001121> <Created TX Data Source named bpmArchDataSource for Pool bpmArchPool.>
####<Sep 23, 2004 5:50:51 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "WLI-B2B System Topic Factory" is started.>
####<Sep 23, 2004 5:50:56 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040322> <JMSServer "cgJMSServer_auto_3" is activating for migration.>
####<Sep 23, 2004 5:50:56 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040321> <JMSServer "cgJMSServer_auto_3" is resuming.>
####<Sep 23, 2004 5:50:58 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040117> <JMSServer "cgJMSServer_auto_3". Opening JDBC store tables "myC_3JMSStore" and "myC_3JMSState" using connection pool "cgPool".>
####<Sep 23, 2004 5:50:59 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040118> <JMSServer "cgJMSServer_auto_3". Finished scan of JDBC store. Found 3 records.>
####<Sep 23, 2004 5:50:59 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040010> <JMSServer "cgJMSServer_auto_3" configured no session pools.>
####<Sep 23, 2004 5:50:59 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040109> <JMSServer "cgJMSServer_auto_3" is started.>
####<Sep 23, 2004 5:50:59 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040309> <JMS server "cgJMSServer_auto_3" is activated.>
####<Sep 23, 2004 5:51:00 PM EDT> <Info> <WebLogicServer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000256> <Invoking com.bea.wli.init.BPMStartup.main(null)>
####<Sep 23, 2004 5:51:00 PM EDT> <Debug> <Management> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-141132> <Dynamic invocation while executing action updateDeployments on myClusterTest08:Location=new_managedServer_3,Name=new_managedServer_3,Type=ServerConfig MBean instance failed. The method updateDeployments with signature [] was invoked with parameters as [].
weblogic.management.AbortDeploymentException: weblogic.t3.srvr.FatalStartupException: Can't start server due to startup class failure WLI Startup Class - with nested exception:
[java.lang.NullPointerException]
at weblogic.t3.srvr.StartupClassService.addDeployment(Lweblogic.management.configuration.DeploymentMBean;)V(StartupClassService.java:92)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Lweblogic.management.configuration.DeploymentMBean;)Z(DeploymentTarget.java:330)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Ljava.util.List;)V(DeploymentTarget.java:590)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments()V(DeploymentTarget.java:568)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments()V(DeploymentTarget.java:240)
at COM.jrockit.reflect.NativeMethodInvoker.invoke0(ILjava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Native Method)
at COM.jrockit.reflect.NativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
at COM.jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(DynamicMBeanImpl.java:711)
at weblogic.management.internal.DynamicMBeanImpl.invoke(Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(DynamicMBeanImpl.java:690)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(ConfigurationMBeanImpl.java:476)
at com.sun.management.jmx.MBeanServerImpl.invoke(Ljava.lang.Object;Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(Ljavax.management.ObjectName;Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(MBeanServerImpl.java:1525)
at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(Ljavax.management.ObjectName;Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(RemoteMBeanServerImpl.java:947)
at weblogic.management.internal.RemoteMBeanServerImpl.invoke(Ljavax.management.ObjectName;Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(RemoteMBeanServerImpl.java:908)
at weblogic.management.internal.MBeanProxy.invoke(Ljava.lang.String;[Ljava.lang.Object;)Ljava.lang.Object;(MBeanProxy.java:946)
at weblogic.management.internal.MBeanProxy.invokeForCachingStub(Ljava.lang.String;[Ljava.lang.Object;)Ljava.lang.Object;(MBeanProxy.java:481)
at weblogic.management.configuration.ServerMBean_Stub.updateDeployments()V(ServerMBean_Stub.java:7271)
at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments()V(SlaveDeployer.java:1210)
at weblogic.management.deploy.slave.SlaveDeployer.resume()V(SlaveDeployer.java:362)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume()V(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume()V(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume()V(T3Srvr.java:964)
at weblogic.t3.srvr.T3Srvr.run([Ljava.lang.String;)I(T3Srvr.java:359)
at weblogic.Server.main([Ljava.lang.String;)V(Server.java:32)
>
####<Sep 23, 2004 5:51:00 PM EDT> <Error> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149601> <The deployment framework was unable to resume accepting requests.>
####<Sep 23, 2004 5:51:00 PM EDT> <Emergency> <WebLogicServer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000342> <Unable to initialize the server: [Deployer:149601]The deployment framework was unable to resume accepting requests.weblogic.t3.srvr.FatalStartupException: Can't start server due to startup class failure WLI Startup Class - with nested exception:
[java.lang.NullPointerException]>I set up WLI Clustering 8.1sp2 with 4 total managed servers, 2 colocated with the admin server, and 2 on a vanilla installation of WLP 8.1sp2.
While the colocated servers boot up correctly (and are able to be recovered by the node manager), I cannot seem to get the remote managed servers to come up properly. The node manager on the remote machine reports the following error:
####<Sep 23, 2004 5:49:50 PM EDT> <Notice> <Log Management> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-170019> <The server log file C:\bea\user_projects\domains\myClusterTest08\new_managedServer_3\new_managedServer_3.log is opened. All server side log events will be written to this file.>
####<Sep 23, 2004 5:49:51 PM EDT> <Info> <Socket> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000406> <NTSocketMuxer was built on Jun 19 2003 15:39:24
>
####<Sep 23, 2004 5:49:51 PM EDT> <Info> <Socket> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000436> <Allocating 2 reader threads.>
####<Sep 23, 2004 5:50:05 PM EDT> <Info> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090093> <No pre-WLS 8.1 Keystore providers are configured for server new_managedServer_3 for security realm myrealm.>
####<Sep 23, 2004 5:50:05 PM EDT> <Notice> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090082> <Security initializing using security realm myrealm.>
####<Sep 23, 2004 5:50:06 PM EDT> <Notice> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090170> <Loading the private key stored under the alias DemoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
####<Sep 23, 2004 5:50:07 PM EDT> <Notice> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090171> <Loading the identity certificate stored under the alias DemoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
####<Sep 23, 2004 5:50:07 PM EDT> <Notice> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\bea\weblogic81\server\lib\DemoTrust.jks.>
####<Sep 23, 2004 5:50:07 PM EDT> <Notice> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\bea\jrockit81sp2_141_05\jre\lib\security\cacerts.>
####<Sep 23, 2004 5:50:08 PM EDT> <Notice> <WebLogicServer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000328> <Starting WebLogic Managed Server "new_managedServer_3" for domain "myClusterTest08">
####<Sep 23, 2004 5:50:08 PM EDT> <Info> <WebLogicServer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000214> <WebLogic Server "new_managedServer_3" version:
WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic XMLX Module 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic Integration 8.1 SP2 Thu Dec 11 22:07:14 PST 2003 148883 (c) 1995, 1996, 1997, 1998 WebLogic, Inc.
(c) 1999, 2000, 2001 BEA Systems, Inc.>
####<Sep 23, 2004 5:50:08 PM EDT> <Info> <WebLogicServer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000215> <Loaded License : C:\bea\license.bea>
####<Sep 23, 2004 5:50:08 PM EDT> <Info> <RJVM> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000570> <Network Configuration for Channel "new_managedServer_3"
Listen Address informatica-svr:7001
Public Address N/A
Http Enabled true
Tunneling Enabled false
Outbound Enabled false
Admin Traffic Enabled true>
####<Sep 23, 2004 5:50:08 PM EDT> <Debug> <RJVM> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000571> <Network Configuration Detail for Channel "new_managedServer_3"
Channel Weight 50
Accept Backlog 50
Login Timeout 5000ms
Max Message Size 10000000
Message Timeout 60s
Idle Timeout 65s
Tunneling Timeout 40s
Tunneling Ping 45s>
####<Sep 23, 2004 5:50:08 PM EDT> <Info> <XML> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-130036> <Initializing XMLRegistry.>
####<Sep 23, 2004 5:50:08 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001135> <Initializing the JDBC service.>
####<Sep 23, 2004 5:50:09 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001137> <Initialization complete.>
####<Sep 23, 2004 5:50:09 PM EDT> <Info> <Connector> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-190000> <Initializing J2EE Connector Service>
####<Sep 23, 2004 5:50:09 PM EDT> <Info> <Connector> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-190001> <J2EE Connector Service initialized successfully>
####<Sep 23, 2004 5:50:09 PM EDT> <Info> <IIOP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-002014> <IIOP subsystem enabled.>
####<Sep 23, 2004 5:50:10 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040090> <Deployed 5 default connection factories.>
####<Sep 23, 2004 5:50:10 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040305> <JMS service is initialized and in standby mode.>
####<Sep 23, 2004 5:50:10 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101128> <Initializing HTTP services.>
####<Sep 23, 2004 5:50:10 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101133> <Initializing Web server new_managedServer_3.>
####<Sep 23, 2004 5:50:10 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101052> <[HTTP new_managedServer_3] Initialized>
####<Sep 23, 2004 5:50:10 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101135> <new_managedServer_3 is the default Web server.>
####<Sep 23, 2004 5:50:11 PM EDT> <Info> <J2EE> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-160037> <J2EE service initializing.>
####<Sep 23, 2004 5:50:11 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149207> <Initializing.>
####<Sep 23, 2004 5:50:13 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module uddiexplorer of application uddiexplorer is transitioning from unprepared to prepared on server new_managedServer_3.>
####<Sep 23, 2004 5:50:13 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module uddiexplorer of application uddiexplorer successfully transitioned from unprepared to prepared on server new_managedServer_3.>
####<Sep 23, 2004 5:50:13 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module uddi of application uddi is transitioning from unprepared to prepared on server new_managedServer_3.>
####<Sep 23, 2004 5:50:13 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module uddi of application uddi successfully transitioned from unprepared to prepared on server new_managedServer_3.>
####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module wl_management_internal1 of application wl_management_internal1 is transitioning from unprepared to prepared on server new_managedServer_3.>
####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module wl_management_internal1 of application wl_management_internal1 successfully transitioned from unprepared to prepared on server new_managedServer_3.>
####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module uddiexplorer of application uddiexplorer is transitioning from prepared to active on server new_managedServer_3.>
####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module uddiexplorer of application uddiexplorer successfully transitioned from prepared to active on server new_managedServer_3.>
####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module uddi of application uddi is transitioning from prepared to active on server new_managedServer_3.>
####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module uddi of application uddi successfully transitioned from prepared to active on server new_managedServer_3.>
####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module wl_management_internal1 of application wl_management_internal1 is transitioning from prepared to active on server new_managedServer_3.>
####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module wl_management_internal1 of application wl_management_internal1 successfully transitioned from prepared to active on server new_managedServer_3.>
####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149208> <Initialization Complete.>
####<Sep 23, 2004 5:50:17 PM EDT> <Notice> <Cluster> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000138> <Listening for announcements from cluster new_cluster_1 on 237.0.0.1:7001.>
####<Sep 23, 2004 5:50:17 PM EDT> <Notice> <Cluster> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000133> <Waiting to synchronize with other running members of new_cluster_1.>
####<Sep 23, 2004 5:50:48 PM EDT> <Info> <JTA> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-110441> <Opening transaction log with driver version "j1.0" and synchronous write policy "Cache-Flush". For information on synchronous write policies, refer to the weblogic.management.configuration.ServerMBean javadoc or console online help.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001138> <Resuming the JDBC service.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001140> <Resume complete.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "DefaultXAConnectionFactory" is started.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "QueueConnectionFactory" is started.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "MessageDrivenBeanConnectionFactory" is started.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "DefaultConnectionFactory" is started.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "TopicConnectionFactory" is started.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040306> <JMS service is active now.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101129> <Initializing the Web application container.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101238> <HTTP log rotation is size based for the Web server: new_managedServer_3.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101051> <[HTTP new_managedServer_3] started>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <WebService> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-220031> <The server does not support reliable SOAP messaging.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <WebService> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-220027> <Web Service reliable agents are started on the server.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149209> <Resuming.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <Common> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000625> <The application has disabled periodic testing of free resources in pool "cgPool".>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "cgPool" created.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "cgPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "cgPool" created.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "cgPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "cgPool" created.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "cgPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "cgPool" created.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "cgPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "cgPool" created.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "cgPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <Common> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000628> <Created "5" resources for pool "cgPool", out of which "5" are available and "0" are unavailable.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001124> <Created Connection Pool named cgPool.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <Common> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000625> <The application has disabled periodic testing of free resources in pool "bpmArchPool".>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "bpmArchPool" created.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "bpmArchPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "bpmArchPool" created.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "bpmArchPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "bpmArchPool" created.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "bpmArchPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "bpmArchPool" created.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "bpmArchPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "bpmArchPool" created.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "bpmArchPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <Common> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000628> <Created "5" resources for pool "bpmArchPool", out of which "5" are available and "0" are unavailable.>
####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001124> <Created Connection Pool named bpmArchPool.>
####<Sep 23, 2004 5:50:51 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001121> <Created TX Data Source named cgDataSource for Pool cgPool.>
####<Sep 23, 2004 5:50:51 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001121> <Created TX Data Source named bpmArchDataSource for Pool bpmArchPool.>
####<Sep 23, 2004 5:50:51 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "WLI-B2B System Topic Factory" is started.>
####<Sep 23, 2004 5:50:56 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040322> <JMSServer "cgJMSServer_auto_3" is activating for migration.>
####<Sep 23, 2004 5:50:56 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040321> <JMSServer "cgJMSServer_auto_3" is resuming.>
####<Sep 23, 2004 5:50:58 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040117> <JMSServer "cgJMSServer_auto_3". Opening JDBC store tables "myC_3JMSStore" and "myC_3JMSState" using connection pool "cgPool".>
####<Sep 23, 2004 5:50:59 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040118> <JMSServer "cgJMSServer_auto_3". Finished scan of JDBC store. Found 3 records.>
####<Sep 23, 2004 5:50:59 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040010> <JMSServer "cgJMSServer_auto_3" configured no session pools.>
####<Sep 23, 2004 5:50:59 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040109> <JMSServer "cgJMSServer_auto_3" is started.>
####<Sep 23, 2004 5:50:59 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040309> <JMS server "cgJMSServer_auto_3" is activated.>
####<Sep 23, 2004 5:51:00 PM EDT> <Info> <WebLogicServer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000256> <Invoking com.bea.wli.init.BPMStartup.main(null)>
####<Sep 23, 2004 5:51:00 PM EDT> <Debug> <Management> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-141132> <Dynamic invocation while executing action updateDeployments on myClusterTest08:Location=new_managedServer_3,Name=new_managedServer_3,Type=ServerConfig MBean instance failed. The method updateDeployments with signature [] was invoked with parameters as [].
weblogic.management.AbortDeploymentException: weblogic.t3.srvr.FatalStartupException: Can't start server due to startup class failure WLI Startup Class - with nested exception:
[java.lang.NullPointerException]
at weblogic.t3.srvr.StartupClassService.addDeployment(Lweblogic.management.configuration.DeploymentMBean;)V(StartupClassService.java:92)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Lweblogic.management.configuration.DeploymentMBean;)Z(DeploymentTarget.java:330)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Ljava.util.List;)V(DeploymentTarget.java:590)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments()V(DeploymentTarget.java:568)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments()V(DeploymentTarget.java:240)
at COM.jrockit.reflect.NativeMethodInvoker.invoke0(ILjava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Native Method)
at COM.jrockit.reflect.NativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
at COM.jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(DynamicMBeanImpl.java:711)
at weblogic.management.internal.DynamicMBeanImpl.invoke(Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(DynamicMBeanImpl.java:690)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(ConfigurationMBeanImpl.java:476)
at com.sun.management.jmx.MBeanServerImpl.invoke(Ljava.lang.Object;Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(Ljavax.management.ObjectName;Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(MBeanServerImpl.java:1525)
at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(Ljavax.management.ObjectName;Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(RemoteMBeanServerImpl.java:947)
at weblogic.management.internal.RemoteMBeanServerImpl.invoke(Ljavax.management.ObjectName;Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(RemoteMBeanServerImpl.java:908)
at weblogic.management.internal.MBeanProxy.invoke(Ljava.lang.String;[Ljava.lang.Object;)Ljava.lang.Object;(MBeanProxy.java:946)
at weblogic.management.internal.MBeanProxy.invokeForCachingStub(Ljava.lang.String;[Ljava.lang.Object;)Ljava.lang.Object;(MBeanProxy.java:481)
at weblogic.management.configuration.ServerMBean_Stub.updateDeployments()V(ServerMBean_Stub.java:7271)
at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments()V(SlaveDeployer.java:1210)
at weblogic.management.deploy.slave.SlaveDeployer.resume()V(SlaveDeployer.java:362)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume()V(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume()V(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume()V(T3Srvr.java:964)
at weblogic.t3.srvr.T3Srvr.run([Ljava.lang.String;)I(T3Srvr.java:359)
at weblogic.Server.main([Ljava.lang.String;)V(Server.java:32)
>
####<Sep 23, 2004 5:51:00 PM EDT> <Error> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149601> <The deployment framework was unable to resume accepting requests.>
####<Sep 23, 2004 5:51:00 PM EDT> <Emergency> <WebLogicServer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000342> <Unable to initialize the server: [Deployer:149601]The deployment framework was unable to resume accepting requests.weblogic.t3.srvr.FatalStartupException: Can't start server due to startup class failure WLI Startup Class - with nested exception:
[java.lang.NullPointerException]> -
MS SQL 2005 clustered database instance.
Short Text
MS SQL cluster database instance - ONLY!
Long Text
Hi,
If possible could you please confirm that our planned landscape
migration is supported by SAP.
At present our PRD SAP system is a standalone instance that consists of
the database & central instance running on the same "HOST".
<u>Current SAP PRD version:</u>
ERP 2004 ECC 5.0 32 bit
MS SQL 2000 32 bit
both running on same host with OS Windows 2003 32 bit
We plan to upgrade/migrate our PRD SAP system to new 64 bit hardware
AND to move to a "Distributed" landscape installation i.e. database
instance & central instance installed on different HOSTS. Also, the
database instance WILL be clustered but the central instance will NOT
be clustered. There are also multiple NON-SAP MS SQL databases that
will run in the same cluster as the PRD SAP database instance.
<u>SAP PRD version after migration:</u>
SAP ERP 2004 ECC 5.0 64bit (running on X86_64 AMD64 hardware) on HOST'X'
MS SQL 2005 64 bit (running on IA64 hardware) on clustered HOST'Y'
Both running on Windows 2003 64 bit
<u>My questions are:</u>
1) Does SAP support a clustered MS SQL 2005 database instance that is
running on a clustered HOST along with NON-SAP MS SQL databases?
2)During the migration our PRD SAP MS SQL database will be upgraded
from MS SQL 2000 32 bit to MS SQL 2005 64 bit IA64, is this also
supported in a clustered istallation (database instance ONLY)?
3) The central PRD SAP instance will be running on x86_64 AMD64
hardware & the database instance will be running on 64 bit IA64
hardware. Is this configuration supported?
Thanking you inadvance.Hi Greg,
Have you figured out the answer? We are trying do the exactly the same thing -- Move our SAP WAS 6.40 clustered central instance to a 64-bit hardware/SQL 2005/Clustered system. And this system has several non-SAP database on there. The biggest concern we have is whether SAP support this architecture. I posted a message here last year and several experts like Clas Hortien, N. P. C, in this form suggest NOT go to this architecture because SAP will not support it. One example, is that SAP/SQL requires server collation setting to SQL_Latin1_General_CP850_BIN2 and other databases may work on different collations.
Migrate SAP SQL Server database to co-exist with others
Anyway, if you or anyone in this form have some more information please share here.
Thanks,
Yujun Ran -
JMS Messaging Bridge Problems with WLS 8.1 sp2
Thank you in advance for your help.
I am trying to configure a JSM Messaging Bridge to connect an MQ Q to a Weblogic
Q. I have this working wonderfully in an environment without clustering but once
I try to deploy to a cluster, I am having two major problems.
1) When the managed servers are restarted, the messaging bridges immediately complain
about not being able to find the resource adaptor. After I manually un-target
the messaging bridge from the cluster and re-target them, they find the resource
adaptor but cannot connect to the source... which leads to my next problem.
2) The messaging bridges cannot connect to the source destination whether it is
an MQ Q or a Weblogic JMS Q does not matter. Here are the log entries that I
see relative:
####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
<Messaging bridge debugging STARTUP! Got Notification:weblogic.management.AttributeAddNotification:
Deployments from <null> to [Caching Stub]Proxy for eBusDev02:Location=secaServer01,Name=seca_OES_ADV_REPLY
Messaging Bridge,Type=MessagingBridgeConfig - weblogic.management.AttributeAddNotification[source=eBusDev02:Location=secaServer01,Name=secaServer01,Type=ServerConfig].>
####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
<Messaging bridge debugging STARTUP! creating bridge seca_OES_ADV_REPLY Messaging
Bridge.>
####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
<Messaging bridge debugging STARTUP! Bridge seca_OES_ADV_REPLY Messaging Bridge
is deployed as a migratable.>
####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
<Messaging bridge debugging RUNTIME! Initializging bridge seca_OES_ADV_REPLY Messaging
Bridge as a migratable.>
####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
<Messaging bridge debugging STARTUP! Bridge seca_OES_ADV_REPLY Messaging Bridge's
source configurations are:
AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
Classpath=null
ConnectionURL = file:/e:/private/JNDI/eBusDev02
DestinationType = Queue
DestinationJNDIName = jms.oes.MQ-ADV-REPLYQ
InitialContextFactory = com.sun.jndi.fscontext.RefFSContextFactory
ConnectionFactoryJNDIName = jms.oes.MQ-QCF
.>
####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
<Messaging bridge debugging STARTUP! Bridge seca_OES_ADV_REPLY Messaging Bridge's
target configurations are:
AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
Classpath=null
ConnectionURL = t3://30.135.10.63:8103,30.135.10.63:8104
DestinationType = Queue
DestinationJNDIName = jms/oes/ADV-REPLYQ
InitialContextFactory = weblogic.jndi.WLInitialContextFactory
ConnectionFactoryJNDIName = jms/oes/QCF
.>
####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
<Messaging bridge debugging STARTUP! Bridge seca_OES_ADV_REPLY Messaging Bridge
is successfully initialized.>
####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
<Messaging bridge debugging RUNTIME! Bridge seca_OES_ADV_REPLY Messaging Bridge
has been successfully initialized as a migratable.>
####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
<Messaging bridge debugging RUNTIME! Activating bridge seca_OES_ADV_REPLY Messaging
Bridge.>
####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
<Messaging bridge debugging RUNTIME! Bridge seca_OES_ADV_REPLY Messaging Bridge
has been successfully activated..>
####<Apr 1, 2004 4:38:44 PM EST> <Info> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '22' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-200033>
<Bridge "seca_OES_ADV_REPLY Messaging Bridge" is obtaining connections to the
two adapters.>
####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '22' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-200006>
<Messaging bridge debugging RUNTIME! Bridge seca_OES_ADV_REPLY Messaging Bridge
Getting source connection.>
####<Apr 1, 2004 4:38:44 PM EST> <Info> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '22' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-200042>
<Bridge seca_OES_ADV_REPLY Messaging Bridge failed to connect to the source destination
and will try again in 15 seconds. (java.lang.NullPointerException)>
I know the queues are up and I am pretty sure my MQ client configuration is correct.
Is there anyway to get more information about the NullPointerException or the
error being encountered?
Given that you have ruled out message backlogs, my first suspicion is that the leak has something to do with connection allocation. Does JMS stats reveal an application generated connection leak? Check to see if the current number of connections/sessions stays steady.
If this doesn't help, you can use a third party tool like OptimizeIt to get periodic snap-shots of memory usage and identify the leaked object (or create a reproducer and have customer support do it). A possible work-around is to modify your app to pool JMS connections/sessions for re-use - greatly reducing the number of connections created per day.
Tom -
Hello all !!
I have a problem when I execute fox formulas in BPS0 in version 7.0, becuase they don't work.
The company migrated BW-BPS to 7.0 version.
The problem occurs when I execute the formulas in BPS0 in the quality environment, which is working with 7.0 version, but we are using 3.5 version in the productive environment; besides we are working with 7.0 version in BW.
I was wondering if the syntax of the FOX formulas between version is diferrent.....any idea??
I appreciate your help!!!Hi Arlene,
please check [Re: Foxformula].
Regards Matthias Nutt
SAP Consulting Switzerland -
Hi gurus,
Wanted to find out the best method for modelling BPS
1) Got a Acutals cube..having
Product group
Product
Profit Center
Budget
2) In the planned cube do i need all the characteristics of the actuals cube +
Jan
Feb
Marc
3) In BPS do i need to create planning areas for each cube & do multiplanning or do i create multiprovider in BI.
AppreciateHi,
Yes the modelling procedures differ in IP and BPS quite a bit.
The objects that need to be created for modelling a Planning scenario are different in both and cannot be migrated from BPS to IP version.
1) if it remains the same why is that BPS dont use Multiproviders & IP uses Multiproviders....
because the modelling objects have been changed in the tool by SAP
2) In both the cases the procedure would be the same...like
- creating seperate planning areas for each cube(actual & plan)
- creating multiplanning area
you do not create planning areas any longer in IP, you work directly on the Infoprovider/Multiprovider
Refer to the help for more details on IP
http://help.sap.com/saphelp_nw70/helpdata/en/44/e042be7db603fbe10000000a1553f6/frameset.htm
hope it helps
Maybe you are looking for
-
How to install portal on Netweaver 04 WebAS SP16 ?
Hello SDNers, We need to have Enterprise Portal installed on our NetWeaver 04 WebAS Java SP 16. The following is our setup: 1. WebAS SP09 was installed without Enterprise Portal SP09. 2. Patch upgrade applied on WebAS from SP09 to SP16. Now is it pos
-
I am running Windows 7 and Thunderbird 26.6.0 I guess I should have made new archive folders under my new e-mail account and transferred everything into them before i deleted the old account, but I didn't know all the archive folders were going to di
-
Error message in customer exit
HI ABAPer's, I am facing the one problem while giving the error message in customer exit ZXM06U43(POCustomer exit). The scenario is i am looping the tekpo(PO line item) internal tables and doing some validations if any lineitem fail in the validat
-
Is there a free App to hide video & pics
Anyone know of a free app that will hide videos & pics on the PB, either app world or sideloaded?
-
Can applet pass value back to web page?
if i run an applet in a web page, eg: aspx is it possible for me to pass value back to the page?