New Member introduction

Hello I am a new member here and I want to introduce myself. I am known as Sakasa and what I do is graphics wallpapers designs. Most of the wallpapers are done for the Linux community and I will want to share some of these works in the near future with you all. I do not really get involve in OS development of graphics wallpapers desktops, themes or anything else.. Hopefully that my art can help this great community through the offering of the art. Here is my latest Arch Linux wallpapers.
http://bestfreewallpapers.net/tiki-brow … lleryId=12
Hope you like these.
Best Regards,
Last edited by sakasa (2010-05-15 17:25:46)

Allan wrote:So... you are not making any wallpapers specifically for Arch, but rather rehashing wallpapers by changing the distro name on them to Arch. Combine that with joining the forums just to post a link to your website and I start hearing warning bells. Are you actually using Arch Linux at all or just here to "spam"?
I have done wallpapers for the linux community for a long time. Arch Linux is a great and known distro. Linux needs a push and this has always been my intention to go ahead and do what I must do and it is to help societies that offer their work for free and can express freely through. I do not need to spam or ever will. I want to make it strickly clear. Many distros have use my wallpapers in their different distro version and I am well known. Antix Linux, PCLinuxOS, and a few others have use my art in others OS, I do not recall right now. I do not care if this society, members or others uses my wallpapers for their distros or for their desktop looks as long as they can benefit from these then I a m doing my duty. Google sakasa and you will see. You comment: you are not making any wallpapers specifically for Arch, but rather rehashing wallpapers by changing the distro name on them to Arch my re: I make a nice wallpaper and after I go ahead and add up the different OS names like all artist do but not how you specify it above.. My art is original and I hold 100's of licenses It would not be fair for the linux society and other distros not to be able to obtain the same type of wallpapers. I do not think it would be correct that I as an artist will take only one side or a specific distro and leave the rest like they do not exist. Linux is for all and I am a truly belief that we must work together to encourage all the distros so we can grow as a bigger community in this world, which it is needed. I thought by offering that I will get an opposite of the response that I am getting from you. The warning bells you maybe hearing it from someone else. You have put me into in a interrogative situation without knowing me, only because I came here to offer to your OS an extra service in a noble way. This is shocking to me I do not judge or interrogate until I am really and truly sure to know completely a person intentions with time before I can judge or asking them a question and even if I do judge them it does not mean I am right, still I could be wrong. So I am very sensitive before I open my mouth to interrogate or ask questions to anyone like the ones you have make me here..
I do not need to spam. I take this very seriously and if you belief from your part that this is my intention then go ahead and erase me from your members list.
I hope that you can understand my message and I ask to excuse my English because it is not the best.
One more thing I am not here to work in the development of your distro or any distro as I mentioned in the above post. I feel exciting when others are doing their work too because this help greatly the Linux community and we most expand linux within unlimited ways if we want it to succeed even more.. This is my belief..
Sincerely, Sakasa
Last edited by sakasa (2010-05-16 06:38:48)

Similar Messages

Techniques for New Product Introduction in Demantra 7.3.0.1

Hi,
In Demantra 7.3.0.1 there are two ways for New Product Introduction:-
1) Demand Planner: Member & chaining management
2) Collaborative Workbench: Create Similar product
Can someone please tell me the pros and cons of each technique.
The new product introduction will be handled by our clients, so I wanted to know if all the required features can be handled by just one method so we can propose that to be used by the client. Or do we need to use both techniques for different scenarios?
As I understand with Chaining one can link one item to many sites at one go, while with CW the similar item is created linked to one particular location.
Also CW allows for adding cannibalization factor which is not accounted for in chaining.
Apart from this it would be really helpful if someone could throw some more light on the issue.
Thanks.

Hi Gaurav,
I personally feel that 'Create Similar product' is a much required improvement over the original way of NPI using Member & Chaining Management.
Also with CW as well, a new and similar item created can also be linked to multiple location, same as Source Item, depending on the filters used in the Worksheet from which the create similar product is invoked.
some of the PROS and CONS of the 2 methods are as follows:
Demand Planner: Member & chaining management
Pros: 1) Can be used to specify the time range for copying the history date.
2) Can be used to specify the Percentage by which the source data needs to be adjusted while copying into the target combination
3) An important feature is that this can be used to do chaining at an aggregated level.
Cons: 1) It takes a long time to setup a New Member, combination and Chaining relationship.
2) High User involvement since user has to perform muliptle tasks and more error prone.
Collaborative Workbench: Create Similar product
Pros: 1) User-friendly
2) Users needs to enter a few datapoints in single form and does not need to navigate through multiple forms/screens
3) Ability to specify Cannibalization parameters as well as Launch dates
4) Good performance.
5) Ongoing Chaining
6) When coupled with features like 'End of Lifecycle date', it provides a complete Business solution
Cons: 1) Can not be used for only performing Chaining.
2) While it can be used to create a New Similar Product, it cannot be used to create a new similar Customer based on an existing item-location combination data. This,though, may not be a very common scenario.
3) Apart from copying other Item attributes, the method also copies the same 'Item Description' level from source to the new similar product, which sometimes can be very confusing.
Hope this helps.
Thanks,
Rohit Goyal

A new member

Hello guys!
A new member to this great forum!
And moving to JAVA :) , too, from others greats Programming Langauges!
S�crates

Welcome,
Here are some links to a bunch of Java related sites, both reference and forums.
Installation Notes - JDK 5.0 Microsoft Windows (32-bit)
Your First Cup of Java
The Java� Tutorial - A practical guide for programmers
New to Java Center
Java Programming Notes - Fred Swartz
How To Think Like A Computer Scientist
Introduction to Computer science using Java
The Java Developers Almanac 1.4
Object-Oriented Programming Concepts
Object-oriented language basics
Don't Fear the OOP
Free Java Books
Thinking in Java, by Bruce Eckel (Free online)
Core Servlet Programming, by Merty Hall (Free Online)
More Servlets, by Marty Hall (Free Online)
A Java GUI Programmer's Primer
Data Structures and Algorithms
with Object-Oriented Design Patterns in Java, by Bruno R. Preiss
Introduction to Programming Using Java, by David J. Eck
Advanced Programming for the Java 2 Platform
The Java Language Specification
Books:
Head First Java, by Bert Bates and Kathy Sierra
Core Java, by Cay Horstmann and Gary Cornell
Effective Java, by Joshua Bloch
As far as wether to use an IDE or not... I say go for it. There are valid reasons to not use an IDE such as understanding classpath. compiling classes and packages, jaring files together, etc..
However, there are numerous reasons to use a good ide such as Netbeans or BlueJ or Eclipse. The IDE will give you immediate feedback about the syntax of your code, misspellings, missing imports, not catching an exception and they also help you conform to good codeing standards such as indentation and {} usage.
IMHO it is perfectly valid for you to say, use the IDE to edit your source code, but then use a command shell in the root of your source code and compile by hand. That way you will be aware of the things the IDE normally hides from you like class paths, library package files, etc... IDE's are great, but they do hide alot of the nuts and bolts that you should be aware of.
Ive thought about this a lot and the best analogy I can think of is... When I have to write some technical paper or thesis, or any proffesional document, I go straight to a word processor because it gives me immediate feedback about things like spelling, grammer errors, formatting and the like. I donot use notepad to compose my documents first and then use a wordprocessor to do spell check or formatting...
Anyway, enough from my soapbox...
Cheers!
JJ

Upload new member in the dimension not from BPC Admin

Hi Experts,
                 If we want to upload a new account not from of BPC admin, how we can do it?
    I tried to do it in MS version and was able to do it, as we have a dimension files in excel format (other than the temporary excel file ), we can add member in that excel file and run the Dimension process without selecting the "from member sheet". And it includes the new member.
              But in Netweaver version if we do same thing in the xml file of that dimension and try to process, it doesn't take the new member which was added in the xml file.. Any idea ..
Thanks
IshitaD

Hi Ishita,
Can you try using Data Manager to load master data? I know that is too much trouble if you want to load say just 1 record but it is a clean option that does not require BPC Admin.
Regards
Pravin

Ann: SuperScheduler: a new member of Super 1.80

Announcement: Super 1.8 - an EJB/J2EE monitoring/admin tool with
SuperEnvironment
SuperLogging
SuperPeekPoke
SuperReport
SuperStress
has got a new member: SuperScheduler
You can anomyously down load it free from:
http://www.acelet.com.
Super is a component based administration tool for EJB/J2ee.
It provides built-in functionality as well as
extensions, as SuperComponents. Users can install
SuperComponents onto it, or uninstall them from it.
Super has the following functions:
* A J2EE/EJB monitor.
* A gateway to EJB servers from different vendors.
* A framework holding user defined SuperComponents.
* A full-featured logging/tracing tool for centralized, chronological logging.
* A PeekPoke tool to read/write attributes from EJBs.
* A Stress test tool.
* A global environment tool.
* A report tool.
* A Scheduler tool.
It is written in pure Java.
The current version support:
* Universal servers.
* Weblogic 5.1, 6.0
* Weblogic 6.1 with EJB 2.
What is new:
Version 1.80 March 2002
Enhancement:
1. Add new component: SuperScheduler
Bug fix:
1. SuperLogging: Verbose should ignore class registration.
2. SuperLogging-tracing: an exception was thrown if the java class without package
name.
Version 1.70 January 2002
Enhancement:
1. SuperLogging: Scope can dynamically change both for upgrade to downgrade (for
weblogic 6.1, need download an application).
2. Add alias names for log threshold as new Java suggests.
3. New component: SuperReport.
Change:
1. SuperLogging: Log database parameters are specified in a properties file, instead
of EJB's deployment descriptor. It is more convenient and it avoids some potential
problems. No change for development, easier for administration.
Bug fix:
1. Add Source Path Panel now accepts both directory and jar file.
2. Bug in SuperEnvironment example (for version 1.60 only).
Version 1.60 December 2001
Enhancement:
1. SuperPeekPoke and SuperStress can use user defined dynamic argument list.
2. Add timeout parameter to logging access.
3. New installation program with A). Easy install. B). Remote command line install.
4. Support EJB 2.0 for Weblogic 6.1.
5. Support SuperPeekPoke, SuperEnvironment and SuperStress for Websphere 4.0 (SuperLogging
was supported since version 1.5).
Change:
1. Poke: argument list is set at define time, not invoke time.
2. Default log database change to server mode from web server mode, booting performance
to 10-20 times.
Bug fix:
1. If the returned object is null, Peek did not handle it correctly.
2. If the value was too big, TimeSeries chart did not handle it correctly. Now
it can handle up to 1.0E300.
3. Help message was difficult to access in installation program.
4. Source code panel now both highlights and marks the line in question (before
it was only highlight using JDK 1.2, not JDK 1.3).
5. Delete an item on PeekPoke and add a new one generated an error.
Version 1.50 August, 2001
Enhancement:
1. Source code level tracing supports EJB, JSP, java helper and other
programs which are written in native languages (as long as you
write correct log messages in your application).
2. Redress supports JSP now.
3. New installation with full help document: hope it will be easier.
4. Support WebSphere 4.0
Version 1.40 June, 2001
Enhancement:
1. Add SuperEnvironment which is a Kaleidoscope with TableView, TimeSeriesView
and PieView for GlobalProperties.
GlobalProperties is an open source program from Acelet.
2. SuperPeekPoke adds Kaleidoscope with TableView, TimeSeriesView and PieView.
Changes:
1. The structure of log database changed. You need delete old installation and
install everything new.
2. The format of time stamp of SuperLogging changed. It is not locale dependent:
better for report utilities.
3. Time stamp of SuperLogging added machine name: better for clustering environment.
Bug fix:
1. Under JDK 1.3, when you close Trace Panel, the timer may not be stopped and
Style Panel may not show up.
Version 1.30 May, 2001
Enhancement:
1. Add ConnectionPlugin support.
2. Add support for Borland AppServer.
Version 1.20 April, 2001
Enhancement:
1. Redress with option to save a backup file
2. More data validation on Dump Panel.
3. Add uninstall for Super itself.
4. Add Log Database Panel for changing the log database parameters.
5. Register Class: you can type in name or browse on file system.
6. New tour with new examples.
Bug fix:
1. Redress: save file may fail.
2. Install Bean: some may fail due to missing manifest file. Now, it is treated
as foreign beans.
3. Installation: Both installServerSideLibrary and installLogDatabase can be worked
on the original file, do not need copy to a temporary directory anymore.
4. PeekPoke: if there is no stub available, JNDI list would be empty for Weblogic5-6.
Now it pick up all availble ones and give warning messages.
5. Stress: Launch>Save>Cancel generated a null pointer exception.
Changes:
1. installLogDatabase has been changed from .zip file to .jar file.
2. SuperLogging: If the log database is broken, the log methods will not try to
access the log database. It is consistent with the document now.
3. SuperLogging will not read system properties now. You can put log database
parameters in SuperLoggingEJB's deployment descriptor.
Version 1.10 Feb., 2001
Enhancement:
1. Re-written PeekPoke with Save/Restore functions.
2. New SuperComponent: SuperStress for stress test.
3. Set a mark at the highlighted line on the Source Code
Panel (as a work-a-round for JDK 1.3).
4. Add support for WebLogic 6.0
Bug fix:
1. Uninstall bean does physically delete the jar file now.
2. WebLogic51 Envoy may not always list all JNDI names. This is fixed.
Version 1.00 Oct., 2000
Enhancement:
1. Support Universal server (virtual all EJB servers).
2. Add Lost and Found for JNDI names, in case you need it.
3. JNDI ComboBox is editable now, so you can PeekPoke not listed JNDI name (mainly
for Envoys which do not support JNDI list).
Version 0.90: Sept, 2000
Enhancement:
1. PeekPoke supports arbitrary objects (except for Vector, Hashtable
and alike) as input values.
2. Reworked help documents.
Bug fix:
1. Clicking Cancel button on Pace Panel set 0 to pace. It causes
further time-out.
2. MDI related bugs under JDK 1.3.
Version 0.80: Aug, 2000
Enhancement:
1. With full-featured SuperLogging.
Version 0.72: July, 2000
Bug fix:
1. Ignore unknown objects, so Weblogic5.1 can show JNDI list.
Version 0.71: July, 2000
Enhancement:
1. Re-worked peek algorithm, doing better for concurent use.
2. Add cacellable Wait dialog, showing Super is busy.
3. Add Stop button on Peek Panel.
4. Add undeploy example button.
Bug fix:
1. Deletion on Peek Panel may cause error under JDK 1.3. Now it works for both
1.2 and 1.3
Version 0.70: July, 2000
Enhancement:
1. PeekPoke EJBs without programming.
Bug fix:
1. Did not show many windows under JDK 1.3. Now it works for both 1.2 and 1.3
Changes:
1. All changes are backward compatible, but you may need to recompile monitor
windows defined by you.
Version 0.61: June, 2000
Bug fix:
1. First time if you choose BUFFER as logging device, message will not show.
2. Fixed LoggingPanel related bugs.
Version 0.60: May, 2000
Enhancement:
1. Add DATABASE as a logging device for persistent logging message.
2. Made alertInterval configurable.
3. Made pace for tracing configurable.
Bug fix:
1. Fixed many bugs.
Version 0.51, 0.52 and 0.53: April, 2000
Enhancement:
1. Add support to Weblogic 5.1 (support for Logging/Tracing and
user defined GUI window, not support for regular monitoring).
Bug fix:
1. Context sensitive help is available for most of windows: press F1.
2. Fix installation related problems.
Version 0.50: April, 2000
Enhancement:
1. Use JavaHelp for help system.
2. Add shutdown functionality for J2EE.
3. Add support to Weblogic 4.5 (support for Logging/Tracing and
user defined GUI window, not support for regular monitoring).
Bug fix:
1. Better exception handling for null Application.
Version 0.40: March, 2000
Enhancement:
1.New installation program, solves installation related problems.
2. Installation deploys AceletSuperApp application.
3. Add deploy/undeploy facilities.
4. Add EJB and application lists.
Change:
1.SimpleMonitorInterface: now more simple.
Version 0.30: January, 2000
Enhancement:
1. Add realm support to J2EE
2. Come with installation program: you just install what you want
the first time you run Super.
Version 0.20: January, 2000
Enhancement:
Add support to J2EE Sun-RI.
Change:
1. Replace logging device "file" with "buffer" to be
compliant to EJB 1.1. Your code do not need to change.
Version 0.10: December, 1999
Enhancement:
1. provide SimpleMonitorInterface, so GUI experience is
not necessary for developing most monitoring applications.
2. Sortable table for table based windows by mouse
click (left or right).
Version 0.01 November., 1999:
1. Bug fix: An exception thrown when log file is large.
2. Enhancement: Add tour section in Help information.
Version 0.00: October, 1999
Thanks.

Not if they are being manually added, you could look at automating the process usIng the outlineload utility or ODI if they are classic applications.
Cheers
John
http://john-goodwin.blogspot.com/

Ann: SuperReport - a new member from Super 1.7

Announcement: Super 1.7 - an EJB/J2EE monitoring tool with
SuperEnvironment
SuperLogging
SuperPeekPoke
SuperStress
has got a new member: SuperReport
You can anomyously down load it free from:
http://www.acelet.com.
Super is a component based administration tool for EJB/J2ee.
It provides built-in functionality as well as
extensions, as SuperComponents. Users can install
SuperComponents onto it, or uninstall them from it.
Super has the following functions:
* A J2EE/EJB monitor.
* A gateway to EJB servers from different vendors.
* A framework holding user defined SuperComponents.
* A PeekPoke tool to read/write attributes from EJBs.
* A full-featured logging/tracing tool for centralized, chronological logging.
* A Stress test tool.
* A global environment tool.
* A report tool.
It is written in pure Java.
The current version support:
* Universal servers.
* Weblogic 5.1, 6.0
* Weblogic 6.1 with EJB 2.
What is new:
Version 1.70 January 2002
Enhancement:
1. SuperLogging: Scope can dynamically change both for upgrade to downgrade (for
weblogic 6.1, need download an application).
2. Add alias names for log threshold as new Java suggests.
3. New component: SuperReport.
Change:
1. SuperLogging: Log database parameters are specified in a properties file, instead
of EJB's deployment descriptor. It is more convenient and it avoids some potential
problems. No change for development, easier for administration.
Bug fix:
1. Add Source Path Panel now accepts both directory and jar file.
2. Bug in SuperEnvironment example (for version 1.60 only).
Version 1.60 December 2001
Enhancement:
1. SuperPeekPoke and SuperStress can use user defined dynamic argument list.
2. Add timeout parameter to logging access.
3. New installation program with A). Easy install. B). Remote command line install.
4. Support EJB 2.0 for Weblogic 6.1.
5. Support SuperPeekPoke, SuperEnvironment and SuperStress for Websphere 4.0 (SuperLogging
was supported since version 1.5).
Change:
1. Poke: argument list is set at define time, not invoke time.
2. Default log database change to server mode from web server mode, booting performance
to 10-20 times.
Bug fix:
1. If the returned object is null, Peek did not handle it correctly.
2. If the value was too big, TimeSeries chart did not handle it correctly. Now
it can handle up to 1.0E300.
3. Help message was difficult to access in installation program.
4. Source code panel now both highlights and marks the line in question (before
it was only highlight using JDK 1.2, not JDK 1.3).
5. Delete an item on PeekPoke and add a new one generated an error.
Version 1.50 August, 2001
Enhancement:
1. Source code level tracing supports EJB, JSP, java helper and other
programs which are written in native languages (as long as you
write correct log messages in your application).
2. Redress supports JSP now.
3. New installation with full help document: hope it will be easier.
4. Support WebSphere 4.0
Version 1.40 June, 2001
Enhancement:
1. Add SuperEnvironment which is a Kaleidoscope with TableView, TimeSeriesView
and PieView for GlobalProperties.
GlobalProperties is an open source program from Acelet.
2. SuperPeekPoke adds Kaleidoscope with TableView, TimeSeriesView and PieView.
Changes:
1. The structure of log database changed. You need delete old installation and
install everything new.
2. The format of time stamp of SuperLogging changed. It is not locale dependent:
better for report utilities.
3. Time stamp of SuperLogging added machine name: better for clustering environment.
Bug fix:
1. Under JDK 1.3, when you close Trace Panel, the timer may not be stopped and
Style Panel may not show up.
Version 1.30 May, 2001
Enhancement:
1. Add ConnectionPlugin support.
2. Add support for Borland AppServer.
Version 1.20 April, 2001
Enhancement:
1. Redress with option to save a backup file
2. More data validation on Dump Panel.
3. Add uninstall for Super itself.
4. Add Log Database Panel for changing the log database parameters.
5. Register Class: you can type in name or browse on file system.
6. New tour with new examples.
Bug fix:
1. Redress: save file may fail.
2. Install Bean: some may fail due to missing manifest file. Now, it is treated
as foreign beans.
3. Installation: Both installServerSideLibrary and installLogDatabase can be worked
on the original file, do not need copy to a temporary directory anymore.
4. PeekPoke: if there is no stub available, JNDI list would be empty for Weblogic5-6.
Now it pick up all availble ones and give warning messages.
5. Stress: Launch>Save>Cancel generated a null pointer exception.
Changes:
1. installLogDatabase has been changed from .zip file to .jar file.
2. SuperLogging: If the log database is broken, the log methods will not try to
access the log database. It is consistent with the document now.
3. SuperLogging will not read system properties now. You can put log database
parameters in SuperLoggingEJB's deployment descriptor.
Version 1.10 Feb., 2001
Enhancement:
1. Re-written PeekPoke with Save/Restore functions.
2. New SuperComponent: SuperStress for stress test.
3. Set a mark at the highlighted line on the Source Code
Panel (as a work-a-round for JDK 1.3).
4. Add support for WebLogic 6.0
Bug fix:
1. Uninstall bean does physically delete the jar file now.
2. WebLogic51 Envoy may not always list all JNDI names. This is fixed.
Version 1.00 Oct., 2000
Enhancement:
1. Support Universal server (virtual all EJB servers).
2. Add Lost and Found for JNDI names, in case you need it.
3. JNDI ComboBox is editable now, so you can PeekPoke not listed JNDI name (mainly
for Envoys which do not support JNDI list).
Version 0.90: Sept, 2000
Enhancement:
1. PeekPoke supports arbitrary objects (except for Vector, Hashtable
and alike) as input values.
2. Reworked help documents.
Bug fix:
1. Clicking Cancel button on Pace Panel set 0 to pace. It causes
further time-out.
2. MDI related bugs under JDK 1.3.
Version 0.80: Aug, 2000
Enhancement:
1. With full-featured SuperLogging.
Version 0.72: July, 2000
Bug fix:
1. Ignore unknown objects, so Weblogic5.1 can show JNDI list.
Version 0.71: July, 2000
Enhancement:
1. Re-worked peek algorithm, doing better for concurent use.
2. Add cacellable Wait dialog, showing Super is busy.
3. Add Stop button on Peek Panel.
4. Add undeploy example button.
Bug fix:
1. Deletion on Peek Panel may cause error under JDK 1.3. Now it works for both
1.2 and 1.3
Version 0.70: July, 2000
Enhancement:
1. PeekPoke EJBs without programming.
Bug fix:
1. Did not show many windows under JDK 1.3. Now it works for both 1.2 and 1.3
Changes:
1. All changes are backward compatible, but you may need to recompile monitor
windows defined by you.
Version 0.61: June, 2000
Bug fix:
1. First time if you choose BUFFER as logging device, message will not show.
2. Fixed LoggingPanel related bugs.
Version 0.60: May, 2000
Enhancement:
1. Add DATABASE as a logging device for persistent logging message.
2. Made alertInterval configurable.
3. Made pace for tracing configurable.
Bug fix:
1. Fixed many bugs.
Version 0.51, 0.52 and 0.53: April, 2000
Enhancement:
1. Add support to Weblogic 5.1 (support for Logging/Tracing and
user defined GUI window, not support for regular monitoring).
Bug fix:
1. Context sensitive help is available for most of windows: press F1.
2. Fix installation related problems.
Version 0.50: April, 2000
Enhancement:
1. Use JavaHelp for help system.
2. Add shutdown functionality for J2EE.
3. Add support to Weblogic 4.5 (support for Logging/Tracing and
user defined GUI window, not support for regular monitoring).
Bug fix:
1. Better exception handling for null Application.
Version 0.40: March, 2000
Enhancement:
1.New installation program, solves installation related problems.
2. Installation deploys AceletSuperApp application.
3. Add deploy/undeploy facilities.
4. Add EJB and application lists.
Change:
1.SimpleMonitorInterface: now more simple.
Version 0.30: January, 2000
Enhancement:
1. Add realm support to J2EE
2. Come with installation program: you just install what you want
the first time you run Super.
Version 0.20: January, 2000
Enhancement:
Add support to J2EE Sun-RI.
Change:
1. Replace logging device "file" with "buffer" to be
compliant to EJB 1.1. Your code do not need to change.
Version 0.10: December, 1999
Enhancement:
1. provide SimpleMonitorInterface, so GUI experience is
not necessary for developing most monitoring applications.
2. Sortable table for table based windows by mouse
click (left or right).
Version 0.01 November., 1999:
1. Bug fix: An exception thrown when log file is large.
2. Enhancement: Add tour section in Help information.
Version 0.00: October, 1999
Thanks.

Announcement: Super 1.7 - an EJB/J2EE monitoring tool with
SuperEnvironment
SuperLogging
SuperPeekPoke
SuperStress
has got a new member: SuperReport
You can anomyously down load it free from:
http://www.acelet.com.
Super is a component based administration tool for EJB/J2ee.
It provides built-in functionality as well as
extensions, as SuperComponents. Users can install
SuperComponents onto it, or uninstall them from it.
Super has the following functions:
* A J2EE/EJB monitor.
* A gateway to EJB servers from different vendors.
* A framework holding user defined SuperComponents.
* A PeekPoke tool to read/write attributes from EJBs.
* A full-featured logging/tracing tool for centralized, chronological logging.
* A Stress test tool.
* A global environment tool.
* A report tool.
It is written in pure Java.
The current version support:
* Universal servers.
* Weblogic 5.1, 6.0
* Weblogic 6.1 with EJB 2.
What is new:
Version 1.70 January 2002
Enhancement:
1. SuperLogging: Scope can dynamically change both for upgrade to downgrade (for
weblogic 6.1, need download an application).
2. Add alias names for log threshold as new Java suggests.
3. New component: SuperReport.
Change:
1. SuperLogging: Log database parameters are specified in a properties file, instead
of EJB's deployment descriptor. It is more convenient and it avoids some potential
problems. No change for development, easier for administration.
Bug fix:
1. Add Source Path Panel now accepts both directory and jar file.
2. Bug in SuperEnvironment example (for version 1.60 only).
Version 1.60 December 2001
Enhancement:
1. SuperPeekPoke and SuperStress can use user defined dynamic argument list.
2. Add timeout parameter to logging access.
3. New installation program with A). Easy install. B). Remote command line install.
4. Support EJB 2.0 for Weblogic 6.1.
5. Support SuperPeekPoke, SuperEnvironment and SuperStress for Websphere 4.0 (SuperLogging
was supported since version 1.5).
Change:
1. Poke: argument list is set at define time, not invoke time.
2. Default log database change to server mode from web server mode, booting performance
to 10-20 times.
Bug fix:
1. If the returned object is null, Peek did not handle it correctly.
2. If the value was too big, TimeSeries chart did not handle it correctly. Now
it can handle up to 1.0E300.
3. Help message was difficult to access in installation program.
4. Source code panel now both highlights and marks the line in question (before
it was only highlight using JDK 1.2, not JDK 1.3).
5. Delete an item on PeekPoke and add a new one generated an error.
Version 1.50 August, 2001
Enhancement:
1. Source code level tracing supports EJB, JSP, java helper and other
programs which are written in native languages (as long as you
write correct log messages in your application).
2. Redress supports JSP now.
3. New installation with full help document: hope it will be easier.
4. Support WebSphere 4.0
Version 1.40 June, 2001
Enhancement:
1. Add SuperEnvironment which is a Kaleidoscope with TableView, TimeSeriesView
and PieView for GlobalProperties.
GlobalProperties is an open source program from Acelet.
2. SuperPeekPoke adds Kaleidoscope with TableView, TimeSeriesView and PieView.
Changes:
1. The structure of log database changed. You need delete old installation and
install everything new.
2. The format of time stamp of SuperLogging changed. It is not locale dependent:
better for report utilities.
3. Time stamp of SuperLogging added machine name: better for clustering environment.
Bug fix:
1. Under JDK 1.3, when you close Trace Panel, the timer may not be stopped and
Style Panel may not show up.
Version 1.30 May, 2001
Enhancement:
1. Add ConnectionPlugin support.
2. Add support for Borland AppServer.
Version 1.20 April, 2001
Enhancement:
1. Redress with option to save a backup file
2. More data validation on Dump Panel.
3. Add uninstall for Super itself.
4. Add Log Database Panel for changing the log database parameters.
5. Register Class: you can type in name or browse on file system.
6. New tour with new examples.
Bug fix:
1. Redress: save file may fail.
2. Install Bean: some may fail due to missing manifest file. Now, it is treated
as foreign beans.
3. Installation: Both installServerSideLibrary and installLogDatabase can be worked
on the original file, do not need copy to a temporary directory anymore.
4. PeekPoke: if there is no stub available, JNDI list would be empty for Weblogic5-6.
Now it pick up all availble ones and give warning messages.
5. Stress: Launch>Save>Cancel generated a null pointer exception.
Changes:
1. installLogDatabase has been changed from .zip file to .jar file.
2. SuperLogging: If the log database is broken, the log methods will not try to
access the log database. It is consistent with the document now.
3. SuperLogging will not read system properties now. You can put log database
parameters in SuperLoggingEJB's deployment descriptor.
Version 1.10 Feb., 2001
Enhancement:
1. Re-written PeekPoke with Save/Restore functions.
2. New SuperComponent: SuperStress for stress test.
3. Set a mark at the highlighted line on the Source Code
Panel (as a work-a-round for JDK 1.3).
4. Add support for WebLogic 6.0
Bug fix:
1. Uninstall bean does physically delete the jar file now.
2. WebLogic51 Envoy may not always list all JNDI names. This is fixed.
Version 1.00 Oct., 2000
Enhancement:
1. Support Universal server (virtual all EJB servers).
2. Add Lost and Found for JNDI names, in case you need it.
3. JNDI ComboBox is editable now, so you can PeekPoke not listed JNDI name (mainly
for Envoys which do not support JNDI list).
Version 0.90: Sept, 2000
Enhancement:
1. PeekPoke supports arbitrary objects (except for Vector, Hashtable
and alike) as input values.
2. Reworked help documents.
Bug fix:
1. Clicking Cancel button on Pace Panel set 0 to pace. It causes
further time-out.
2. MDI related bugs under JDK 1.3.
Version 0.80: Aug, 2000
Enhancement:
1. With full-featured SuperLogging.
Version 0.72: July, 2000
Bug fix:
1. Ignore unknown objects, so Weblogic5.1 can show JNDI list.
Version 0.71: July, 2000
Enhancement:
1. Re-worked peek algorithm, doing better for concurent use.
2. Add cacellable Wait dialog, showing Super is busy.
3. Add Stop button on Peek Panel.
4. Add undeploy example button.
Bug fix:
1. Deletion on Peek Panel may cause error under JDK 1.3. Now it works for both
1.2 and 1.3
Version 0.70: July, 2000
Enhancement:
1. PeekPoke EJBs without programming.
Bug fix:
1. Did not show many windows under JDK 1.3. Now it works for both 1.2 and 1.3
Changes:
1. All changes are backward compatible, but you may need to recompile monitor
windows defined by you.
Version 0.61: June, 2000
Bug fix:
1. First time if you choose BUFFER as logging device, message will not show.
2. Fixed LoggingPanel related bugs.
Version 0.60: May, 2000
Enhancement:
1. Add DATABASE as a logging device for persistent logging message.
2. Made alertInterval configurable.
3. Made pace for tracing configurable.
Bug fix:
1. Fixed many bugs.
Version 0.51, 0.52 and 0.53: April, 2000
Enhancement:
1. Add support to Weblogic 5.1 (support for Logging/Tracing and
user defined GUI window, not support for regular monitoring).
Bug fix:
1. Context sensitive help is available for most of windows: press F1.
2. Fix installation related problems.
Version 0.50: April, 2000
Enhancement:
1. Use JavaHelp for help system.
2. Add shutdown functionality for J2EE.
3. Add support to Weblogic 4.5 (support for Logging/Tracing and
user defined GUI window, not support for regular monitoring).
Bug fix:
1. Better exception handling for null Application.
Version 0.40: March, 2000
Enhancement:
1.New installation program, solves installation related problems.
2. Installation deploys AceletSuperApp application.
3. Add deploy/undeploy facilities.
4. Add EJB and application lists.
Change:
1.SimpleMonitorInterface: now more simple.
Version 0.30: January, 2000
Enhancement:
1. Add realm support to J2EE
2. Come with installation program: you just install what you want
the first time you run Super.
Version 0.20: January, 2000
Enhancement:
Add support to J2EE Sun-RI.
Change:
1. Replace logging device "file" with "buffer" to be
compliant to EJB 1.1. Your code do not need to change.
Version 0.10: December, 1999
Enhancement:
1. provide SimpleMonitorInterface, so GUI experience is
not necessary for developing most monitoring applications.
2. Sortable table for table based windows by mouse
click (left or right).
Version 0.01 November., 1999:
1. Bug fix: An exception thrown when log file is large.
2. Enhancement: Add tour section in Help information.
Version 0.00: October, 1999
Thanks.

Trouble installing Creative Cloud Desktop. After running the installer the dock the opens up is blank with a blue dotted loading emblem and will not do anything?????. New member here, thanks for the time.

After running the installer the dock the opens up is blank with a blue dotted loading emblem and will not do anything?????. I attempted to quit the install and restart but it produced the same result. New member here, thanks for the time.

Avanmanandfriends please see Creative Cloud app doesn't open and hangs on spinning progress wheel - http://helpx.adobe.com/creative-cloud/kb/creative-cloud-app-doesnt-open.html which discusses how to resolve your current error.

10/15    PLS-00049: bad bind variable 'NEW.MEMBER'

I have created a view based on 2 tables called member and account which works fine i am then trying to create a trigger to update my member view as
create or replace trigger member_view_update
Instead of update on member_view
for each row
begin
     update member set
     last_name = :new.last_name,
     first_name =:new.first_name,
     manager_number= :new.manager_number,
     title=:new.title,
     address=:new.address,
     telephone_1 =:new.telephone_1,
     post_code=:new.post_code,
     where rowid= :new.member.rowid;
     update account set account_balance=:new.account_balance
     where rowid=:new.account_rowid;
end;
But this has the following errors
LINE/COL ERROR
2/2 PL/SQL: SQL Statement ignored
10/2 PL/SQL: ORA-01747: invalid user.table.column, table.column, or
column specification
10/15 PLS-00049: bad bind variable 'NEW.MEMBER'
View code
Create or replace view member_view as
select member.rowid member_rowid,
member.member_number,last_name, first_name, manager_number, title, telephone_1, address, post_code,
account.rowid account_rowid,
account_balance
from member, account
WHERE MEMBER.MEMBER_NUMBER = ACCOUNT.MEMBER_NUMBER

Hello,
I think that you have to replace
where rowid= :new.member.rowid;By
where rowid= :new.member_rowid;Francois

Can not add a new member to the existing log group.

Dear all,
I just want to multiplex the online redo log to different devices for security reason. I just have one member for each group. So I want to use this command to add a new member.
alter database add logfile member '/u02/oracle/oradata/TEST/redo01.log' to ('/u01/app/oracle/oradata/TEST/redo01.log')
or
alter database add logfile member '/u02/oracle/oradata/TEST/redo01.log' to group 1.
But both commands failed with error pasted below:
ERROR at line 1:
ORA-19510: failed to set size of 102400 blocks for file "/u02/oracle/oradata/TEST/redo01.log" (block size=512)
ORA-27045: unable to close the file
Linux-x86_64 Error: 5: Input/output error
Additional information: 4
Do you know what caused this problem?
Thanks,
Ricky

I just want to multiplex the online redo log to different devices for security reason. I just have one member for each group. So I want to use this command to add a new member.Not a BAD idea.. :)
ERROR at line 1:
ORA-19510: failed to set size of 102400 blocks for file "/u02/oracle/oradata/TEST/redo01.log" (block size=512)
ORA-27045: unable to close the file
Linux-x86_64 Error: 5: Input/output error
Additional information: 4It is running out of space. check the required space on mount point /u02 , if not you can create in another mount point as per your requirement.
THanks

Problem with add new Member in Account Dimension

Hi Expert
I want to add new member in account dimension but occured some Error about a member count of a circular reference. Please help me for solve this error. Thank you so much
Best regards,
Bank

Hi,
This kind of error indicates faulty dimension formulas. There must be at least 2 formulas referencing each other. For example:
1. A=B+C
2. C=A*D
The above 2 formulas are dependent on each other. On one hand, you need C to calculate A. On the other hand, you need A to calculate C. So, causing a cross reference. Try to remove all the dimension formulas in your account dimension and process it. See, if its successful or not. If yes, then the formula was the definite reason. Now, try to add the formula one by one, till you get the error.
Hope this helps.

DRM Error - Adding new member (3317)

I received the following error (#3317) when I tried to add a new member - can anyone please advise on how to fix this problem?
*\\Record #89 - Error adding member ABC12345 (3317)*
*\\Record #89 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.*
*ABC123456789 ABC12345 SAMPLE NAME S +*
Thanks!

The answer lies within the error message itself,
Please check below thread,
Essbase Studio???
and also
http://docs.oracle.com/cd/E12032_01/doc/epm.921/html_errmsgs/aso.htm
-Murali

Business rule (add new member)

Hello!
Is it possible to write a business rule, which adds to the data form (and in the dimension Account) new member, without using the Add Asset (Capex)?

In Essbase, you cannot add metadata dynamically. However, Add Capex is an example of business rules to populate/create block which makes metadata show up on webforms due to suppress missing blocks/rows on.

Object ID not created when adding new member

Hi,
I have 11 Dimension on my application, while i tried to add new member on user define dimension (Location) and on entity dimension. the object id is not created in repository.
i'm using Hyperion Planning 11.1.1.1 what might be the cause and how to fix this?
please help.
Regards,
Ika

Hi John,
this is the error that i've got.
java.sql.SQLException: ORA-06510: PL/SQL: unhandled user-defined exception
ORA-06512: at "APPS.XJM_UPLOAD_SD_PKG", line 494
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:125)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:316)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:282)
     at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:639)
     at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:185)
     at oracle.jdbc.driver.T4CPreparedStatement.execute_for_rows(T4CPreparedStatement.java:633)
     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1086)
     at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:2984)
     at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3057)
     at com.sunopsis.sql.SnpsQuery.executeUpdate(SnpsQuery.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execStdOrders(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSqlS.treatTaskTrt(SnpSessTaskSqlS.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java)
     at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java)
     at com.sunopsis.dwg.cmd.DwgCommandScenario.treatCommand(DwgCommandScenario.java)
     at com.sunopsis.dwg.cmd.DwgCommandBase.execute(DwgCommandBase.java)
     at com.sunopsis.dwg.cmd.e.i(e.java)
     at com.sunopsis.dwg.cmd.e.y(e.java)
     at com.sunopsis.dwg.DwgJv.treatCmd(DwgJv.java)
     at com.sunopsis.dwg.DwgJv.main(DwgJv.java)
     at oracle.odi.Agent.main(Agent.java)
/u01/oracle/TEST/apps/apps_st/appl/xxcust/12.0.0/bin/XXJM_UPLOAD_SDF
Program exited with status 110
after checking the object id for location and entity is not found.

Referring a New Member

Hi ALL,
How to refer new member? and how to get points regarding this?
Regards,
P.Manivannan.

Hi,
Thanks Craig Cmehil
Regards,
P.Manivannan

Why not displayed new member in dimension sap bpc?

Good day guys
I have the following problem:
Add new members to a dimension but not displayed.
example: DIMENSION(inputcurrency) added MEMBER: MXN (Mexican Pesos); when I excel interface I can not see the new member, before this process the dimension and active AppSet.
that could be?
Use SAP BPC 7.5 SP8

Hi Bish,
Without processing a dimension the data should no go to the database. If you modify the the dimension and you want those new members in report you have to process that dimension. And if you save that dimension after modification its save the members in application sever. while retrieving the data it pick up from the database layer not from application layer, So the on fly calculation are stored in application layer( Like conversion files, Transformation files, script logics and Member formulas). So if you want the new members in report you have to process. Its by SAP design it self.
After modification of dimension no need to logoff and login every time. In order to avoid that option we have a anothe solution that is Activate Metadata Cache option.
In order to use that go to EPM--> User OPtions---> Activate metadata Option
You can clear the metadata cache. When the cache is cleared, the structure of the data source you are connected to is synchronized with the structure copied locally; which means that the members of dimensions that have been added, modified or deleted in the data source are loaded.
For more details related to Metadata option go to the EPM 10 Office Addin User Guide document which is available in google free of cost
Regards,
Saida Reddy G

New Member introduction

Similar Messages

Maybe you are looking for