Creating an Architecture Document For a Portal
I have been asked to come up with an Architecture Document for a public facing SharePoint 2010 site. I am familiar with the SharePoint 2010 technologies, however I need a starting point on where and how to start the Architecture document. Is there any Architecture Template Document that exists so that I can use them?
Hi
I cannot share the full and final doc with you but following Index will help you creating the Architecture document from the scratch
1 Document Overview............................................................................................................ 7
1.1 Scope............................................................................................................................... 7
1.2 Audience......................................................................................................................... 7
2 Logical Architecture............................................................................................................ 9
2.1 Overview.......................................................................................................................... 9
2.2 Diagram........................................................................................................................... 9
2.3 Component Description.............................................................................................. 9
3 Physical Architecture....................................................................................................... 11
3.1 Overview....................................................................................................................... 11
3.2 Production Environment.......................................................................................... 11
3.2.1 Diagram................................................................................................................... 11
3.2.2 Component Description....................................................................................... 12
3.2.3 Hardware Requirements...................................................................................... 14
3.2.4 Software Requirements........................................................................................ 14
3.3 Staging Environment................................................................................................. 14
3.3.1 Diagram................................................................................................................... 15
3.3.2 Component Description....................................................................................... 15
3.3.3 Hardware Requirements...................................................................................... 15
3.3.4 Software Requirements........................................................................................ 16
3.4 Development & Test Environment......................................................................... 16
3.4.2 Diagram................................................................................................................... 16
3.4.3 Component Description....................................................................................... 17
3.4.4 Hardware Requirements...................................................................................... 17
3.4.5 Software Requirements........................................................................................ 18
4 Non-Functional Requirements....................................................................................... 19
4.1 Security......................................................................................................................... 19
4.1.1 Requirements......................................................................................................... 19
4.1.2 Authentication........................................................................................................ 19
4.1.3 Authorization.......................................................................................................... 19
4.2 Availability..................................................................................................................... 21
4.2.1 Requirements......................................................................................................... 21
4.2.2 Hardware Redundancy and Failover................................................................. 22
4.2.3 Scaling Logical SharePoint Components......................................................... 22
4.2.4 Disaster Recovery.................................................................................................. 22
4.3 Performance................................................................................................................. 23
4.3.1 Requirements......................................................................................................... 23
4.3.2 Performance & Capacity Expectations.............................................................. 23
4.3.3 Size and Volume Assumptions.......................................................................... 23
4.3.4 Performance Testing Approach.......................................................................... 25
4.3.5 Performance Tuning Approach.......................................................................... 25
4.3.6 Monitoring and Reporting.................................................................................... 26
4.4 Accessibility................................................................................................................. 26
4.4.1 Requirements......................................................................................................... 26
4.4.2 Internal Access....................................................................................................... 26
4.4.3 Remote Access...................................................................................................... 26
4.5 Auditing & Reporting................................................................................................. 27
4.5.1 Requirements......................................................................................................... 27
4.5.2 Approach................................................................................................................. 27
4.5.3 Audit Reports.......................................................................................................... 27
4.5.4 Diagnostic Logging............................................................................................... 28
4.5.5 Portal Usage Reporting........................................................................................ 28
4.6 Exception Handling & Logging............................................................................... 28
4.6.1 Exception Handling............................................................................................... 28
Application..................................................................................................................... 29
4.6.2 Logging.................................................................................................................... 29
4.7 Caching......................................................................................................................... 29
4.7.1 Disk based caching for BLOBs........................................................................... 29
4.7.2 Client-side caching............................................................................................... 30
4.7.3 Object Caching...................................................................................................... 30
4.8 Maintainability.............................................................................................................. 31
4.8.1 Backup and Restore.............................................................................................. 31
4.8.2 Archiving & Purging.............................................................................................. 32
4.9 Regional Deployment................................................................................................ 32
4.9.1 Conceptual Diagram............................................................................................. 32
4.9.2 Feature Summary.................................................................................................. 33
4.10 Service Management.............................................................................................. 35
5 Search Architecture.......................................................................................................... 36
5.1 Introduction.................................................................................................................. 36
5.2 Key Design Considerations..................................................................................... 37
5.2.1 Distributed Geographical Deployment............................................................... 37
5.2.2 Content Sources.................................................................................................... 37
5.2.3 Availability & Performance................................................................................... 37
5.2.4 Physical Infrastructure.......................................................................................... 38
5.2.5 Search as a Shared Service................................................................................ 38
5.3 Search Architecture in portal..................................................................................... 38
6 Content Deployment Architecture................................................................................ 41
6.1 Introduction.................................................................................................................. 41
6.2 Key Design Considerations..................................................................................... 41
6.2.1 Distributed Geographical Deployment............................................................... 41
6.2.2 Security.................................................................................................................... 42
6.2.3 Availability............................................................................................................... 42
6.2.4 Publishing Frequency.......................................................................................... 42
6.2.5 Physical Infrastructure.......................................................................................... 42
6.2.6 User Contributed Content.................................................................................... 42
6.3 Content Deployment in portal................................................................................... 43
7 References.......................................................................................................................... 45
8 Key Decisions.................................................................................................................... 46
9 Dependencies.................................................................................................................... 47
10 Key Contacts................................................................................................................... 48
11 Appendix A – Active Directory Requirements........................................................ 49
12 Appendix B – Capacity Sizing Model........................................................................ 51
13 Appendix C – Hardware & Software Requirement Summary............................. 53
14 Appendix D – Site Architecture................................................................................... 55
Regards
Deepak Aggarwal
Similar Messages
-
How to create the appraisals document in the portal?
Hi all,
I am new of SAP, I would like to create the appraisals document in the portal, but i cant find the path of do that. Please kindly help me.
Thanks,
AndyHi ,
You can use BSP Application HAP_DOCUMENT for creating/modifying appraisal forms.
use the page document_todo.htm
Create a BSP Iview for documnet_todo.htm in the Portal... -
LSMW me51n, how to create one PR document for all the records in the file
HI all,
I need to create LSMW for t-code me51n -Create Purchase Requisition. I`m using Bapi BUS2105, method CREATEFROMDATA, idoc message type PREQCR, basic type PREQCR03. The problem is that the LSMW is creating different idoc and different PR document for every record in the source file. My requirement is to create one PR document for one source file (Every source file is different Purchase Requisition) . I`m trying to do this with writing some code(global functions ) in the 'Mapping and conversion rules' events - BEGINOF_TRANSACTION_, ENDOF_TRANSACTION__..., but i`m not very sure what exactly i`m doing .
Please help me resolve this problem, any help will be appreciated .
Best regards, Emil Milchev.Thank you for you answer.
But I have found faster way of doing it - two source structures, one HEADER and ONE ITEM.
HEADER: one empty text field and identificator for it.
ITEM: everything else.
Then everything was just fine, i`ve mapped the different IDOC segments by PREQ_ITEM fields (equal values in the source file : 10-10-10..., 20-20-20,.... etc.) and put all required fields for my LSMW
SOURCE FIELDS:
Z_ME51N_V2 - MASS_UPLOAD - CREATE create
Source Fields
UPFILE upload file
IDENT C(010) ident
Identifing Field Content: header
TEXT C(001)
UPFILE2 123
IDENT C(010) ident
Identifing Field Content: item
BSART C(004) Document type
BANFN C(010) Purchase requisition number
BNFPO_FOR_MAP N(005) Item number of purchase req. for MAPPING acc.
BNFPO N(005) Item number of purchase requisition
KNTTP C(001) Account assignment category
PSTYP C(001) Item category in purchasing document
MATNR C(018) Material Number
WERKS C(004) Plant
LGORT C(004) Storage Location
MENGE N(013) Purchase requisition quantity
EKGRP C(003) Purchasing group
KONNR C(010) Number of principal purchase agreement
KTPNR N(005) Item number of principal purchase agreement
LIFNR C(010) Desired Vendor
FLIEF C(010) Fixed Vendor
AFNAM C(012) Name of requisitioner/requester
PREIS AMT4(011) Price in purchase requisition
ABLAD C(025) Unloading Point
WEMPF C(012) Goods Recipient
PS_POSID C(024) Work Breakdown Structure Element (WBS Element)
KOSTL C(011) COST_CTR v bapito ?
NAME1 C(040) Name1 - Name of an address
NAME2 C(040) Name2 - Name of an address 2
STREET C(060) Street
DELIVERY_DATE C(008) Date on which the goods are to be delivered
TEXT C(132) item text
STRUCTURE RELATIONS :
Structure Relations
E1PREQCR Header segment <<<< UPFILE upload file
E1BPEBANC Transfer Structure: Create Requisition Item <<<< UPFILE2 123
E1BPEBKN Transfer Structure: Create/Display Requisition Acct Assgt <<<< UPFILE2 123
E1BPEBANTX BAPI Purchase Requisition: Item Text <<<< UPFILE2 123
E1BPESUHC Communication Structure: Limits <<<< UPFILE2 123
E1BPESUCC Communication Structure: Contract Limits <<<< UPFILE2 123
E1BPESLLC Communication Structure: Create Service Line <<<< UPFILE2 123
E1BPESKLC Create Comm. Structure: Acct Assgt Distr. for Service Line <<<< UPFILE2 123
E1BPESLLTX BAPI Services Long Text <<<< UPFILE upload file
E1BPMERQADDRDELIVERY PO Item: Address Structure BAPIADDR1 for Inbound Delivery <<<< UPFILE2 123
E1BPMERQADDRDELIVERY1 PO Item: Address Structure BAPIADDR1 for Inbound Delivery <<<< UPFILE2 123
E1BPPAREX Ref. Structure for BAPI Parameter EXTENSIONIN/EXTENSIONOUT <<<< UPFILE2 123
MAINTAIN FIELD MAPPING AND... :
the MAPPING between two IDOC`s segments:
In first segment:
E1BPEBANC Transfer Structure: Create Requisition Item
Fields
PREQ_NO Purchase requisition number
Source: UPFILE2-BANFN (Purchase requisition number)
Rule : Transfer (MOVE)
Code: E1BPEBANC-PREQ_NO = UPFILE2-BANFN.
PREQ_ITEM Item number of purchase requisition
Source: UPFILE2-BNFPO (Item number of purchase requisition)
Rule : Transfer (MOVE)
Code: E1BPEBANC-PREQ_ITEM = UPFILE2-BNFPO.
In second segment :
E1BPEBKN Transfer Structure: Create/Display Requisition Acct Assgt
Fields
PREQ_NO Purchase requisition number
PREQ_ITEM Item number of purchase requisition
Source: UPFILE2-BNFPO_FOR_MAP (Item number of purchase req. for MAPPING
Rule : Transfer (MOVE)
Code: E1BPEBKN-PREQ_ITEM = UPFILE2-BNFPO_FOR_MAP.
After that everything was OK . -
How to create an External Alias for a Portal URL ?
Hi Gurus,
Can anybody tell me how to create an external alias for a portal link(URL). Actually, my problem is i want to send this Portal URL(link) thru' a SendMail step to the user so that when he clicks on it, it will take him to his UWL(Ofcourse after signing-in). As this URL length is > 80 char(101 char), i am not getting the full lenght URL in my Outlook mail. THough we are on ECC 6.0,Basis Rel 7.0, as per the OSS note 559234, we should have this length extended to 132 bytes. But, for some reason, its not happening. And,in the same OSS note, it was mentioned that we can use external aliases to achieve this(shortening the URL length).
Can anybody tell me how to achieve this, either thru' increasing the URL length or thru' ext. aliases.
Please reply asap.
Thanks in advance
venuNot an issue as of now. I'll open up again if needed
-
I was at Apple Store yesterday and they created a pages document for me. When I got home and tried to open it, I get a message that I need a newer version of Pages. I see the image before I push "open". The 'kind' is pages publication. The file does not appear in the 'open recent' list.
Just be careful with Pages 5, it is not strictly an upgrade.
Apple has actually removed over 90 features and some work can be very difficult in the newer version.
It was all done to make it more interchangeable with the inferior iOS version:
http://www.freeforum101.com/iworktipsntrick/viewforum.php?f=22&mforum=iworktipsn trick
Peter -
HT5843 How do I create a locked document for privacy?
How do I create a locked document for privacy?
With the document open, tap the tools icon (wrench) and select Set Password. this assumes you are using the most recent version of the iWorks app or apps in question.
-
How to Create a Billing Document For SalesOrder
Hi Guys,
Any one please Explain me how to create a Billing Document for salesOrder. give me step by step procedure so i can easily understand the terms.Thanks in advance.
Thanks
Kiran.BHi Kiran,
Normally a billing doc is created after a sales order-->delivery.
U can create a sales order w.r.t a Contract or another sales order.
In your case, its possible only for sales Returns.
pass billing doc number to ORDER_HEADER_IN-REF_DOC in BAPI_SALESORDER_CREATEFROMDAT2.
Reward points if helpful
Regards,
Hemant -
Need to create a Change document for tracking Purpose on standard table
Hi Experts,
I am updating a field in standard table so need to create a change document for tracking the changes being done on the field.
I created the change Document with transaction SCDO but I am stuck at point - How to call that in the report program to enable the change document.
Please advice.
Thanks!!Hi
U can assign your transaction to Z-report like this:
PARAMETERS: TAB1 RADIOBUTTON GROUP R1 DEFAULT 'X',
TAB2 RADIOBUTTON GROUP R1,
TAB3 RADIOBUTTON GROUP R1.
DATA: TABNAME TYPE TABNAME.
START-OF-SELECTION.
CASE 'X'.
WHEN TAB1. TABNAME = 'BSID'.
WHEN TAB2. TABNAME = 'BSAD'.
WHEN TAB3. TABNAME = 'BKPF'.
ENDCASE.
CALL FUNCTION 'RS_TABLE_LIST_CREATE'
EXPORTING
TABLE_NAME = TABNAME
* ACTION = 'ANZE'
* WITHOUT_SUBMIT = ' '
* GENERATION_FORCED =
* NEW_SEL =
* NO_STRUCTURE_CHECK = ' '
* DATA_EXIT = ' '
* IMPORTING
* PROGNAME =
* TABLES
* SELTAB =
EXCEPTIONS
TABLE_IS_STRUCTURE = 1
TABLE_NOT_EXISTS = 2
DB_NOT_EXISTS = 3
NO_PERMISSION = 4
NO_CHANGE_ALLOWED = 5
OTHERS = 6
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF. -
MI31: Cannot Create Physical Inventory Document for a Certain Material
Dear SAP MM Friends,
Greetings! I am a budding MM functional analyst in our company. I received a call earlier regarding with transaction code MI31 (Selected Data for Physical Inventory Documents w/o Special Stock). The user cannot generate a physical inventory document for a certain material.
The thing is, we no longer have any stock for this material (MMBE). I tried generating physical document again by ticking "Only Materials with Zero Stock" but to no avail.
May I ask what might be the reasons behind? Your prompt response is highly appreciated.
Thank you very much.
Best Regards,
AlbertHi,
Please check also the existing physical inventory document for material, probably you still have active physical document from previous period.
1. Go to MI22 --> select your plant, storage location or you can also specify your material number --> execute.
2. Check your Physical Document list, at field Status doc. --> if the status is Doc. active, but it is not in your current period, then it could be the problem.
3. Delete the physical inventory doc that you found in step 2 (use tcode MI02 --> physical doc, year --> choose delete button)
4. Try to create new physical document for the material.
hope this help.
rob -
Creating an Accounting Document for Invoice
We cannot create an accounting document for Invoice.There is no problem in account determination procedure. I've tried to clear in VFX3, but gives me an error message that says "express document 'update was terminated' received from author.
After analysis the error being reported is:
"M2 012: Error determining posting period (info structure S010).Function module is MCV_STATISTICS_UPD_V1_INVOICE V1 NORMAL
Can you suggest how we can post/Release to Accounts?Hi Narendra
Go to T-code MCVV. In this case since the doc is not created it will not work.
Is there an ST22 dump. if yes put a break point there.
Check SM13 and you can see the here where the update fails. Apply break point there.
Go to MC26 and enter S010 and check if any update rules exisit. in one of the formulas you need to put a break point.then go back to VF01 and then before you hit the save enter /h in the command box to go into debug mode.
Once in debug mode Follow the menu path Setings--->update debug on/off.Debug and see why the update is failing.
Thanks -
How to create one GR document for mutiple Purchase orders
Can you please explain me in SAP - How to create one Goods Receipt document for reference of Multiple purchase orders.
Dear Tanuj,
Both Rama & Stephen are correct.
You can take Single GR for Multiple PO either in MIGO or MB01 as long as that POs belongs to same vendor.
In MIGO, after putting the PO press,enter, again give the next PO of that vendor .
If this solve your problem, close the issue.
With Regars,
Krishna Reddy -
BAPI_GOODSMVT_CREATE to create a material document for consumable goods
Hi All,
I am using a BAPi (BAPI_GOODSMVT_CREATE) to create a material document using a PO. Please note that the PO contain no material number. It contains short text. The account assignment is being copied in to the MIGO from PO (when i am doing the process manually without BAPI). But when i am using the BAPI at that time i am getting an error as:
E M7 036 No goods receipt possible for purchase order 45XXXXXXXXXX 00010 .
Logically this should not happen as when i do it manually i am able to post MIGO.
Under goods movement header i am giving :
posting date
doc date
text
goods movement code :
01
GOODSMVT_ITEM
plant
mov type
po number
vendor
line item
short text
cost cenrtre
order no(int ord no)
mov indicator: B
GL account
base unit of measure
Where i am going wrong?Hi Jurgen
In response to my post where i wrote my observations :
As you have suggested i have removed the account assignment objects and now i am not getting the error as mentioned in my post but at the same time i notice in export parameters in the bapi the following things which was not present earlier.
GOODSMVT_HEADRET 50000xxxxx2014
MATERIALDOCUMENT 50000xxxxx
MATDOCUMENTYEAR 2014
Now another thing is i am not getting any entry in return table.... which i should get. Please note that my test run contains no values(X).
i think i am near to the solution. Could you suggest any more crucial points i might be missing?"
for this i found out that there is a way to solve this issue. My concern was why the material document was not updating . Well this is how SAP behaves.
To update it we have to run simultaneously another fm " BAPI_TRANSACTION_COMMIT". This will update it in the mseg table which in turn will reflect it PO history. So my requirement is answered and fulfilled.
Thank you so much for the replies and cooperation.
Thank you all. -
Tcode to create single delivery document for all line items in PO
Hi all,
Sorry if it is a simple question, But I am from SD module. What is Tcode to create a single delivery documents for all line items in PO. I have 3 line items with Different materials having diffent quantities and there are different delivery dates and different delivery schedule dates. I need to create single delivery. Could you please tell me how to do it? What is the Tcode?
Thanks
AnilHi,
Inbound delivery T.code VL31N.
Regards,
JS -
Do we need to create individual shipment document for Transportation Chain
Do we need to create individual shipment document in Transportation Chain if the forwarding agent is same for all shipment?
For Example :
first it takes truck,
then ship,
then again truck to reach Customer.
in all above case forwading agent is same eg: DHL ServiceHi Doak,
Yes you need to create individual shipment document in Transportation chain.
For Example : when the trucks go from their respective shipping points to the harbor, the freight documents should not also contain main leg and subsequent leg information. When you create texts, you would not know if they are supposed to be valid for the preliminary, main or subsequent legs.
In order to avoid such limitations, we would recommend that you denote a transportation chain using multiple shipment documents. You can create these shipment documents almost automatically by using collective processing.
If you want depict a transportation chain within a shipment document, you must also accept the limited functions available to you.
The reason: Almost all shipment document functions refer to the document as a whole:
1.Outputs can only be printed for the entire document, not for individual legs
2.Handling units can only be created for the entire document, not for individual legs
3. The same is valid for texts, deadlines in general, etc.
Hope this provides you some clarity. Reward points if helpful.
Regards
Srikanth.A -
Create one invoice document for factory sales and third party sales
Hi All,
I want to create one single invoice document for material sold from factory and from third party.
I have checked the copy controls for order to billing but the system is still spliting the invoice.
Please share your expertise.Hello,
Can you please provide the details from the "Split Analysis", when you are trying to combine the 2 documents.
Regards,
Raghavendra
Maybe you are looking for
-
Browser crashes when trying to open 2 applets in 2 browser windows-
i am having this weird problem, on windows XP, if i open a applet in IE or firefox browser and then open a new browser window and try to open another applet in that windows, the browser simply crashes with no error message or anything, For example if
-
Set up a read only group on the config.xml file through Admin console
I would like to set up a group which can use Admin console (http://ip:7001/console). However, this group cannot deploy, modify anything on the configuration. In the document, I can add ACL lists. But how? The table of permission function on the docum
-
While similar to previous threads ... I've encountered a different flavor of issue with the _unknown user. It has appeared this week exclusively (all other folders appear correct) at the top level, Macintosh HD drive. This isn't a traditional folder,
-
so on my ibook g4 mid way through using it the screen blacks out (there is a very faint glow) this is happening more regularly now and atm as a temporary fix i just close the lip and open it. iv looked through some forums and it seems like a problem
-
How do I find the path for data files on my computer