Differences in means of deployment

Hi Everyone,
Could i know what is the difference between deploying through NWDS and SDM.Why are we using NWDI.
Why are we using NWDI for business packages as a compulsion.
Thanks in advance..

Hi,
NWDS is a development environment, at if you for example deploy webdynpro application it again connects to SDM on the server to deploy.
So we just have helper tool on NWDS to deploy on server, but any way these helper tools will anyway use the tools on server to deploy.
It is not a must to use NWDI to develop business packages, I developed a business packages which only has par file, there we need no NWDI at all. So it depends what you are developing, if you develop DC's then you need NWDI.
Using NWDI you have a sourcecontrol in it which also helps people to work in teams and not overwrite each others code.
So it all depends on what you are doing.
Regards,
Praveen Gudapati

Similar Messages

What does this mean? (deployment problem)

Error: Transaction attributes must be specified for the method defined in the home interface[....Home ]. Method [create] has no transaction attributedefined with in this bean [....Bean].
What does this error means?
I already have this method in my Home class
public Car create (String carId, String VRN)
throws RemoteException, CreateException, MissingPrimaryKeyException;
and this method in Bean class
public String ejbCreate (String carId, String VRN)
throws CreateException, MissingPrimaryKeyException {
//create

if you are using deployment tool in j2ee jdk 1.4, it will generate the descriptor for you.
I think you miss this in ejb-jar.xml
<container-transaction>
<method>
<ejb-name>AccountBinEJB</ejb-name>
<method-intf>Home</method-intf>
<method-name>create</method-name>
<method-params>
<method-param>java.lang.String</method-param>
<method-param>java.lang.String</method-param>
<method-param>java.lang.String</method-param>
</method-params>
</method>
<trans-attribute>NotSupported</trans-attribute>
</container-transaction>
// Notice on the line with trans-attribute

What is the best methodology to handle database schema changes after an application has been deployed?

Hi,
VS2013, SQL Server 2012 Express LocalDB, EF 6.0, VB, desktop application with an end user database
What is a reliable method to follow when there is a schema change for an end user database used by a deployed application? In other words, each end user has their own private data, but the database needs to be expanded for additional features, etc.
I list here the steps it seems I must consider. If I've missed any, please also inform:
(1) From the first time the application is installed, it should have already moved all downloaded database files to a separate known location, most likely some sub-folder in <user>\App Data.
(2) When there's a schema change, the new database file(s) must also be moved into the location in item (1) above.
(3) The application must check to see if the new database file(s) have been loaded, and if not, transfer the data from the old database file(s) to the new database file(s).
(4) Then the application can operate using the new schema.
This may seem basic, but for those of us who haven't done it, it seems pretty complicated. Item (3) seems to be the operative issue for database schema changes. Existing user data needs to be preserved, but using the new schema. I'd like
to understand the various ways it can be done, if there are specific tools created to handle this process, and which method is considered best practice.
(1) Should we handle the transfer in a 'one-time use' application method, i.e. do it in application code.
(2) Should we handle the transfer using some type of 'one-time use' SQL query. If this is the best way, can you provide some guidance if there are different alternatives for how to perform this in SQL, and where to learn/see examples?
(3) Some other method?
Thanks.
Best Regards,
Alan

Hi Uri,
Thank you kindly for your response. Also thanks to Kalman Toth for showing the right forum for such questions.
To clarify the scenario, I did not mean to imply the end user 'owns' the schema. I was trying to communicate that in my scenario, an end user will have loaded their own private data into the database file originally delivered with the application.
If the schema needs to be updated for new application features, the end user's data will of course need to be preserved during the application upgrade if that upgrade includes a database schema change.
Although I listed step 3 as transferring the data, I should have made more clear I was trying to express my limited understanding of how this process "might work", since at the present time I am not an expert with this. I suspected my thinking
is limited and someone would correct me.
This is basically the reason for my post; I am hoping an expert can point me to what I need to learn about to handle database schema changes when application upgrades are deployed. For example, if an SQL script needs to be created and deployed
then I need to learn how to do that. What's the best practice, or most reliable/efficient way to make sure the end user's database is changed to the new schema after the upgraded application is deployed? Correct me if I'm wrong on this,
but updating the end user database will have to be handled totally within the deployment tool or the upgraded application when it first starts up.
If it makes a difference, I'll be deploying application upgrades initially using Click Once from Visual Studio, and eventually I may also use Windows Installer or Wix.
Again, thanks for your help.
Best Regards,
Alan

UV-SO when partitioned and deployed

Hi there,
I have a question related to User-Visible Service
Object(UV-SO) when partitioned and deployed.
According to TechNote 9674:Service Object Visibility,
"if a partition only contains UV-SOs, there will be
one of these partitions per user". This means, if a
partition only contains a UV-SO, this UV-SO is reachable
outside its partition.
I did some tests. I let an EV-SO call a UV-SO. When I
ran it in partition workshop(EV-SO and UV-SO are in
separate server partitions), I got exception raised
complaining "Cannot resolve the distributed reference
for the UV-SO". Then I deployed this project with the
same partition configuration, and it works without any
error. It looks like there is difference between
partitioning and deploying. What the TechNote(9674)
mentions is correct for deployment, but not for
partition workshop.
Does anybody have any idea about this?

It would appear that the error has now been corrected. There were three things I changed: the startup.aliases file in the startup directory on the target (home:/lvuser/natinst/bin) had "localhost" set as the alias for the controller. I changed this to the controller's IP address. Next, I had some file I/O functions in my RT application which used paths relative to the path obtained with the "Current VI's Path" VI. As this path changes depending on location / execution system, I had to create a VI which used the Application:Kind property with a case structure to appropriately strip / build the desired data file paths regardless of execution system. This may have broken my RT application. Finally, I had a property node in one of my RT SubVIs which attempted to modify an indicator in the SubVI, which is not supported in a compiled RT executable. I may have done this for debugging purposes somewhere along the way, but in any case, I removed it, and after recompiling and deploying the RT executable, everything seems to be working as intended now. The host VI on the desktop computer can connect to the RT application through the project, and when compiled into an executable, that works too.

Difference between Solution manager and ASAP

Hi All,
Can anyone tell me what's the difference between SAP solution manager and ASAP?
Regards
Saroj

ASAP stands For Accelerated SAP........its a SAP implementation methodology. It consists of Five phases---
1. Project Preparation
2. Business Blueprint
3. Realization phase
4. Final preparation phase
5. Go live and Support
For Solution manager u can follow this link:
http://www.sap.com/services/pdf/BWP_SB_SAP_Solution_Manager.pdf
ASAP and Solution Manager are tools used for managing SAP implementation and roll out project. Both supports sevral stages of the project as mention by Raj.
The main Difference between three tools (ASAP, VSAP and Solution Manager) are as follow:
ASAP:
- Offline CD set with tools, content and a methodology for component-based implementation projects
VSAP:
- Offline CD set with tools, content and methodologies for Evaluation, Implementation and Continuous Business Improvement
- ASAP CD set is used as a tool platform. ASAP content is included to cover the implementation phase
Solution Manager:
- Onsite platform to support key implementation actitivities
- Including key ASAP concepts and tool features
- Enhanced concepts to encompass the specifics of mySAP.com implementations
- Integrated platform to support Implementation and operation of mySAP.com
- Solution Manager is server based tool.
More informaiton you can find from the following links:
ValueSAP : https://www.service.sap.com/valuesapupdates
Solution Manager: http://service.sap.com/solutionmanager
some documents what is the duty of asap and solution manager i think with u can understand the difference.
asap means,
ASAP
ASAP stands for Accelerated SAP. Its purpose is to help design SAP implementation in the most efficient
manner possible. Its goal is to effectively optimize time, people, quality and other resources, using a proven
methodology to implementation.
ASAP focuses on tools and training, wrapped up in a five-phase process oriented roadmap for guiding
implementation.
The road map is composed of five well-known consecutive phases:
Phase 1 Project Preparation
Phase 2 Business Blueprint
Phase 3 Realization
Phase 4 Final Preparation
Phase 5 Go-Live and support
In today's post we will discuss the first phase.
Phase 1 : Project Preparation
Phase 1 initiates with a retrieval of information and resources. It is an important time to assemble the
necessary components for the implementation. Some important milestones that need to be accomplished
for phase 1 include
Obtaining senior-level management/stakeholder support
identifying clear project objectives
architecting an efficient decision-making process
creating an environment suitable for change and re-engineering
building a qualified and capable project team.
Senior level management support:
One of the most important milestones with phase 1 of ASAP is the full agreement and cooperation of the
important company decision-makers - key stakeholders and others. Their backing and support is crucial for a
successful implementation.
Clear project objectives:
be concise in defining what your objectives and expectations are for this venture. Vague or unclear notions of
what you hope to obtain with SAP will handicap the implementation process. Also make sure that your
expectations are reasonable considering your company's resources. It is essential to have clearly defined
ideas, goals and project plans devised before moving forward.
An efficient decision making process:
One obstacle that often stalls implementation is a poorly constructed decision-making process. Before
embarking on this venture, individuals need to be clearly identified. Decide now who is responsible for
different decisions along the way. From day one, the implementation decision makers and project leaders
from each area must be aware of the onus placed on them to return good decisions quickly.
Environment suitable for change and re engineering:
Your team must be willing to accept that, along with new SAP software, things are going to change, the
business will change, and information technology enabling the business will change as well. By
implementing SAP, you will essentially redesign your current practices to model more efficient or predefined
best business practices as espoused by SAP. Resistance to this change will impede the progress of your
implementation.
Building a qualified project team:
Probably the most important milestone early in assembling a project team for the implementation. If you are
implementing the materials management and plant maintenance modules, you need to include people from
both of these departments. The team should also represent management as well as non management or
"functional" personnel. Sometimes management is less aware of the day-to-day functions of an organization,
including how implementing SAP will tactically influence those function
ASAP- Second Phase- Business Blueprint
SAP has defined a business blueprint phase to help extract pertinent information about your company that is
necessary for implementation. These blueprints are in the form of questionnaires that are designed to probe
for information that uncovers how your company does business. As such, they also serve to document the
implementation. Each business blueprint document essentially outlines your future business processes and
business requirements. The kinds of questions asked are germane to the particular business function, as
seen in the following sample questions:
1) What information do you capture on a purchase order?
2) What information is required to complete a purchase order?
Accelerated SAP question and answer database:
The question and answer database (QADB) is a simple although aging tool designed to facilitate the creation
and maintenance of your business blueprint. This database stores the questions and the answers and
serves as the heart of your blue print. Customers are provided with a customer input template for each
application that collects the data. The question and answer format is standard across applications to
facilitate easier use by the project team.
Issues database:
Another tool used in the blueprinting phase is the issues database. This database stores any open concerns
and pending issues that relate to the implementation. Centrally storing this information assists in gathering
and then managing issues to resolution, so that important matters do not fall through the cracks. You can
then track the issues in database, assign them to team members, and update the database accordingly.
ASAP Phase- 3 - Realization:
With the completion of the business in phase 2, "functional" experts are now ready to begin configuring SAP.
The Realization phase is broken in to two parts.
1) Your SAP consulting team helps you configure your baseline system, called the baseline configuration.
2) Your implementation project team fine-tunes that system to meet all your business and process
requirements as part of the fine tuning configuration.
The initial configuration completed during the base line configuration is based on the information that you
provided in your blueprint document. The remaining approximately 20% of your configuration that was not
tackled during the baseline configuration is completed during the fine tuning configuration. Fine tuning
usually deals with the exceptions that are not covered in baseline configuration. This final bit of tweaking
represents the work necessary to fit your special needs.
Configuration Testing:
With the help of your SAP consulting team, you segregate your business processes into cycles of related
business flows. The cycles serve as independent units that enable you to test specific parts of the business
process. You can also work through configuring the SAP implementation guide (IMG). A tool used to assist
you in configuring your SAP system in a step-by-step manner.
Knowledge Transfer:
As the configuration phase comes to a close, it becomes necessary for the Project team to be self-sufficient
in their knowledge of the configuration of your SAP system. Knowledge transfer to the configuration team
tasked with system maintenance (that is, maintenance of the business processes after Go-live) needs to be
completed at this time.
In addition, the end users tasked with actually using the system for day-to-day business purposes must be
trained.
ASAP Methodology - Phase 4 - Final Preparation:
As phase 3 merges into phase 4, you should find yourselves not only in the midst of SAP
training, but also in the midst of rigorous functional and stress testing. Phase 4 also
concentrates on the fine tuning of your configuration before Go-live and more importantly, the
migration of data from your old system or systems to SAP.
Workload testing (including peak volume, daily load, and other forms of stress testing), and
integration or functional testing are conducted to ensure the accuracy of your data and the
stability of your SAP system. Because you should have begun testing back in phase 2, you do
not have too far to go until Go-live. Now is an important time to perform preventative
maintenance checks to ensure optimal performance at your SAP system.
At the conclusion of phase 4, take time to plan and document a Go-live strategy. Preparation for
Go-live means preparing for your end-users questions as they start actively working on the new
SAP system.
ASAP - Phase 5 - Go-live and Support:
The Go-live milestone is itself is easy to achieve; a smooth and uneventful Go-live is another
matter altogether. Preparation is the key, including attention to what-if scenarios related not only
to the individual business processes deployed but also to the functioning of technology
underpinning these business processes and preparation for ongoing support, including
maintenance contracts and documented processes and procedures are essential
solutionmanager means,
SAP Solution Manager
Purpose
The SAP Solution Manager supports you throughout the entire lifecycle of your solutions, from the Business Blueprint thru configuration to production operation. It provides central access to tools methods and preconfigured content, that you can use during the evaluation, implementation, and productive operation of your systems.
Features
Implementation of the mySAP Business Suite
All phases of the implementation project (Business Blueprint, Configuration) are performed centrally in the Solution-Manager system.
Central project documentation repository in the Solution Manager
Integrated Project Administration allows you to manage planning schedules, human resources and other project data.
Customizing Synchronization
The Customizing Scout, with which you can compare customizing in various SAP components, e.g. an ERP system with SAP MDM
The Customizing Distribution, with which you can synchronize customizing in various SAP components.
Test
You can use the Test Workbench to organize and perform tests at the end of a project phase.
Reuse of the project structure for process-oriented tests
Global rollout
Integrated authoring environment, with which customers and partners can create their own templates, which they can reuse in subsidiaries, e.g. in a global rollout
E-Learning management
Creation of training material and learning maps (computer-supported self-tuition courses) to train end users after the implementation of new functions
Solution Monitoring
Central system administration
Analyze your system landscape with Service Level Reporting
System monitoring in real time
Business Process Monitoring
Services
Access to programs and Services, which help you to monitor and optimize the performance and availability of your system landscapes, and minimize your operational system risks
Service Desk
Solution support with workflow to create and handle problem messages
Change Management
Management of change requests, with workflow for the monitoring and audit of changes and transports in your system landscape, with the Change Request Management.
See also:
Projects
Solution Monitoring
SAP Solution Manager Roles
Authorization Concept
Project Authorizations
The following composite roles contain the authorizations required for the tasks to be performed in a project:
○ Project Leader
○ Application Consultant
○ Development Consultant
○ Technical Consultant
There are individual roles for Roadmap administration.
Production Authorizations
Production authorizations are in individual roles for the functions:
○ Solution Directory
○ Solution Monitoring
○ Service Data Control Center
○ Service Desk
○ Corporate Functionality
○ Solution Manager Diagnostics
○ Solution Reporting
Use
Adjust the SAP Solution Manager roles to your requirements.
Overview of Roles in Solution Manager
If you use trusting-trusted RFC connections, assign the authorization profile S_RFCACL to the user, as well.
Scenario Role
Implementation and Distribution SAP_SOL_PM_COMP
SAP_SOL_AC_COMP
SAP_SOL_BC_COMP
SAP_SOL_TC_COMP
SAP_SOL_RO_COMP
SAP_SOL_RE_COMP
SAP_SOL_LEARNING_MAP_DIS
SAP_DMDDEF_DIS
Implementation and Distribution (Roadmaps) SAP_RMDEF_RMAUTH_EXE
SAP_RMDEF_RMAUTH_DIS
Implementation and Distribution (E-Learning Management) SAP_SOL_TRAINING_EDIT
Service Desk (Service Desk) SAP_SUPPDESK_ADMIN
SAP_SUPPDESK_PROCESS
SAP_SUPPDESK_CREATE
SAP_SUPPDESK_DISPLAY
Service Desk (Corporate Functionality) SAP_SUPPCF_ADMIN
SAP_SUPPCF_CREATE
SAP_SUPPCF_PROCESS
Service Desk (Issue Tracking) SAP_SV_SOLUTION_MANAGER
SAP_SV_SOLUTION_MANAGER_DISP
SAP_SUPPDESK_ADMIN
SAP_SUPPDESK_PROCESS
SAP_SUPPDESK_DISPLAY
Change Request Management (Schedule Manager; Service Desk, cProjects)
SAP_CM_CHANGE_MANAGER
SAP_CM_DEVELOPER_COMP
SAP_CM_TESTER_COMP
SAP_CM_OPERATOR_COMP
SAP_CM_PRODUCTIONMANAGER_COMP
SAP_SOCM_REQUESTER
SAP_CM_ADMINISTRATOR_COMP
Solution Monitoring
(Service Data Control
Center)
SAP_SDCCN_ALL
SAP_SDCCN_DIS
SAP_SDCCN_EXE
Solution Monitoring
(Solution Directory)
SAP_SOLMAN_DIRECTORY_ADMIN
SAP_SOLMAN_DIRECTORY_EDIT
SAP_SOLMAN_DIRECTORY_DISPLAY
Solution Monitoring
(Operations)
SAP_SV_SOLUTION_MANAGER
SAP_SV_SOLUTION_MANAGER_DISP
SAP_SETUP_DSWP
SAP_SETUP_DSWP_SLR
SAP_SETUP_DSWP_SM
SAP_SETUP_DSWP_BPM
SAP_SETUP_DSWP_CSA
SAP_OP_DSWP
SAP_OP_DSWP_SLR
SAP_OP_DSWP_SM
SAP_OP_DSWP_EWA
SAP_OP_DSWP_BPM
SAP_OP_DSWP_CSA
Solution Reporting SAP_SOL_REP_ADMIN
SAP_SOL_REP_DISP
Solution Manager Diagnostics SAP_SMDIAG_WIZARD
SAP_SMDIAG_TEMPLATE
Cf.:
● Overview of Roles and Profiles in Satellite Systems
● SAP Solution Manager 4.0 configuration guide
● SAP note 834534
● SAP note 803142
Overview of Roles and Profiles in the Satellite Systems
Use the profiles below for SAP R/3 Release before SAP Web Application Server 6.10. Use the profiles below from SAP R/3 Release SAP Web Application Server 6.10.
If you use a trusting-trusted RFC connection, assign the authorization profile S_RFCACL to the user, as well.
Scenario Roles (Release > 6.10) Profile ( SAP_S_CUS_CMP S_CUS_CMP Data read access
SAP_S_CMSREG S_CMSREG Central system repository data
SAP_S_BDLSM_READ S_BDLSM_READ SDCCN data
Adjust Roles and Profiles
Before you assign SAP standard roles and profiles to users, copy and specify them.
SAP delivers roles and profiles with default values. If they are missing, you must set the values in the authorization objects yourself. Proceed as follows:
1. Load the roles/profiles from client 000 into your target client. You can:
○ Transport client 000 into your target client (roles and profiles)
○ Upload und Download (for roles in transaction PFCG)
○ RFC connection in transaction PFCG (for roles; menu path: MENU ® READ FROM OTHER SYSTEM WITH RFC). In this case, you must have set-up the RFC connection (transaction SM59).
2. Copy the roles/profiles into your namespace.
a. Choose Role Maintenance (transaction PFCG).
b. Enter a role name and choose Copy Role.
c. Enter the name of the new role in the To Role field.
d. Choose Copy All.
e. Save.
3. Complete missing values in the authorization objects.
a. Choose the Authorizations tab.
b. Choose ChangeAuthorization Data.
c. Enter your own values for the authorization objects, or double-click on the yellow traffic light.
The authorization objects appear with a green traffic light.
d.
When you double-click on the yellow traffic light, the value * appears. This grants full authorization for this field of the authorization object.
e. Save.
f. Generate the authorization profile.
4. Assign the role to users.
a. Choose the Users tab.
b. Enter the user names.
c. Choose User Adjustment.
d. Save.
You can also assign the roles to the users, in the user maintenance (transaction SU01).
e.
Project Authorization
Roles
The roles in the SAP Solution Manager are composite roles, which contain individual roles, which in turn contain authorizations for individual functions, e.g. for the Business Blueprint.
The following composite roles contain the central authorizations which they require for projects, and can be tailored to suit individual projects:
● Project leaders are responsible for organizing and planning the project, and monitoring costs and deadlines.
● Application consultants consultants are responsible for business content and the documentation of operational activities. This composite role has limited authorization and is intended for project members who need to be adjusted individually.
● Development consultants are responsible for the development of customer-specific programs and authorizations.
● Technical consultants are responsible for installing systems and providing technical support to users.
● Display user/Read only : contains SAP Solution Manager display/read only authorization.
● Read authorization depending on status in Document Management : only contains read authorization per status in Knowledge Warehouse Document Management
See also:
● Solution Manager Roles Overview
● Overview of Roles and Profiles in Satellite Systems
● SAP Solution Manager 4.0 configuration guide
● SAP note 834534 (Roles in the Solution Manager)
● SAP note 803142 (Roles in Satellite Systems)
Project Manager
Technical name: SAP_SOL_PM_COMP
Tasks
Project managers are responsible for the realization of the desired project results and the daily management of the project. They anticipate deviations from the project direction and carry out the necessary corrective measures immediately. Project managers should also understand the integration of the business processes within the enterprise.
Project managers are also members of the steering committee. They have decision-making authority in matters concerning the program and budget. He forwards strategic questions to the sponsor in order to make joint decisions.
Activities in SAP Solution Manager
The main responsibilities of the project manager include:
Organizing the entire project
Developing strategies and procedures for an efficient SAP implementation
Developing and maintaining the time schedule for the implementation project
Finalizing and managing the project scope, budget and deadlines in accordance with the approved plans
Assigning and managing resources
Monitoring project progress on a weekly basis
Carrying out evaluations and analyses
Carrying out a formal review at the end of each phase
Clarifying open issues in good time
Reporting regularly to the review committee on the progress and status of the project
Representing the project internally and externally
Giving status updates to the whole project team
Project managers can also copy content from a ValueSAP Edition 2 project into an SAP Solution Manager project. See the migration tool documentation.
Notes on Tailoring
If you require additional authorization, you can use the role SAP_BC_CUS_ADMIN: It contains authorization for the administration of customizing projects in the component systems.
The SAP Solution Manager configuration guide contains further information about authorizations in the component systems.
Integration
The project manager defines the content and the time frame of an implementation project, manages resources and monitors project progress. The application consultant reports to him and supports him in an administrative function.
Application Consultant
Technical name: SAP_SOL_AC_COMP
Tasks
Application consultants are responsible for making sure that the Business Blueprint and software configuration are tailored to the business processes and that analysis and report requirements are fulfilled. They use their knowledge of proven business procedures to support them in these tasks. Application consultants also function as advisers and work closely with the rest of the project team.
They also work in close cooperation with legacy system experts, when extraction of legacy data is necessary.
Activities in SAP Solution Manager
The main responsibilities of the application consultant include:
Supporting definition and modeling of business processes
Checking how the business model works with the SAP products
Configuring the software to suit the required business processes and to meet analysis and report requirements
Determining the global and local standardization requirements
Determining requirements for organizational change in the enterprise
Supporting knowledge transfer to other project team members
Supporting organization and performance of tests
Defining requirements for authorization profiles and access authorizations
Analyzing statistical performance and passing on recommendations for improvement to support
Creating and developing data solutions and strategies to meet the requirements of the corresponding SAP component (for example, APO, BW, CRM)
Creating end user training materials for the new functions
The application consultant is not responsible for:
The technical implementation of the solution
The programming of interfaces and other developments
Recurring problems with the quality of data (problems with data quality should be passed on to the project manager)
Notes on Tailoring
This role only contains basic functions. The following roles are available for additional authorizations:
SAP_BC_CUS_CUSTOMIZER contains authorizations for working with IMG activities.
The following role is useful for the application components:
SAP_BC_CUS_CUSTOMIZER
Integration
Application consultants are responsible for the development of business content and the documentation of operative activities in accordance with the appropriate standards. The development consultant develops customer-specific programs and their authorizations.
Development Consultant
Technical name: SAP_SOL_BC_COMP
Tasks
Development consultants work with the project manager and the application consultant on the planning and organization of the authorization concept. They also perform developmental tasks and customer-specific developments.
Activities in SAP Solution Manager
The main responsibilities of the development consultant include:
Organizing authorizations
Developing ABAP programs, for example, interfaces, forms, or modifications
Working with the ABAP Workbench
Notes on Tailoring
The following roles are available for additional authorizations:
SAP_BC_DWB_ABAPDEVELOPER contains authorization for implementing new applications and enhancements and for changing and modifying standard applications using the tools and services provided in the ABAP Workbench.
SAP_BC_TRANSPORT_ADMINISTRATOR contains all authorizations for the Change and Transport System
Integration
Development consultants work for the project manager and the application consultant and carry out programming tasks, in contrast to technical consultants who act as system administrators and are responsible for installing systems and providing technical support to users.
Technical Consultant
Technical name: SAP_SOL_TC_COMP
Tasks
Technical consultants plan the technical requirements for a project with the project manager and the manager of the technical team and then carry out the required technical tasks in the system.
Depending on the scope and complexity of the implementation, technical consultants may work in several areas, for example, system administration, database administration, network administration, operating system administration, development of cross-application components, or ABAP development.
For international projects, technical consultants also manage consultancy in the following areas:
Country-specific business requirements and country-specific SAP software requirements
Language-specific or codepage-specific requirements
Time-zone issues
Activities in SAP Solution Manager
The main responsibilities of the technical consultant include:
Setting up and installing the system landscape
Managing the system landscape and the corresponding transport landscape
Providing support and advice in all technical questions during an implementation project
Giving daily updates on the technical direction of the project including communicating deviations in the project
Developing and realizing the Cutover Plan before going live
Communicating effectively with the business process team
Transferring knowledge effectively to employees in system administration
In order to be able to carry out these tasks, the technical consultant should meet the following requirements:
A sound knowledge in the areas of databases, networks, programming and Internet technology
A sound knowledge of the SAP solutions
Notes on Tailoring
The following roles are available for additional authorizations:
SAP_BC_RRR_SAA_ADMIN provides the authorization for executing all the tasks in the System Administration Assistant.
Integration
The technical consultant acts as a system administrator and is responsible for installing systems and providing technical support to users, in contrast to the basis consultant who works under the instruction of the project manager and the application consultant and carries out programming tasks.
Read Authorization by Document Status
Technical name:
Use the specified individual role to:
● display business process scenarios, business processes steps, etc. of your solution, in the Solution Directory.
Integration
Use the Solution Monitoring role SAP_SV_SOLUTION_MONITORING_DISP to display the Solution Directory and sessions in Solution Monitoring.
Adjustment
Adjust Roles and Profiles
Solution Monitoring Roles
Tasks
Authorizations specified for the Solution Monitoring in the SAP Solution Manager:
for the Solution Monitorin sessions, classified by the areas Operations Setup and Operations
general individual role to display all sessions
Display all Sessions
general individual role to edit all sessions
Edit all Sessions
Activities
Authorizations are assigned to the roles. Specify user access to the session. There are the following authorizations:
A The user with the role has full authorization for the transaction or session.
D The user with the role can call the transaction or session in display mode.
N The user with the role has no authorization for the transaction or session.
Operations Setup session authorizations
Individual role Service Level Reporting System Monitoring Central Administration Business Process Monitoring
SAP_SETUP_DSWP A A A A
SAP_SETUP_DSWP_SLR A N N N
SAP_SETUP_DSWP_SM N A N N
SAP_SETUP_DSWP_CSA N N A N
SAP_SETUP_DSWP_BPM N N N A
Operations session authorizations
Individual role Early Watch Alert Service Level Reporting System Monitoring Central Administration Business Process Monitoring
SAP_OP_DSWP A A A A A
SAP_OP_DSWP_EWA A N N N N
SAP_OP_DSWP_SLR D A N N N
SAP_OP_DSWP_SM N N A (1) N N
SAP_OP_DSWP_CSA N N N A (1) N
SAP_OP_DSWP_BPM N N N N A
SAP_SV_SOLUTION_MANAGER_DISP session authorization
Individual role Early Watch Alert Service Level Reporting System Monitoring Central Administration Business Process Monitoring
SAP_SV_SOLUTION_ MANAGER_DISP D D D D D
SAP_SV_SOLUTION_MANAGER session authorization
Individual role Early Watch Alert Service Level Reporting System Monitoring Central Administration Business Process Monitoring
SAP_SV_SOLUTION_ MANAGER A A A A A
(1) from Release 3.20 SP02
Cf.:
Overview of Roles and Profiles
SAP Solution Manager 3.2configuration guide
SAP note 625773
Notes on Tailoring
You can use and combine the individual Solution Monitoring roles individually, according to your requirements.
Special authorizations for specific checks in individual sessions, are described in the online documentation of the sessions:
See also:
Set-Up Central System Administration
Using business process monitoring
Integration
If you need authorization for specific areas in the SAP Solution Manager, in addition to the authorizations for Solution Monitoring, use the associated individual roles with the specific authorizations:
Change Request Management
Service Desk
Service Data Control Centre
Solution Directory
General Administration and Display Authorization
Technical name: SAP_SV_SOLUTION_MANAGER
Technical name: SAP_SV_SOLUTION_MANAGER_DISP
Tasks
Authorizations are assigned to the roles. Specify user access to the session. The following authorizations are available for your project:
A The user with the role has full authorization for the transaction or session.
D The user with the role can call the transaction or session in display mode.
N The user with the role has no authorization for the transaction or session.
Activities in
Both individual roles have full authorization for the sessions in their areas.
If you only assign one of the roles to a user, the system only offers the user this area in the system interface.
They have display authorization for other transactions, according to the requirements of the session types:
■ SDCCN (Service Data Control Centre) for SAP EarlyWatch Alert and Service Level Reporting
■ SOLMAN_DIRECTORY (Solution Directory) for business process monitoring
Special authorization objects
Authorization Object Activity Meaning
D_SOL_VIEW 20 (Operations) Determines which area can be processed and displayed in the SAP Solution Manager.
D_SOLMANBU A (Bundle ID) Restricts processing by sessions.
■ SDCCN (Service Data Control Centre) for Service Level Reporting
■ SOLMAN DIRECTORY (Solution Directory) for business process monitoring
Special authorization objects
Authorization Object Activity Meaning
D_SOL_VIEW 10 (Operations Setup) Determines which area can be processed and displayed in the SAP Solution Manager.
D_SOLMANBU A Restricts processing by sessions.
Activities in the session type roles
●
Functional roles
Role Technical name Bundle ID Further explanation
Operations Setup
Service Level Reporting SAP_SETUP_DSWP_SLR EWA_CUST Additional display authorization for the transaction SDCCN (Service Data Control Centre)
System monitoring SAP_ SETUP DSWPSM SOL_MON Additional authorization to call the Solution Manager Diagnostics wizard
Central System Administration SAP_ SETUP_DSWP_CSA SOL_CSA Authorization object S_SAA_ADMI controls authorizations for customizing
checks.
Business process monitoring SAP_SETUP_DSWP_BPM BPM_JOBM
CP_BPM
CP_BPM_R
SOL_BPMO
Additional display authorization for the Solution Directory
Operations
SAP EarlyWatch Alert SAP_OP_DSWP_EWA EW_ALERT Additional full authorization for the transaction SDCCN (Service Data Control Centre)
Service Level Reporting SAP_OP_DSWP_SLR EW_CONS Additional display authorization for the transaction SDCCN (Service Data Control Centre)
Central system
administration
SAP_OP_DSWP_CSA SOL_CSA
System
monitoring
SAP_OP_DSWP_SM SOL_MON Additional authorization to call the Solution Manager Diagnostics wizard
Business process
monitoring
SAP_OP_DSWP_BPM BPM_JOBM
CP_BPM_R
SOL_BPMO
Additional display authorization for the Solution Directory
■
Adjustment
You can adjust the roles to your requirements.
If you also need authorization to display the Business Process MONITORING session, as well as the functional role for Service Level reporting in Operations , to check the business processes for the Service Level report, you can:
i. copy the authorization object D_SOLMANBU into the role and adjust it to your requirements (activity: 1; bundle ID: BPM_JOBM; CP_BPM_R; SOL_BPMO)
ii. give the user the role and adjust the authorization object D_SOLMANBU to your requirements (activity 1).
Integration
You can combine the functional roles with other roles in the area:
● Service Desk
● Change Management
●
If you want to create a Service Desk message from a Business Process MONITORING session, you need the role for the user in a message system , as well as the functional role for business process monitoring .
The online documentation for the sessions describes the scenarios in more detail.
Solution Reporting Roles
Technical name: SAP_SOL_REP_ADMIN
Technical name: SAP_SOL_REP_DISP
Tasks
The individual roles administer and display Solution Reporting.
Activities in
Tasks
The specified role sets up service connections to SAP.
Adjustment
Adjust Roles and Profiles
Simple way to differentiate is ASAP is a methodology for SAP Project Implementation where as Solution Manager is a document repository to store the documentation that u will create during all phases of the project.

Got reading error when deploying a web Dynpro project

Hi everyone,
I'm working on NWDS 7.1 CE. After I synchronized a project (using the "Create Project" option), then Build and Deploy it under the Development Infrastructure perspective, I can run it by choosing the "Run" option of the web Dynpro project's application. But once I chose "Deploy new arcihve and run", I got the following error message:
[ERROR CODE DPL.DC.3095] A reading error occurred while loading the SDU 'D:/usr/sap/DW1/J00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/3888/dow.comgcacmpprofitcenterui.ear'.; nested exception is:
     com.sap.engine.services.dc.util.readers.sdu_reader.SduReaderException: [ERROR CODE DPL.DC.3388]
The specified file D:/usr/sap/DW1/J00/j2ee/cluster/server0/temp/tc~bl~deploy_controller/archives/3888/dow.com~gca~cmp~profitcenter~ui.ear is not a valid SAP deployable unit. In case it is Java Enterprise application, please convert it to SAP compatible deloyable unit first.
Additional information: 'The information about the development component found in the manifest is either missing or incomplete!
Manifest attributes are missing or have badly formatted value:
attribute keylocation is missing
attribute keyname is missing
attribute keyvendor is missing
attribute keycounter is missing
Does anyone know what happens here? What's the difference of the Build/Deploy commands under Web Dynpro perspective and under Development Infrastructure perspective? After I made changes to the project, can I just deploy it under the Development Infrastructure perspective?
Thanks,
James

Hi Nilesh,
       Try opening Visual Admin if your not able to login with username(administrator) and password. Problem with NWD2004s do the following steps.
C:\usr\sap\J2E\JC01\j2ee\configtool->configtool.bat->open it
1. Click on Secure store
2. Right you will find :
admin/password/J2E->retype your admin passowrd which you gave during installation=>SAVE properly
Restart the server and try login visual admin
       Deploy now...Other wise see this thread same error solved:
Re: An Deploy Problem about Credentials.
Regards
Suresh

Application deployment on WebLogic 10.3.2

I am trying to understand the best practice to deploy web applications on WebLogic 10.3.2. Is it recommended have a managed server for each and every deployment or can we have multiple deployments under one managed server. Will there be any performance issues when multiple deployments are running on one managed server? Also can we have each deployment on one managed server listen on common http port?
Please advice.

**Is it recommended have a managed server for each and every deployment or can we have multiple deployments under one managed server.
--You can deploy multiple applications of one single managed server.
**Will there be any performance issues when multiple deployments are running on one managed server?
--There will not be performance issue as such; however you have to make sure that the system and server configurations meets the requirements.
--WebLogic Server allows you to configure a work manager where you define the rules and constraints for your application to boost the performance.
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/config_wls/self_tuned.html
**Also can we have each deployment on one managed server listen on common http port?
--Just to make sure if I understood correctly, did you mean one deployment per managed server listen on same http port?
--If yes, each managed server will have its own unique http port. So application deployed on that will be using a port associated with that managed server.
--In case if you want all the applications to use a same IP/Port, you can use proxy which will route the requests to these applications deployed on different managed servers.
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/plugins/overview.html

Error while deploying New WebService as part my EAR

Hi,
Jdev Version: 11.1.1.6.0
I have created a new Model project for WebService and did all the configuration mentioned on below url,
I am able to test this new webservice project by launching "TasksServiceImpl.java" file locally but getting some error while deploying it on standalone server. See below log for more details,
08:03:16 PM INFO: Unable to load annotation javax.interceptor.Interceptors for parsing. The annotation is ignored.
08:03:16 PM INFO: Unable to load annotation javax.interceptor.Interceptors for parsing. The annotation is ignored.
08:03:16 PM INFO: GenericWSWarAnnotationListener.parseAnnotatedClass Adding Servlet Mapping with URL pattern /TalentTasksService for annotated WebService class oracle.apps.xyz.common.tasksService.applicationModule.server.TasksServiceImpl
08:03:16 PM Error: Could not load endpointInterface oracle.appsxyz.common.tasksService.TasksService
08:03:17 PM #### Deployment incomplete. ####
08:03:17 PM WSA process exited with code 1.
Full deployment log file is also attached.
I have verified the jar selection mention on this forum link: help..
Any help on this will be greatly appreciate.

Yes Frank. Ours is an SDO service created as per [Service enabled Application Modules|http://docs.oracle.com/cd/E23943_01/web.1111/b31974/bcextservices.htm#CJAJGIEB] . We have created the deployment profile as a 'Business Component Service Interface' profile.
Our attempt to deploy onto standalone from Jdev also fails with the same error. Unsure why the interface is unable to load - Error: Could not load endpointInterface oracle.apps.xyz.common.tasksService.TasksService.
Does this mean, the deployment process is unable to locate this interface? We have cross checked our deployment profiles quite a few times and could not find anything amiss.

Getting error while deploying New WebService project on standalone server

Hi,
I have created a new Model project for WebService and I am able to test this new webservice project by launching "TalentTasksServiceImpl.java" file locally but getting some error while deploying it on standalone server. See below log for more details,
08:03:16 PM INFO: Unable to load annotation javax.interceptor.Interceptors for parsing. The annotation is ignored.
08:03:16 PM INFO: Unable to load annotation javax.interceptor.Interceptors for parsing. The annotation is ignored.
08:03:16 PM INFO: GenericWSWarAnnotationListener.parseAnnotatedClass Adding Servlet Mapping with URL pattern /TalentTasksService for annotated WebService class oracle.apps.hcm.talent.common.tasksService.applicationModule.server.TalentTasksServiceImpl
*08:03:16 PM Error: Could not load endpointInterface oracle.apps.hcm.talent.common.tasksService.TalentTasksService*
08:03:17 PM #### Deployment incomplete. ####
08:03:17 PM WSA process exited with code 1.
I have verified the jar selection mention on this forum link: help..
Any help on this will be greatly appreciate.

Yes Frank. Ours is an SDO service created as per [Service enabled Application Modules|http://docs.oracle.com/cd/E23943_01/web.1111/b31974/bcextservices.htm#CJAJGIEB] . We have created the deployment profile as a 'Business Component Service Interface' profile.
Our attempt to deploy onto standalone from Jdev also fails with the same error. Unsure why the interface is unable to load - Error: Could not load endpointInterface oracle.apps.xyz.common.tasksService.TasksService.
Does this mean, the deployment process is unable to locate this interface? We have cross checked our deployment profiles quite a few times and could not find anything amiss.

Unable to view deployed files in SJWS 7.0

I did search the forum but could not find any posts related to my issue.
We have an existing application running on version 6.1 and the application is not a .war file.
The application is just a folder consisting of jsp's which is located under the www-root/webapps on version 6.1
We have setup SJWS 7.0 in another machine and copied the application folder from version 6.1 to the location www-root/webapps in version 7.0
I get "File not found" exception when I try to access the application on the version 7.0 web server.
I did read the documentation for version 7.0 but could not figure out the ways and means for Deploying applications.
Could someone help out a noob on SJWS.
Thanks.

Thanks for the response.
Packaging the jsp has been ruled out. I have placed the application folder under the <web server home>/www-root/webapps and enabled the web-app section in the server.xml file.
Current application url is as follows, which is in iplanet version 6.1
http://localhost:8080/QA/AP/6.0/Admin
The application folder QA is kept under the webapps directory.
The application folder on version 7 is the same and kept under webapps directory.
<web-app>
<uri>/QA/AP/6.0/Admin</uri>
<enabled>true</enabled>
<path>*<Web Server HOME>*/www-root/webapps/QA/AP/6.0/Admin</path>
<description>Admin Web App</description>
</web-app>
When i try to access the application with the url
http://localhost:8080/QA/AP/6.0/Admin
I get file not found.
Also how can I clear the cache in version 7 where as in version 6 we have Class Cache folder.
Thanks in advance.

WLS 8.1 two domains with EJB and webapp deployed has JVM conflicts?

Test configuration environment:
Windows 2003 server installed with weblogic 8.1 server and oracle 9i.
This weblogic server have two domains, one is for EJB deployment, the other is a webapp that implements accessing to oracle through EJB.
The issue is when we tested a method provided by the EJB that uses double to calculate some total value, the result was correct. But when we tested it using webapp that was deployed on the same server of EJB, it's result was negative or zero.
I think the reason is that the JVM which both EJB and webapp used for calculation was the same and may made some conflicts when they run at the same time.
Any suggestion would be greatly appreciated.
Thank you in advance!
Shuaibing
Message was edited by:
linuxapple

This morning I deployed that webapp to the Domain that deployed the EJB, The results of calculating in webapp's jsp was correct.
Any one be kind enough to tell me what the calling JVM differences between single domain(deployed by EJB and webapp) and two domains (deployed EJB and webapp separately)?

MDS Exception when deploying taskflow

Use Case:
I have a taskflow that uses the Web Service Data Control as business service. Now I have packaged this as a jar file and deployed this as a shared library in my
integrated weblogic server. Now I created a new portal application and created a page.
I then created a file connection into my reosurce palette and drop my taskflow as a region on the page that I created in Webcenter Portal.
My problem is that when I ran it I am encountering below error
oracle.jbo.NoDefException: JBO-25002: Definition com.test.model.DataControls of type null is not found.
Caused by: oracle.mds.core.MetadataNotFoundException: MDS-00013: no metadata found for metadata object "/com/test/model/DataControls.dcx"Anybody know why?
Thanks
Webcenter 11.1.1.6

What do you mean with deploy method? I'm using the Deploy View of the NWDS, can't think of another way to deploy stuff on CE.
Or do you mean how the Content is structured? It's a SCA with a couple of DCs, which each consists of an ear, which each contains one ejb module. So the structure looks like the following:
SCA
+DC
++EAR
+++EJB
+DC
++EAR
+++EJB
+DC
++EAR
+++EJB
But it's no completely new project. I just want to add a bunch of web services to the existing ones. Therefore I modelled them with the Enterprise Service Builder and then used the model to let the NWDS generate the EJB Skeleton.
But thanks for your tip anyway.

"jdbc:mysql:///test" - "jdbc:mysql:test" what is the difference

"jdbc:mysql:///test" -> "jdbc:mysql:test" what is the difference:
I used both of them in my url but only "jdbc:mysql:///test" worked only
what is the difference what /// means?

JDBC URLs have the format
jdbc:<subprotocol>://<data source identifier>
jdbc indicates a JDBC data source. subprotocol identifies which JDBC Driver to use.
For com.mysql.jdbc.Driver and localhost server, database name as 'test':
it's jdbc:mysql://localhost/test
or jdbc:mysql://127.0.0.1:3306/test
you would select another server and database name.
For sun.jdbc.odbc.JdbcOdbcDriver with MS Access or SQLServer database, it's jdbc:odbc:DSNname
HTH

Required step by step guidance to deploy ejb on AppServer

Hi Friends,
I've downloaded the "Sun Java System Application Server
Platform Edition" from sun site.
But i don't knw how to deploy it using this App server.
eg.
1)How to create a project and application (Go to Menu select New something like this) using this AppServer?
1)How to connect to database not in code for deployment using AppServer?
2)How two beans interact with each other and how i mapp thm to each other while deploying it ?
3)How the Entity beans mapped to corresponding Session bean?
4)How i used it(ejb) with web-tier , means the deployment with any servlet or jsp?
I want step by step guidance to deploy an application on AppServer .
Regards,
Sachin Warang.

You could start with the tutorial, Part 3: Enterprise Beans
http://java.sun.com/javaee/5/docs/tutorial/doc/

Best method for BITS(Background Intelligent Transfer Service) deployment

Hi,
What is the best method for BITS(Background Intelligent Transfer Service) deployment for over 2000+ Windows 2008 servers at once? Also, does it matter on Windows 2008\2008 R2\2012 if the SCCM agent is installed before we deploy BITS to the servers?
Thanks,
Eric

Hi,
What is the best method for BITS(Background Intelligent Transfer Service) deployment for over 2000+ Windows 2008 servers at once? Also, does it matter on Windows 2008\2008 R2\2012 if the SCCM agent is installed before we deploy BITS to the servers?
Thanks,
Eric
What do you mean by Deploy BITS to the servers? The BITS client should already be installed on then as it is native to the OS.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

Differences in means of deployment

Similar Messages

Maybe you are looking for