Best practice for "Portal Appplication in Maintenance"message ?

Hi,
I was wondering how you deal with portal applications that go "in maintenance". We now have multiple application area's (HR/PM/CO) integrated in our portal with own developed applications and I was wondering what the best option is if not the entire portal (for portal maintenance) goes down, but you just want to show for example a message "portal application down for maintenance" only for a certain application in the portal
- Do you change the role in which the application under maintenance is and assign it a page with the 'maintenance message'
Regards,
Igor

Hi
in our framework, each application on the back end system (SAP) posess 'running' state that is either true or false.
All application iview check the state of their respoective application, and display a logo and message where the app is not running.
thus, no change in the portal if part of the application is in maintenance.
in addition, administrator possess a Iview that allows changing the state of an application.
we're currently discussing changing the state to a tri-state (running, will-be-closed, closed), to allows more flexibility.
regards,
Guillaume Patry

Similar Messages

Best Practice for Portal Patches and effort estimation

Hi ,
One of our client is applying the following patches
1. ECC 6.0 SP15(currently SP14)
2. ESS MSS SP15(currently SP14 with some level of functional customization )
3. EP 7 SP18(currently SP14)
We would like to kwow the best practice for applying portal patches and the effort estimation for redoing the portal devt on the new patch.
o   What is the overall level of effort with applying Portal patches?
o   How are all the changes to SAP objects handle? Do they have to be
     manually re-entered?
o What is the impact of having a single NWDI instance across the
    Portal Landscape during the Patch process?
Regards,
Revathi Raju.

Hi Revathi,
o What is the overall level of effort with applying Portal patches?
overall effort to apply the patch is apprx 1/2-1 days for NW7 system. This is exclude the patch files download because it's based on your download speed.
o How are all the changes to SAP objects handle? Do they have to be
manually re-entered?
Depending on your customization. Normally it wont effect if you created the customzation application apart from SAP standard application
o What is the impact of having a single NWDI instance across the
Portal Landscape during the Patch process?
Any change that related to NWDI, you might be need to re-deployed from NWDI itself.
Thanks
Regards,
AZLY

Best Practices For Portal Content Objects Transport System

Hi All,
I am going to make some documentation on Transport Sytem for Portal content objects in Best Practices.
Please help in out and send me some documents related to SAP Best Practices for transport for Portal Content Objects.
Thanks,
Iqbal Ahmad
Edited by: Iqbal Ahmad on Sep 15, 2008 6:31 PM

Hi Iqbal,
Hope you are doing good
Well, have a look at these links.
http://help.sap.com/saphelp_nw04/helpdata/en/91/4931eca9ef05449bfe272289d20b37/frameset.htm
This document, gives a detailed description.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f570c7ee-0901-0010-269b-f743aefad0db
Hope this helps.
Cheers,
Sandeep Tudumu

Best practice for RAC planned downtime maintenance?

I have a 3 node RAC on Linux redhat. DB version is 11gr2.
I want to know the steps to perform each node OS patch upgrade.
I want to be sure I did right steps:
1). Node 1, stop crs and do the OS patch upgrade.
2). same steps for Node 2, 3.
Is this right?
Thank you for any help.

user569151 wrote:
I have a 3 node RAC on Linux redhat. DB version is 11gr2.
I want to know the steps to perform each node OS patch upgrade.
I want to be sure I did right steps:
1). Node 1, stop crs and do the OS patch upgrade.
2). same steps for Node 2, 3.
If your RAC environment is configured properly follow this step:
Node 1:
* Relocate services to node 2 or 3 and stop database instance and service using SRVCTL
* Stop Clusterware using CRSCTL
* Disable automatic Startup of Clusterware on this node using CRSCTL
* Patch your OS
* Relink Oracle Binaries (Grid Infrastructure/Oracle Database) (P.S You will need unlock and re-lock your Grid Home to relink binaries see note RAC: Frequently Asked Questions [ID 220970.1])
If you are using ACFS you must check if that OS Upgrade will affect ACFS drivers (ACFS Supported On OS Platforms. [ID 1369107.1])
* Enable Automatic Startup of Clusterware on this node using CRSCTL
* Start Clusterware using CRSCTL
* Start Database and Services with SRVCTL
Repeat steps above on Node 2 and 3
Of course don't forget a good plan to backup and recovery to support case of failure.
http://docs.oracle.com/cd/E11882_01/server.112/e17157/planned.htm#CJACDIJD
Is It Necessary To Relink Oracle Following OS Upgrade? [ID 444595.1]
My concern is here, let's say each node has to be restarted.
So my procedure should be on 1st node: crsctl stop crs to stop everything and failover everything to other nodes.
I wonder crsctl stop crs will cause ASM instance to be down?Yes "CRSCTL STOP CRS" will try stop all clusterware resource with clean state. If any problem occurs will be raised on your prompt.
Regards,
Levi Pereira
Edited by: Levi Pereira on Nov 1, 2012 7:35 PM

Best practice for using messaging in medium to large cluster

What is the best practice for using messaging in medium to large cluster In a system where all the clients need to receive all the messages and some of the messages can be really big (a few megabytes and maybe more)
I will be glad to hear any suggestion or to learn from others experience.
Shimi

publish/subscribe, right?
lots of subscribers, big messages == lots of network traffic.
it's a wide open question, no?
%

Noticing a lot of database index fragmentation yet no Health Analyzer alerts...? Best practice for database maintenance in 2013?

Could someone point me to a document for best practices for database maintenance with SharePoint 2013? I have read the 2010 document, but I'm hoping their is an updated one that I'm just missing.
My problem is that our DBA recently noticed that many of our SharePoint databases have high index fragmentation. I have the Health Analyzer rules enabled for index fragmentation and they run daily, but I've never received an alert despite the majority
of our databases having greater than 40% fragmentation and some are even above 95%.
Obviously it has our attention now and we want to get this addressed. My understanding (which I now fear is at best incomplete, more likely just plain wrong) was that a maintenance plan wasn't needed for index fragmentation in 2010/2013 like it was
in 2007.
Thanks,
Troy

It depends. Here are the rules for that job:
Sampled mode
Page count >24 and avg fragmentation in percent >5
Or
Page count >8 avg page space used in percent < fill_factor * 0.9 (Fill Factor in SharePoint 2013 varies from 80 to 100 depending on the index, it is important not to adjust index fill factors)
I have seen cases where the indexes are not automatically managed by the rule and require a manual defragmentation with a Full Scan, instead of Sampled. Once the Full Scan defrag completed, the timer job started handling the index fragmentation automatically.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

What's best practice for logging messages in pageflow?

What's best practice for logging messages in pageflow?
Workshop complains when I try to use a Log4J logger by saying it's not serializable. Is there a context similar to JWSContext that you can get a logger from?
There seems to be a big hole in the documentation on debug logging in workflows and JSP pages.
thanks,
Rodger...

Make the configuration change in setDomainEnv.cmd. Find where the following variable is set:
LOG4J_CONFIG_FILE
and change it to your desired path.
In your Global.app class, instantiate a static Logger like this:
transient static Logger logger = Logger.getLogger(Global.class);
You should be logging now as long as you have the categories and appenders configured properly in your log4j.xml file.

Business Package for SAP Best Practices for Enterprise Portal

Hi,
We are implementing EP for ECC 5.0 and we have to web enable some FI transactions like FB50/fb60 etc. We want to use standard business package for this. The only business package that caters this requirement is "Business Package for SAP Best Practices for Enterprise Portal 60.1". When i checked the data source for this business package, the specification is for "SAP R/3 4.6B and above". Does this work for ECC 5.0 as well? In general does the R/3 specific business packages work for ECC versions? Please let me know. Thanks for the help. I promise rewards.
Regards
Hari

Hari,
When you download the BPO via Portal Content Portfolio,
each bpo has additional information on the release.
For example for the one you are inquiring about - Business Package for SAP Best Practices for Enterprise Portal, the additional release information is provided on the following links;
https://www2.iviewstudio.com/sdn/info/index.cfm?action=faqs&part=#QSR03
https://www2.iviewstudio.com/sdn/detail_view/index.cfm?action=package_information&CatalogSet=SAP%20Content&ItemID=17212&CFID=7544845&CFTOKEN=99283970
Regards,
James

Best Practices for standardizing long text for EP GUI version

Hello, I have a question that is related to standardizing best practices for all portal applications that use EP
1) The portal team has recommended activating the GUI version from portal to allow the long text to have the same features as the standard GUI. Since this solution is per transaction, we will need to identify what transactions need to have this temporary solution built in. Also, business users will need to remember which transactions they will access via portal or GUI.
(2) Even though the long text function is activated via GUI per transaction, the system will prompt a message of u201CRuntime Error! Program C:\Program Files\Microsoft Office\OFFICE11\WINWORD.EXEu201D. This may create frustrations to the users each time they maintain the long text. The risk of this may be losing the use of long text throughout the maintenance orders, production orders, notifications, material masters, equipment masters, maintenance task lists, production routings, etc.
All feedback welcomed
Thanks Mark

I found the solution, make everything in Illustrator (well text anyway) at a big size then bring it ibto Photoshop in a dicument 1024 x 576 (so no widescreen pixel ratio) then when saving document bring size of Image to 720 x 576 then you get great anti aliased pictures.
Solved.

BEST PRACTICES FOR CREATING DISCOVERER DATABASE CONNECTION -PUBLIC VS. PRIV

I have enabled SSO for Discoverer. So when you browse to http://host:port/discoverer/viewer you get prompted for your SSO
username/password. I have enabled users to create their own private
connections. I log in as portal and created a private connection. I then from
Oracle Portal create a portlet and add a discoverer worksheet using the private
connection that I created as the portal user. This works fine...users access
the portal they can see the worksheet. When they click the analyze link, the
users are prompted to enter a password for the private connection. The
following message is displayed:
The item you are requesting requires you to enter a password. This could occur because this is a private connection or
because the public connection password was invalid. Please enter the correct
password now to continue.
I originally created a public connection...and then follow the same steps from Oracle portal to create the portlet and display the
worksheet. Worksheet is displayed properly from Portal, when users click the
analyze link they are taken to Discoverer Viewer without having to enter a
password. The problem with this is that when a user browses to
http://host:port/discoverer/viewer they enter their SSO information and then
any user with an SSO account can see the public connection...very insecure!
When private connections are used, no connection information is displayed to
SSO users when logging into Discoverer Viewer.
For the very first step, when editing the Worksheet portlet from Portal, I enter the following for Database
Connections:
Publisher: I choose either the private or public connection that I created
Users Logged In: Display same data to all users using connection (Publisher's Connection)
Users Not Logged In: Do no display data
My question is what are the best practices for creating Discoverer Database
Connections.
Is there a way to create a public connection, but not display it in at http://host:port/discoverer/viewer?
Can I restrict access to http://host:port/discoverer/viewer to specific SSO users?
So overall, I want roughly 40 users to have access to my Portal Page Group. I then want to
display portlets with Discoverer worksheets. Certain worksheets I want to have
the ability to display the analyze link. When the SSO user clicks on this they
will be taken to Discoverer Viewer and prompted for no logon information. All
SSO users will see the same data...there is no need to restrict access based on
SSO username...1 database user will be set up in either the public or private
connection.

You can make it happen by creating a private connection for 40 users by capi script and when creating portlet select 2nd option in Users Logged in section. In this the portlet uses there own private connection every time user logs in.
So that it won't ask for password.
Another thing is there is an option of entering password or not in ASC in discoverer section, if your version 10.1.2.2. Let me know if you need more information
thnaks
kiran

BI Best Practice for Chemical Industry

Hello,
I would like to know if anyone is aware of SAP BI Best Practice for Chemicals.And if so can anyone please post a link aswell.
Thanks

Hi Naser,
Below information will helps you in detail explanation regarding Chemical industry....
SAP Best Practices packages support best business practices that quickly turn your SAP ERP application into a valuable tool used by the entire business. You can evaluate and implement specific business processes quickly u2013 without extensive Customization of your SAP software. As a result, you realize the benefits with less Effort and at a lower cost than ever before. This helps you improve operational efficiency while providing the flexibility you need to be successful in highly demanding markets. SAP Best Practices packages can benefit companies of all sizes, including global enterprises creating a corporate template for their subsidiaries.
Extending beyond the boundaries of conventional corporate divisions and functions, the SAP Best Practices for Chemicals package is based on SAP ERP; the SAP Environment, Health & Safety (SAP EH&S) application; and the SAP Recipe Management application. The business processes supported by SAP Best Practices for Chemicals encompass a wide range of activities typically found in a chemical industry
Practice:
u2022 Sales and marketing
u2013 Sales order processing
u2013 Presales and contracts
u2013 Sales and distribution (including returns, returnables, and rebates, with quality management)
u2013 Inter- and intracompany processes
u2013 Cross-company sales
u2013 Third-party processing
u2013 Samples processing
u2013 Foreign trade
u2013 Active-ingredient processing
u2013 Totes handling
u2013 Tank-trailer processing
u2013 Vendor-managed inventory
u2013 Consignment processing
u2013 Outbound logistics
u2022 Supply chain planning and execution Supply and demand planning
u2022 Manufacturing planning and execution
u2013 Manufacturing execution (including quality management)
u2013 Subcontracting
u2013 Blending
u2013 Repackaging
u2013 Relabeling
u2013 Samples processing
u2022 Quality management and compliance
u2013 EH&S dangerous goods management
u2013 EH&S product safety
u2013 EH&S business compliance services
u2013 EH&S industrial hygiene and safety
u2013 EH&S waste management
u2022 Research and development Transformation of general recipes
u2022 Supplier collaboration
u2013 Procurement of materials and services (Including quality management)
u2013 Storage tank management
u2013 E-commerce (Chemical Industry Data Exchange)
u2022 Enterprise management and support
u2013 Plant maintenance
u2013 Investment management
u2013 Integration of the SAP NetWeaver Portal component
u2022 Profitability analysis
More Details
This section details the most common business scenarios u2013 those that benefit most from the application of best practices.
Sales and Marketing
SAP Best Practices for Chemicals supports the following sales and marketingu2013related business processes:
Sales order processing u2013 In this scenario, SAP Best Practices for Chemicals supports order entry, delivery, and billing. Chemical industry functions include the following:
u2022 Triggering an available-to-promise (ATP) inventory check on bulk orders after sales order entry and automatically creating a filling order (Note: an ATP check is triggered for packaged material.)
u2022 Selecting batches according to customer requirements:
u2022 Processing internal sales activities that involve different organizational units
Third-party and additional internal processing u2013 In this area, the SAP Best Practices for Chemicals package provides an additional batch production step that can be applied to products previously produced by either continuous or batch processing. The following example is based on further internal processing of plastic granules:
u2022 Purchase order creation, staging, execution, and completion
u2022 In-process and post process control
u2022 Batch assignment from bulk to finished materials
u2022 Repackaging of bulk material
SAP Best Practices for Chemicals features several tools that help you take advantage of chemical industry best practices. For example, it provides a fully documented and reusable prototype that you can turn into a productive solution quickly. It also provides a variety of tools, descriptions of business scenarios, and proven configuration of SAP software based on more than 35 years of working with the
Chemical industry.
SAP Functions in Detail u2013 SAP Best Practices for Chemicals
The package can also be used to support external toll processing such as that required for additional treatment or repackaging.
Tank-trailer processing u2013 In this scenario, SAP Best Practices for Chemicals helps handle the selling of bulk material, liquid or granular. It covers the process that automatically adjusts the differences between the original order quantities and the actual quantities filled in the truck. To determine the quantity actually filled, the tank trailer is weighed before and after loading. The delta weight u2013 or quantity filled u2013 is transmitted to the SAP software via an order confirmation. When the delivery for the sales order is created, the software automatically adjusts the order quantity with the confirmed filling quantity.The customer is invoiced for the precise quantity filled and delivered.
Supply Chain Planning and Execution
SAP Best Practices for Chemicals supports supply chain planning as well as supply chain execution processes:
Supply and demand planning u2013 Via the SAP Best Practices for Chemicals package, SAP enables complete support for commercial and supply-chain processes in the chemical industry, including support for integrated sales and operations planning, planning strategies for bulk material, and a variety of filling processes with corresponding packaging units. The package maps the entire supply chain u2013 from sales planning to material requirements planning to transportation procurement.
Supplier Collaboration
In the procurement arena, best practices are most important in the following
Scenario:
Procurement of materials and services:
In this scenario, SAP Best Practices for Chemicals describes a range of purchasing processes, including the following:
u2022 Selection of delivery schedules by vendor
u2022 Interplant stock transfer orders
u2022 Quality inspections for raw materials, including sampling requests triggered
by goods receipt
Manufacturing Scenarios
SAP Best Practices for Chemicals supports the following sales and
Manufacturingu2013related business processes:
Continuous production u2013 In a continuous production scenario, SAP Best Practices for Chemicals typifies the practice used by basic or commodity chemical producers. For example, in the continuous production of plastic granules, production order processing is based on run-schedule headers. This best-practice package also describes batch and quality management in continuous production. Other processes it supports include handling of byproducts,co-products, and the blending process.
Batch production u2013 For batch production,
SAP Best Practices for Chemicals typifies the best practice used by specialty
chemical producers. The following example demonstrates batch production
of paint, which includes the following business processes:
u2022 Process order creation, execution, and completion
u2022 In-process and post process control
u2022 Paperless manufacturing using XMLbased Process integration sheets
u2022 Alerts and events
u2022 Batch derivation from bulk to finished materials
Enterprise Management and Support
SAP Best Practices for Chemicals also supports a range of scenarios in this
area:
Plant maintenance u2013 SAP Best Practices for Chemicals allows for management
of your technical systems. Once the assets are set up in the system, it focuses on preventive and emergency maintenance. Tools and information support the setup of a production plant with assets and buildings.Revenue and cost controlling u2013 The package supports the functions that help you meet product-costing requirements in the industry. It describes how cost centers can be defined, attached
to activity types, and then linked to logistics. It also supports costing and settlement of production orders for batch and continuous production. And it includes information and tools that help you analyze sales and actual costs in a margin contribution report.
The SAP Best Practices for Chemicals package supports numerous integrated
business processes typical of the chemical industry, including the following:
u2022 Quality management u2013 Supports integration of quality management concepts across the entire supplychain (procurement, production, and sales), including batch recall and complaint handling
u2022 Batch management u2013 Helps generate batches based on deliveries from vendors or because of company production or filling, with information and tools for total management of batch production and associated processes including batch derivation, batch information cockpit, and a batchwhere- used list
u2022 Warehouse management u2013 Enables you to identify locations where materials
or batch lots are stored, recording details such as bin location and other storage information on dangerous goods to help capture all information needed to show compliance with legal requirements
Regards
Sudheer

Best-practice for Catalog Views ? :|

Hello community,
A best practice question:
The situtation: I have several product categories (110), several items in those categories (4000) and 300 end-users. I would like to know which is the best practice for segment the catalog. I mean, some users should only see categories 10,20 & 30. Other users only category 80, etc. The problem is how can I implement this ?
My first idea is:
1. Create 110 Procurement Catalogs (1 for every prod.category). Each catalog should contain only its product category.
2. Assign in my Org Model, in a user-level all the "catalogs" that the user should access.
Do you have any idea in order to improve this ?
Saludos desde Mexico,
Diego

Hi,
Your way of doing will work, but you'll get maintenance issues (to many catalogs, and catalog link to maintain for each user).
The other way is to built your views in CCM, and assign these views to the users, either on the roles (PFCG) or on the user (SU01). The problem is that with CCM 1.0 this is limitated, cause you'll have to assign one by one the items to each view (no dynamic or mass processes), it has been enhanced in CCM 2.0.
My advice:
-Challenge your customer about views, and try to limit the number of views, with for example strategic and non strategic
-With CCM 1.0 stick to the procurement catalogs, or implement BADIs to assign items to the views (I experienced it, it works, but is quite difficult), but with a limitated number of views
Good luck.
Vadim

Best Practices for Defining NDS Java Projects...

We are doing a Proof of Concept on using NDS to develop non-SAP Java applications. We are attempting to determine if we can replace our current Java development tools with NDS/WAS.
We are struggling with SAP's terminology and "plumbing" for setting up/defining Java projects. For example, what is and when do you define Tracks, Software Components, Development Components, etc. All of these terms are totally foreign to us and do not relate to our current Java environment (at least not that we can see). We are also struggling with how the DTR and activities tie in to those components.
If any one has defined best practices for setting up Java projects or has struggled with and overcome these same issues, please provide us with some guidance. This is a very frustrating and time-consuming issue for us.
Thank you!!

Hi Peggy,
In Component Model we divide software projects into small components.Components can use other components in well defined manner.
A development object is a part of a component that can be changed or developed in some way; it provides the component with a certain part of its functionality. A development object may be a Java class, a Web Dynpro view, a table definition, a JSP page, and so on. Development objects are always stored as sources in a repository.
A development component can be defined as a frame shared by a number of objects, which are part of the software.
Software components combine components (DCs) to larger units for delivery and deployment.
A track comprises configurations and runtime systems required for developing software component versions.It ensures stable states of deliverables used by subsequent tracks.
The Design Time Repository is for versioning source code management. Distributed development of software in teams. Transport and replication of sources.
You can also find lot of support in SDN for the above concepts with tutorials.
Refer this Link for a overview on Java development Infrastructure(JDI)
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webas/java/java development infrastructure jdi overview.pdf
To understand further
Working with Net Weaver Development Infrastructure :
http://help.sap.com/saphelp_nw04/helpdata/en/03/f6bc3d42f46c33e10000000a11405a/content.htm
In the above link you can find all the concepts clearly explained.You can also find the required tutorials for development.
Regards,
Vijith

Best Practices for Workshop IDE (Development Workstation Setup)

Is there any Oracle documentation that describes best practices for setting up Workshop and developing on a workstation that includes Oracle's ODSI, OSB, Portal, and WLI? We are using all these products on a weblogic server for each developer's machine and experiencing performance and reliability issues. What's the optimal way to use these products on a developer's workstation. Thanks.

Hi,
Currently you dont see such best practice site with in workshop.
but you can verify most issues from doc.
http://docs.oracle.com/cd/E13224_01/wlw/docs103/
if you need any further assistance let me know.
Regards,
Kal

Best Practice for External Libraries Shared Libraries and Web Dynrpo

Two blogs have been written on sharing libraries with Web Dynpro DC, but I would
like to know the best practice for doing this.
External libraries seem to work great at compile time, but when deploying there is often an error related to the external library not being a deployed component.
Is there a workaround for this besides creating a shared J2EE library which I have been able to get working? I am not interested in something that works, but really
what are the best practice for this. What is the best way to limit the number of jars that need to be kept in a shared library/ext library. When is sharing ref service/etc a valid approach vs. hunting down the jars in the portal libraries etc and storing in an external library.

Security is mainly about mitigation rather than 100% secure, "We have unknown unknowns". The component needs to talk to SQL Server. You could continue to use http to talk to SQL Server, perhaps even get SOAP Transactions working but personally
I'd have more worries about using such a 'less trodden' path since that is exactly the areas where more security problems are discovered. I don't know about your specific design issues so there might be even more ways to mitigate the risk but in general you're
using a DMZ as a decent way to mitigate risk. I would recommend asking your security team what they'd deem acceptable.
http://pauliom.wordpress.com

Best practice for "Portal Appplication in Maintenance"message ?

Similar Messages

Maybe you are looking for